Problem finding where the reset happened in the code with ESP-Insights

[filzek]

Currently we are using ESP-INSIGHTS in the ESP-IDF 5.2.1 development and we are facing serious issues with the new SDK as the BLE is doing a lot of crazy stuff onto the esp32 chipset, so, we are using the insights to try to found exactly where the problem is happen.

The problem is that the ESP-INSIGHTS dashboard only logs:

REBOOT
22/05/24 22:19:25
Reset (software or hardware) due to interrupt watchdog (ESP_RST_INT_WDT)
Reset (software or hardware) due to interrupt watchdog (ESP_RST_INT_WDT)

So, its possible to the ESP-INSIGHT to capture the func and task that was running that cause the ESP_RST_INT_WDT?

please advise as this is extreme important part to understant the insights

[vikramdattu]

Hi @filzek,

Can you also analyse logs before the reboot. That could give us the hint as what actually has caused Interrupt watch dog trigger.

Logging of WDT info, is not done for following reasons,

1. Since, it is critical interrupt, the watchdog handler needs to be extremely light weight.
2. Because, of this requirement, the WDT trigger information is printed to console using esp_rom function which cannot (and should not) be hooked with, the mechanism with which esp_insights capture these logs.

That said, it definitely is worth checking if we could have something useful to be added for WDTs. We will investigate the possibilities.

Thanks.