Hmm - interesting... what about doing it only if it were on a USB connection (with the console also on USB)? Because then it's going to crash anyway if nothing is there to read the messages, and if it is, you probably don't want to get spammed either.
it happens in response to just about every wiring error in I2C
There was a 'bug' in the Pico where the timeouts were crazy long. I hope I've fixed that now - however you're right, the timeouts should be way shorter across the board. From what I can tell, as short as 1ms seems ok - anyone know better?
If there's something reproducable that you can't break out of with Ctrl-C then can you let me know? I should be able to fix those.
I guess if you break out of an interval with Ctrl-C, it should maybe kill that interval?
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.
Hmm - interesting... what about doing it only if it were on a USB connection (with the console also on USB)? Because then it's going to crash anyway if nothing is there to read the messages, and if it is, you probably don't want to get spammed either.
There was a 'bug' in the Pico where the timeouts were crazy long. I hope I've fixed that now - however you're right, the timeouts should be way shorter across the board. From what I can tell, as short as 1ms seems ok - anyone know better?
If there's something reproducable that you can't break out of with Ctrl-C then can you let me know? I should be able to fix those.
I guess if you break out of an interval with Ctrl-C, it should maybe kill that interval?