Not sure if this is the correct site, since is due to an "strange behaviour" which occurs after get the latest commits from master, not in a release.
I did a deep-sleep test when I started to develop with ESP32 at the commit 5f3b9876b8088f89f5223484ad000cb4480d03f6 and all was working ok.
Today I retrieved a lot of new commits from master repository, and found that after the second Deep-sleep, the Task Group 0 watchdog is being triggered during the deep sleep. This was solved rolling back to the mentioned commit. Not sure which commit introduces this behaviour or if the problem is related just with my device but I thought could be interesting share with the community and developers.
Notes:
- I'm using 1000 as value in "Extra delay in deep sleep wake stub" configuration.
- Observed using DevKitC device using a simple code as shown next.
- I tested by removing watchdogs (interrupt and task) in menuconfig and occurs the same.
- I tested also by removing watchdog task with "esp_task_wdt_delete()" after enable it with "esp_task_wdt_init" and occurs the same.
Best regards and sorry for the inconvenience,
Dav
Code: Select all
RTC_DATA_ATTR int wake_count = 0;
void RTC_IRAM_ATTR esp_wake_deep_sleep(void) {
esp_default_wake_deep_sleep();
wake_count++;
}
void app_main(void)
{
///esp_task_wdt_init();
//esp_task_wdt_feed();
esp_deep_sleep_wakeup_cause_t cause = esp_deep_sleep_get_wakeup_cause();
if (cause == ESP_DEEP_SLEEP_WAKEUP_UNDEFINED) {
ESP_LOGI(tagg,"First start (%d)",wake_count);
} else {
ESP_LOGI(tagg,"Woken from deep sleep (%d)",wake_count);
}
//esp_task_wdt_delete();
esp_deep_sleep(3*1000000);