Getting random Interrupt Watchdog errors
Posted: Tue Sep 25, 2018 8:24 am
Hi all,
I have an ESP32 running on a custom build PCB. However sometimes the program crashes with the following error message:
Or sometimes like this:
Some characters are missing in the output above. I don't now why. This system is connected to a Raspberry Pi, maybe its not fast enough to keep up? I don't no at this point... it happens only during a crash, otherwise the Serial outputs correct/readable data.
Now according to the documentation, this is caused by the Interrupt Watchdog that kick in. So there might be a piece of code that loops infinitely. This I can understand.
But sometimes the reset reason is "TG0WDT_SYS_RESET" and sometimes its "TG1WDT_SYS_RESET". What to make of this. THe documentation says that TG0 is related to the "Task WDT" and the TG1 is related to the "Interrupt WDT".
Where to go from here? I have no clue where to start looking for the cause of this crash.
Anybody got some ideas?
I have an ESP32 running on a custom build PCB. However sometimes the program crashes with the following error message:
Code: Select all
Interrupt wd$
timeout on CPU0 PC 0021 : 0x0003A0 088e : 0x3fa3
: 0x3fa6A3 f0de : 0x0001A5 0001 A6 0000 : 0x0000A8 0001 : 0x3434
: 0x000aA11 0001 : 0x3f0dA13 0001 A14 fc24 : 0x3fc7SAR 0008 : 0x0000
: 0x0000LBEG 0020 : 0x40cfLCOUNT ffff
Backtrace:0021:0x3fa3088b:0x3fa5 0x40d5fca008fa:0x3f2c
Core1 register dump:
: 0x40c7PS 0604 : 0x80c9A1 fce0 A2 fc88 : 0x3434A4 0004 : 0x3f0e
: 0x3f12A7 0001 : 0x0000A9 f0df A10 0005 : 0x0000A12 080f : 0x3f0b
: 0x0002A15 0000 : 0x0001EXCCAUSE0005 EXCVADDR0000 : 0x40ceLEND 0026 : 0xffff
0x40c7fce0 0x40c9fcf008f4:0x3fc3 0x40d008413m 249s_oedm aecr upt ls..[mets Jun 8 2016 00:22:57
rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:5628
load:0x40078000,len:7756
ho 0 tail 12 room 4
load:0x40080000,len:5948
0x40080000: _iram_start at /home/peter/esp/esp-idf/components/freertos/xtensa_vectors.S:1685
entry 0x40080318
0x40080318: _KernelExceptionVector at ??:?
W (31) boot: PRO CPU has been reset by WDT.
W (31) boot: WDT reset info: PRO CPU PC=0x40083306
0x40083306: spi_flash_disable_interrupts_caches_and_other_cpu at /home/peter/esp/esp-idf/components/spi_flash/cache_utils.c:135Code: Select all
Interrupt wdt timeout $
n CPU0 PC 0021 : 0x0003A0 0892 : 0x3fa2
: 0x3f96A3 f0da : 0x0001A5 0001 A6 0000 : 0x0000A8 0001 : 0x3430
: 0x000aA11 0001 : 0x3f0cA13 0001 A14 fc1c : 0x3fc8SAR 0004 : 0x0000
: 0x0000LBEG 0020 : 0x40cfLCOUNT ffff
Backtrace:0021:0x3fa2089f:0x3fa4 0x40e1fc9008fe:0x000f
Core1 register dump:
: 0x40c7PS 0604 : 0x80c6A1 fcd0 A2 fc70 : 0x3430A4 0004 : 0x3f0d
: 0x3f01A7 0001 : 0x0000A9 f0db A10 0005 : 0x0000A12 0813 : 0x3f0a
: 0x0002A15 0000 : 0x0001EXCCAUSE0005 EXCVADDR0000 : 0x40ceLEND 0026 : 0xffff
0x40c7fcd0 0x40c5fce00808:0x3fc3 0x40dc008d[;1E(08 pcr_upCr upfahcni scrutd R=xfffisedo x[mCPU halted.
ets Jun 8 2016 00:22:57
rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:5612
load:0x40078000,len:7756
ho 0 tail 12 room 4
load:0x40080000,len:5876
0x40080000: _WindowOverflow4 at /home/peter/esp/esp-idf-v3.1/components/freertos/xtensa_vectors.S:1685
entry 0x40080318
0x40080318: _KernelExceptionVector at ??:?
W (31) boot: PRO CPU has been reset by WDT.
W (31) boot: WDT reset info: PRO CPU PC=0x4008fc06
0x4008fc06: commonErrorHandler at /home/peter/esp/esp-idf-v3.1/components/esp32/panic.c:649
W (31) boot: WDT reset info: APP CPU PC=0x4008fc46
0x4008fc46: panicHandler at /home/peter/esp/esp-idf-v3.1/components/esp32/panic.c:649
I (37) boot: ESP-IDF v3.1 2nd stage bootloader
I (42) boot: compile time 09:29:55
I (46) boot: Enabling RNG early entropy source...
I (51) boot: SPI Speed : 40MHz
I (56) boot: SPI Mode : DIO
Now according to the documentation, this is caused by the Interrupt Watchdog that kick in. So there might be a piece of code that loops infinitely. This I can understand.
But sometimes the reset reason is "TG0WDT_SYS_RESET" and sometimes its "TG1WDT_SYS_RESET". What to make of this. THe documentation says that TG0 is related to the "Task WDT" and the TG1 is related to the "Interrupt WDT".
Where to go from here? I have no clue where to start looking for the cause of this crash.
Anybody got some ideas?