I noticed a similar thing when connected to GPS or LCD or both. It feels like someone is poking around in memory - for sure not my code, because I do not use (yet) those instructions and I'm aware of the risk they pose. Reloading the code helped. Since I was in development I did not pay much attention an attributed it to incorrect / run-away code.
Since I wanted to test-run my GPS connection and line processing for days, I tried to catch any irregularities in try-catch blocks... but somehow I could not get it working. The errors - a GPS sentence field was unexpectedly empty - just let's the thread die and luckily, the next on.data will keep the processing (re-)going.
@tom.gidden, I'm glad you brought this up, so I feel less 'begin nuts...' or 'seeing ghosts...' ;-)
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 a similar thing when connected to GPS or LCD or both. It feels like someone is poking around in memory - for sure not my code, because I do not use (yet) those instructions and I'm aware of the risk they pose. Reloading the code helped. Since I was in development I did not pay much attention an attributed it to incorrect / run-away code.
Since I wanted to test-run my GPS connection and line processing for days, I tried to catch any irregularities in try-catch blocks... but somehow I could not get it working. The errors - a GPS sentence field was unexpectedly empty - just let's the thread die and luckily, the next on.data will keep the processing (re-)going.
@tom.gidden, I'm glad you brought this up, so I feel less 'begin nuts...' or 'seeing ghosts...' ;-)