Web IDE no longer flashing to RAM properly?

[RKBoss6]

I was just developing a new module using sleeplog, and I started noticing that the IDE would no longer upload code successfully, especially in RAM. Instead, it says Prompt not detected - upload failed. Trying to recover... followed by Execution Interrupted printed to the IDE console. Every once in a while before, it would come up, but the second try flashing it again fixed it. However, as of now, nothing is being properly uploaded to RAM. Memory is fine, I tried compacting the watch, rebooting the watch, nothing has worked so far... As far as I can tell, uploading code to files still uploads fully, but with that same prompt not detected error.

[gfwilliams]

Have you tried uploading different code? Prompt not detected usually means that the code you uploaded is taking a long time (a few seconds at least) to run as it's uploaded, and so the IDE thinks something is wrong and tries to break out of execution.

If there's stuff that takes a long time you can always run it in a setTimeout so it occurs after the initial upload is done

[RKBoss6]

Yes, my code so far takes about 3 seconds to run, as it gathers a lot of data... is there any way to fix that without changing the code, like a setting in the IDE?

[siegmar]

Today I have the same problem : New interpreter error: FIFO_FULL
Prompt not detected - upload failed. Trying to recover...
My Sourcecode has now 77 kByte the Sourcecode from yesterday, I can load

[siegmar]

To RAM yes for debugging when the code is compressed then it is correct loaded in the IDE. When I make a App and load it with my app Loader it is also working well

[siegmar]

Ok, sometimes this "Prompt not detected - upload failed. Trying to recover" is coming. I have a routine on the beginnig it needs sometimes 3000 ms . FIFO full and the Prompt not detected ... is a different failure. I think my 3000 ms delay is the problem now. How can I solve this problem. ?

[RKBoss6]

As @gfwilliams said, just wrap whatever starts the code inside a setTimeout(...,20). When it registers that there's a timeout, it ignores the delay, and it worked for me.

[siegmar]

Thanks Gordon, i will check it in the afternoon. Your Interpreter is really fantastic, it makes a lot of fun and my app is working very well :-)

[fanoush]

There is also a way to send selection of text - you just mark it with mouse or shift + cursor and then press shift+enter. This does the same thing as if you would type the block to the left side (or copy paste it?). I just tried it with code like this

var x=0;
print(Date());
for (i=0;i<100000;i++)x+=i;
print(Date());
print(x);

and it takes long time and still does not produce any error. However I am not sure if it can be used in your case. I am using it sometimes when doing 'partial upload' - like fixing bug in one function and updating its definition but leaving the rest the same and already running.

[gfwilliams]

FIFO full and the Prompt not detected ... is a different failure.

But they're caused by the same thing - code taking a long time to run. I'd say just consider writing code to Storage even for testing - it'll solve a lot of issues and is closer to what you get when running from the app loader, so better from that point of view

[siegmar]

As you said Gordeon : " just wrap whatever starts the code inside a setTimeout(...,20). When it registers that there's a timeout, it ignores the delay, and it worked for me." It's worked for me too ...until now Thank you you for your help