Specific script loading problem

[numerist]

For some years, I've loaded my watch script onto my js1 and js2 with no problem. Although the script is unchanged, I now get this:
New interpreter error: FIFO_FULL
Interpreter error: [
"FIFO_FULL"
]
along with a few other script errors that probably result from that. Is there a quick fix? I'm not familiar enough with js to figure this out. Thanks!

[gfwilliams]

How do you load the script on? Using the IDE?

I seem to recall a post about this before at some point. Is it possible that your settings got reset and the IDE is uploading the code to RAM and not to a file on the Bangle's storage? It'd show RAM under the upload button if so.

If the script had some code that runs at startup and takes a long time to execute, that can stall the device while it's uploading. Normally it should be caught before you get the FIFO_FULL error but it can be caused by a few things, including changes to your PC/drivers that increase the latency of the bluetooth connection or the number of packets that can be buffered up.

[numerist]

Thank you for your answer. I was using the IDE, yes. The mistake may have been trying to load into RAM. Loading to Flash enabled the loading into the watch to work. I hope that makes sense—it's not something I understand much.

[yerpj]

I am experiencing the FIFO_FULL error quite often those days, I don't know exactly why, but I was able to reduce it by setting the option in IDE settings --> Communications --> Throttle Send --> Always . I hope it can help you as well

[gfwilliams]

Are you uploading to RAM, or flash?

I'm setting things up to allow the IDE to do packet-based uploads soon which should basically fix this completely (but not for RAM uploads)

[yerpj]

I get this error while uploading to flash. I used to have it quite often on a custom build running on a NRF52840 but I recently experienced the same as well on a Puck.js running on version 2v26 IIRC.

[RKBoss6]

Here's another thread with this same issue: https://github.com/orgs/espruino/discussions/7852

[gfwilliams]

Kind of, yes - although the main issue:

Prompt not detected - upload failed. Trying to recover...

isn't really an error - it's reporting that it uploaded your code but the device isn't responding because it was too busy executing that code, so it tries to break out.

It was actually a 'feature', added because people were uploading code that took ages to execute and then complaining that the device was unresponsive.

[RKBoss6]

Huh, that's nice to know, thanks. Someone in that thread also had that issue, so that's why it put it in.