-
Notifications
You must be signed in to change notification settings - Fork 7.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
Crashed task handle: 0x3ffbbbf4, name: 'esp_timer' case InterruptWDTTimoutCPU0 (IDFGH-7181) #8780
Comments
Hi @sxsx2yzyz, I see that Thread 1 is looping indefinetely, triggering the watchdog which means it was unable to take the Does this always happen after 30 hours? What is your application exaclty doing? I know it's hard but can you try providing a small example that reproduces the issue? Or have your tried reproducing it? |
I had the same problem again and this time after the program has been running for about 33.5 hours.I have 2 pieces of esp32wrover-E and 1 piece of esp32wrover-IE, the problem is always esp32wrover-IE.
I tried to analyse coredump, but the program was recompiled and app.elf has been changed. Here is output of run
|
The same thing happened again, this time with esp32-wrover-E, 67 hours after the chip was booted, and here are the results of the coredump analysis.
|
i have the same issue, happen when enable psram in menuconfig and enable psram during startup.
in my case if i enable this option: |
I enabled too.Now i'm trying not to use esp_timer. |
I no longer use anything related to esp_timer, e.g. LEDC_LOW_SPEED_MODE for ledc, periodic_timer for esp_timer. no longer have this problem. |
Again
|
Environment
git describe --tags
to find it):v5.0-dev-422-ga18cb70905-dirty
xtensa-esp32-elf-gcc --version
to find it):8.4.0
Problem Description
The program ran for about 30 hours and an InterruptWDTTimoutCPU0 error occurred
coredump:
The text was updated successfully, but these errors were encountered: