-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CircuitPython crashes with Internal watchdog timer expired. #9428
Comments
Thanks. Is the failure also The plain Pico doesn't have wifi, so how did you make this run on the Pico? Or is that a typo? How long does it take for the safe mode failure to happen? Are you using the latest versions of the needed libraries? |
Yes it is.
It is a Pico/W only issue. I'm so used to including both versions of the Pico when I write about them. My apologies.
I can only say overnight. For example I went to bed around 11pm after checking it was still operational, then when I got up this morning a little after 6 am it was in safe mode.
Yes. Whenever I update I always pull the version of the libraries that match the CircuitPython version as well as the release date. |
Could you post a redacted (hide password, SSID, etc.) version of your |
Just the four shown above. STATIC_IP and GATEWAY aren't needed, and I need to adjust the comment block accordingly. |
CircuitPython version
Code/REPL
Behavior
When left to run unattended the board will stop executing, and any attempt to perform ^D to restart returns the following message at the REPL:
Auto-reload is off.
Running in safe mode! Not running saved code.
You are in safe mode because:
Internal watchdog timer expired.
Press reset to exit safe mode.
Press any key to enter the REPL. Use CTRL-D to reload.
Description
Not only does this occur with the Espressif ESP32-S3 board, but it also occurs with the Raspberry Pi Pico and Pico/W with the same version of CircuitPython. It will also occur with CircuitPython 9.0.5, again with the boards listed above.
Additional information
No response
The text was updated successfully, but these errors were encountered: