-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Core 1 panic'ed (Interrupt wdt timeout on CPU1) on ESP32 NodeMCU ( ESP32-D0WD-V3) #211
Comments
It seems that the watchdog triggers because of the loop. I am trying for now to run with the watchdog disabled as indicated here and will report back in a few hours: https://stackoverflow.com/questions/51750377/how-to-disable-interrupt-watchdog-in-esp32-or-increase-isr-time-limit |
Might be related to #93 and espressif/arduino-esp32#832 |
I have the same issue wie an ESP32 and a DHT22 sensor, but sometimes it takes some days after the error occurs. I think the problem is, that the loop in line 304 is missing a break condition. If we are getting a timeout for every expectPulse it takes about 80 ms and this is not far away from 300ms what is the watchdog timer. So something like this could help:
I'm not able to test this right now, but on weekend I will test it and report back. |
I solved that by doing my own lib (https://github.com/mathieucarbou/MycilaDS18) which is using behind the code from https://github.com/junkfix/esp32-ds18b20 based on RMT peripheral. It is far more reliable on ESP32 and does not have busy loops for the readings. |
As mentioned in (#211 (comment)), I was able to test the modification and now for about 8 days my project is running without any errors. I have created a pull request (#218). |
code:
called from stup():
called from loop, executed each 10 seconds:
crash:
where it crashed:
Please let me know if you need something else...
The text was updated successfully, but these errors were encountered: