You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use esp_reset_reason() to detect crash on production firmware.
In my code I check the reason like ESP_RST_PANIC or ESP_RST_INT_WDT and switch device to safemode with limited hardware and peripheral install, because secure boot and flash encryption chip make it bricked if it enter boot loop, and there is no way to flash it.
It work fine if I set debug level from INFO to VERBOSE, it it will stop working when set:
CONFIG_LOG_DEFAULT_LEVEL_NONE=y
I don't know if this is a bug or by design.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
esp_reset_reason() not working when set log level none (CONFIG_LOG_DEFAULT_LEVEL_NONE=y)
esp_reset_reason() not working when set log level none (CONFIG_LOG_DEFAULT_LEVEL_NONE=y) (IDFGH-14810)
Mar 9, 2025
I use esp_reset_reason() to detect crash on production firmware.
In my code I check the reason like ESP_RST_PANIC or ESP_RST_INT_WDT and switch device to safemode with limited hardware and peripheral install, because secure boot and flash encryption chip make it bricked if it enter boot loop, and there is no way to flash it.
It work fine if I set debug level from INFO to VERBOSE, it it will stop working when set:
I don't know if this is a bug or by design.
The text was updated successfully, but these errors were encountered: