ESP32 Forum

Posted: **Fri May 11, 2018 9:47 pm**

Hello,

I am running a program with multiple tasks on the ESP32 module, which are continuously employing GPIO interrupts, timer interrupts and WiFi communication.

After running for a few hours, the system suddenly crashed and reset itself with the following message on the monitor:

W (30) boot: PRO CPU has been reset by WDT.
W (30) boot: WDT reset info: PRO CPU PC=0x40081ae3
0x40081ae3: .check_dport_access_end at /home/ro269/Desktop/gridballast/Support/esp-idf/components/esp32/./dport_panic_highint_hdl.S:182

W (31) boot: WDT reset info: APP CPU PC=0x4008d977
0x4008d977: panicHandler at /home/ro269/Desktop/gridballast/Support/esp-idf/components/esp32/./panic.c:648

Can someone explain to me what caused this and what can done to possibly rectify it?

Thanks.

Posted: **Mon May 14, 2018 3:02 am**

It looks like the CPU may have crashed while in a critical section for performing DPORT reads/writes, which prevents it from printing a proper panic handler stack trace.

What version of ESP-IDF are you using?

Posted: **Tue Jul 03, 2018 7:59 pm**

I have a similar problem. I've opened an issue on github #2144, with details.

ESP32 Forum

CPU crash due to DPort access?

CPU crash due to DPort access?

Re: CPU crash due to DPort access?

Re: CPU crash due to DPort access?