3 ms·
Yep that exactly, which is interesting as the ESP32 in comparison usually still manages to connect and lets you break execution despite being stuck in a loop wi
by moffkalast 4y ago
Yep that exactly, which is interesting as the ESP32 in comparison usually still manages to connect and lets you break execution despite being stuck in a loop with main.py, even with blocking timers set up. Frankly the WebREPL on the ESP is about as reliable as the Pico is via USB cable.
I've never lost any code on the ESP, but on the Pico just as you're nearing deployment and want to test run at boot you run into the easy pitfall of having to delete all of your files to unbrick the thing. Luckily I hadn't written much by that point yet.
I'd assumed that it's because the ESP runs the repl backend and the user code on separate cores, but the Pico is also dual core which would mean it could do the same. Yet it does not. I'm more convinced that the implementation is just kinda bad instead.