Problem with reboot W/O backtrace on ESP32 - esp-idf 3.0.9
Posted: Tue Feb 16, 2021 10:38 am
Hello, I have a problem in an esp32 that crashes and reboot every ~10h for an irs interrupt without writing the problem:
I tried to change the interrupt watchdog timeout from 300ms to 1000ms or to 50ms without noticeable differences.
I also enabled the core dump from menuconfig, but nothing is printed before the reboot.
How can I have information regarding the problem that blocked the interrupt?
I have different tasks running on the device, but most of the code is running without interrupts. The device is communicating with an UART device, connected to wifi and sending information to an MQTT broker.
Thanks
Code: Select all
ets Jun 8 2016 00:22:57
rst:0x8 (TG1WDT_SYS_RESET),boot:0x12 (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:5560
load:0x40078000,len:12568
entry 0x40078fe8
[0;33mW (26) boot: PRO CPU has been reset by WDT.[0m
[0;33mW (27) boot: WDT reset info: PRO CPU PC=0x400840d6[0m
[0;33mW (27) boot: WDT reset info: APP CPU PC=0x400faf86[0m
[0;32mI (33) boot: ESP-IDF v3.0.9-dirty 2nd stage bootloader[0m
I also enabled the core dump from menuconfig, but nothing is printed before the reboot.
How can I have information regarding the problem that blocked the interrupt?
I have different tasks running on the device, but most of the code is running without interrupts. The device is communicating with an UART device, connected to wifi and sending information to an MQTT broker.
Thanks