...I noticed that with combination of most recent updated parts - Chrome (on OS X), Espruino, and Espruino - something is not as clean working anymore as before, especially after having saved a piece of code. 'Removing' that piece of saved code with reset() and saving no code - empty editor / right hand side - it is still fishy. Empty program still saves 800+ bytes and pluging Pico into USB wants to output something (loading message). Connecting will not always be successful, and when seemingly successful - indicated by the green connected icon - console (input) is not always connected, logo not always shown, nor will uploading - sending - code to the board make the logo show... Sometimes upload is extremely slow - see green progress bar at the bottom right in the IDE. Entering reset() may trigger the logo... and the uplaod. Recovering from not connected even though showing connected requires sometimes a restart of the browser. I guess it has something to do with the access of the serial (through USB) by Chrome.
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.
...I noticed that with combination of most recent updated parts - Chrome (on OS X), Espruino, and Espruino - something is not as clean working anymore as before, especially after having saved a piece of code. 'Removing' that piece of saved code with
reset()
and saving no code - empty editor / right hand side - it is still fishy. Empty program still saves 800+ bytes and pluging Pico into USB wants to output something (loading message). Connecting will not always be successful, and when seemingly successful - indicated by the green connected icon - console (input) is not always connected, logo not always shown, nor will uploading - sending - code to the board make the logo show... Sometimes upload is extremely slow - see green progress bar at the bottom right in the IDE. Enteringreset()
may trigger the logo... and the uplaod. Recovering from not connected even though showingconnected
requires sometimes a restart of the browser. I guess it has something to do with the access of the serial (through USB) by Chrome.