Contents
What is the function of the watchdog in ESP32?
The Interrupt Watchdog is responsible for detecting instances where FreeRTOS task switching is blocked for a prolonged period of time. The TWDT is responsible for detecting instances of tasks running without yielding for a prolonged period. The interrupt watchdog makes sure the FreeRTOS task switching interrupt isn’t blocked for a long time.
What are the tasks that did not reset the watchdog?
The following tasks did not reset the watchdog in time: E (51859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: E (66859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: E (81859) task_wdt: Task watchdog got triggered.
How to disable interrupt watchdog in ESP32 or increase ISR?
I searched ways to disable interrupt WDT but no help. The file esp_int_wdt.h in ~Documents\\Arduino\\hardware\\espressif\\esp32 ools\\sdk\\include\\esp32 provides two functions for enabling interrupt WDT for both or one CPU. There is no function to disable it.
Why is the interrupt watchdog bad for FreeRTOS?
The interrupt watchdog makes sure the FreeRTOS task switching interrupt isn’t blocked for a long time. This is bad because no other tasks, including potentially important ones like the WiFi task and the idle task, can’t get any CPU runtime.
What happens when ESP32 is connected to OpenOCD?
This means that interrupt watchdog and task watchdog functionality will essentially be disabled. No warnings or panics from either watchdogs will be generated when the ESP32 is connected to OpenOCD via JTAG. Initialize the non-CPU-specific parts of interrupt watchdog.
Are there any watchdog timers in ESP-IDF?
The ESP-IDF has support for two types of watchdogs: The Interrupt Watchdog Timer and the Task Watchdog Timer (TWDT). The Interrupt Watchdog Timer and the TWDT can both be enabled using Project Configuration Menu, however the TWDT can also be enabled during runtime.