Ahh - was it 6 calls in quick succession? and you were pressing the screen/mashing the button at the same time? FIFO_FULL means Espruino hasn't been able to process all the data it received, and some got lost.
What you're doing with g.dump() is basically blocking Espruino's execution for several seconds while it sends the data out. XON/XOFF flow control is implemented in the IDE so it shouldn't send more data than the watch can handle, and if you're pressing the button or doing other things that add to the event queue then those can't be flow controlled.
I wouldn't have thought it was anything to worry about. If you get FIFO_FULL during upload that's more worrying as it means flow control isn't working. I think possibly I need to find a way to increase the input buffer size since the delay in transmission means by the time XOFF gets back to the IDE it's already sent a few more packets.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Hi,
Ahh - was it 6 calls in quick succession? and you were pressing the screen/mashing the button at the same time? FIFO_FULL means Espruino hasn't been able to process all the data it received, and some got lost.
What you're doing with
g.dump()
is basically blocking Espruino's execution for several seconds while it sends the data out. XON/XOFF flow control is implemented in the IDE so it shouldn't send more data than the watch can handle, and if you're pressing the button or doing other things that add to the event queue then those can't be flow controlled.I wouldn't have thought it was anything to worry about. If you get FIFO_FULL during upload that's more worrying as it means flow control isn't working. I think possibly I need to find a way to increase the input buffer size since the delay in transmission means by the time XOFF gets back to the IDE it's already sent a few more packets.