Arduino-esp32: Task watchdog got triggered. The following tasks did not feed the watchdog in time

Created on 28 Aug 2017 · 67Comments · Source: espressif/arduino-esp32

Hardware:

Board: ESP32-WROVER-KIT
Core Installation/update date: 25/08/2017
IDE name: Arduino IDE
Upload Speed: 115200

Description:

if the

void loop()

function is empty i keep receiving the error message

Task watchdog got triggered. The following tasks did not feed the watchdog in time:

 - IDLE (CPU 1)

Tasks currently running:

CPU 0: IDLE

CPU 1: loopTask

i solved the problem by adding

vTaskDelay(10);

in the main.cpp

void loopTask(void *pvParameters)
{
    setup();
    for(;;) {
        micros(); //update overflow
        loop();
        vTaskDelay(10);
    }
}

according to ESP_Sprite recommendation in this post
https://esp32.com/viewtopic.php?f=2&t=809&p=10191&hilit=esp_task_wdt_feed#p10191

Would it be possible to update the arduino-esp32 framework ?

Sketch:

/*
 *  This sketch demonstrates how to scan WiFi networks.
 *  The API is almost the same as with the WiFi Shield library,
 *  the most obvious difference being the different file you need to include:
 */
#include "WiFi.h"

void setup()
{
    Serial.begin(115200);

    // Set WiFi to station mode and disconnect from an AP if it was previously connected
    WiFi.mode(WIFI_STA);
    WiFi.disconnect();
    delay(100);

    Serial.println("Setup done");
    Serial.println("scan start");

     // WiFi.scanNetworks will return the number of networks found
     int n = WiFi.scanNetworks();
     Serial.println("scan done");
     if (n == 0) {
         Serial.println("no networks found");
     } else {
         Serial.print(n);
         Serial.println(" networks found");
         for (int i = 0; i < n; ++i) {
             // Print SSID and RSSI for each network found
             Serial.print(i + 1);
             Serial.print(": ");
             Serial.print(WiFi.SSID(i));
             Serial.print(" (");
             Serial.print(WiFi.RSSI(i));
             Serial.print(")");
             Serial.println((WiFi.encryptionType(i) == WIFI_AUTH_OPEN)?" ":"*");
             delay(10);
         }
     }
     Serial.println("");

     // Wait a bit before scanning again
     delay(5000);
}

void loop()
{

}

Debug Messages:

Source

orcema

Most helpful comment

Anyone who still want to avoid that error should try
adding these three line to your continuous rtos function,

TIMERG0.wdt_wprotect=TIMG_WDT_WKEY_VALUE;
TIMERG0.wdt_feed=1;
TIMERG0.wdt_wprotect=0;

And add this header

#include "soc/timer_group_struct.h"
#include "soc/timer_group_reg.h"

akshar001 on 17 Aug 2018

👍6 🎉3

All 67 comments

@orcema Your link gives a 404. What are you suggesting?

lonerzzz on 29 Aug 2017

@lonerzzz try this link works

tobozo on 29 Aug 2017

Thanks for the link but I a unsure what it is you are suggesting. Please clarify. The link refers to calling vTaskDelay() and that works for keeping the watchdog fed when there is no other activity. You wouldn't want to feed the watchdog by default because that would defeat its purpose when the loop is actually supposed to be doing something and fails to service the watchdog.

lonerzzz on 29 Aug 2017

In the sketch above the loop() function is empty. I had to search long time to find how to avoid this error message. The idea is to apply a default watchdog feed in order to avoid this error reporting when the loop() function is empty. I think it wouldn't defeat the purpose of the watchdog as code instructions inside a loop() function are executed sequentially thus if the code hangs up inside this loop() function the default watchdog feed using the vTaskDelay() will not be triggered.

orcema on 30 Aug 2017

👍1

@orcema I understand where you are going but what is the delay that gets chosen? It will vary per application and you wouldn't want to put a delay in that negatively impacts the ability of a particular application to meet its processing needs. Having sufficient delay in an empty loop to prevent watchdog triggering means slowing down the application for other use cases. This is especially bad for lightweight tasks that have to execute frequently.

I would also like to understand if @tobozo is looking for the same thing.

lonerzzz on 30 Aug 2017

@lonerzzz I have an ESP32-WROVER-KIT too and was just curious to know why a loop() would be empty (better power management?).

tobozo on 30 Aug 2017

@tobozo Sorry if I tell you something you already know, but I will go into detail just for clarity. Let me know if you are asking something different than what I answer.

As part of the Arduino standard implementation across the different MCUs, the underlying framework always calls a loop function for the application-specific code to be able to periodically perform its own steps. In some situations, the loop function is not required by the application, but is required to match the standard Arduino API of a setup() function and a loop() function.

Having the loop function gives no benefits of its own. It simply allows the underlying implementation time to do its own work and allows an Arduino application to get CPU time as well. The loop exists to provide a common implementation that is compliant with the standard pattern of the Arduino across the different MCUs. Because the ESP-32 implementation is sitting on top of FreeRTOS, the RTOS is checking for tight loops and can result in the watchdog timeouts. Hence we need to have the vTaskDelay() calls if we are not writing code that makes use of the loop() method.

lonerzzz on 30 Aug 2017

@lonerzzz A delay of 10ms is suffisent to avoid the error message and i guess that a delay of 10ms shouldn't be a problem for any arduino sketch.

orcema on 31 Aug 2017

@orcema I would have to disagree with that. It completely depends on the application what the tolerance to such a delay would be. If driving a display for example, such a delay could easily become noticeable if regular updates needed to be processed. On top of that, once the delay is automatically added, any application that cannot support such a delay would require removing it from core code.

lonerzzz on 31 Aug 2017

@lonerzzz Thus i think this vTaskDelay() has to be managed individually by each arduino sketch.

orcema on 1 Sep 2017

@orcema I would agree with managing how it is used per sketch, the question is in what manner. We would either have to explicitly add vTaskDelay as is indirectly documented or augment the Arduino definition with something to set a specified delay or no delay in the loop, possibly as part of the setup. I think that this would be seen as a variation from the standard Arduino approach so would required getting buy in. I could see this method but that is still not great in terms of being visible to people just getting started.

lonerzzz on 1 Sep 2017

@lonerzzz Maybe the solution would be to define a global variable in Arduino.h and set its default value to 10. As you suggested this value could be updated to the needed value in the setup function. This way the arduino standard would be respected and for most sketches the default value would be ok.

orcema on 1 Sep 2017

@orcema you also can just add some delay in your sketch loop() without change core files, like:

void loop(){
    delay(2000);
}

Trying reproduce with others sketches but looks like this just occur with this one

copercini on 1 Sep 2017

@copercini with my board the ESP32-WROVER-KIT it happens for every arduino sketch having an empty loop function. Even if the loop function is not empty but holds only an conditional statement "IF" the error shows up.
For me is ok to add this vTaskDelay manually in each sketch but for a beginner this would be non Arduino standard and most beginner will struggle to find the origin of this error.

orcema on 1 Sep 2017

I don't know what is going on here, but I can tell you that I will not add vTaskDelay(10) after each loop. For you to trigger WDT in the loop, you have to be running as IDF component and have WDT enabled for the Idle task on Core1. Those are disabled for Arduino in order to give to most Arduino-like behavior under FreeRTOS. You can add vTaskDelay(10) to your loop if you need it and achieve the same result.

10ms between each loop is ages in processor time ;) 2.4 million wasted CPU cycles, to be exact. Nothing else is running on Core1 ;)

me-no-dev on 2 Sep 2017

@me-no-dev if the WDT is disabled for the Idle task on Core 1, what happens if the code hangs up?

orcema on 2 Sep 2017

The same thing that happens on any AVR and STM ;) nothing. I do not say that this is the correct way, but that is tha way of Arduino. Still you have the option to run through IDF and delay/yield in the loop. So you are not left hanging.

me-no-dev on 2 Sep 2017

This is a bug. It is caused by the WIFI Thread coming in at the same priority as the Loop function.

tuskiomi on 10 Sep 2017

wifi thread and loop run on different processors

me-no-dev on 10 Sep 2017

Hello guys,

So,finally what we should use instead of vTaskDelay() to feed the watchdog.
Actually,I am also facing same issue as can see logs below:

Task watchdog got triggered. The following tasks did not feed the watchdog in time:
Tasks currently running:
CPU 0: wifi
Task watchdog got triggered. The following tasks did not feed the watchdog in time:
Tasks currently running:
CPU 0: wifi
Task watchdog got triggered. The following tasks did not feed the watchdog in time:
Tasks currently running:
CPU 0: wifi
Task watchdog got triggered. The following tasks did not feed the watchdog in time:
Tasks currently running:
CPU 0: wifi

PatelKishanJ on 25 Dec 2017

👍2

am also getting same thing, I tried using delay but did not solved
what is the solution for that, other then vTaskDelay

Ningappaa on 19 Mar 2018

hello,
I could not resolved this issue.
But we can do one thing and that is change some set up in menuconfig.
Means there is one option available to do operation when watchdog-got triggered.
If we can restart the device whenever watchdog will trigger we can atleast retain to hang-up the device.

Regards,
Kishan Patel.

PatelKishanJ on 19 Mar 2018

thanks for response ,
is there any option stop watchdog without restarting the device.

On 19 March 2018 at 17:34, jenextech notifications@github.com wrote:

hello,
I could not resolved this issue.
But we can do one thing and that is change some set up in menuconfig.
Means there is one option available to do operation when watchdog-got
triggered.
If we can restart the device whenever watchdog will trigger we can atleast
retain to hang-up the device.

Regards,
Kishan Patel.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/espressif/arduino-esp32/issues/595#issuecomment-374189587,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjD5Drh7pcSwVqDU9CZVGQE2MAZrrou-ks5tf57jgaJpZM4PD_Mh
.

Ningappaa on 19 Mar 2018

hello, another possible cause for this going off is a delay in i2c response time. i have not tested with SPI, but i suspect it may be the same.

tuskiomi on 19 Mar 2018

hello,
am not using i2c or SPI

On 19 March 2018 at 21:45, tuskiomi notifications@github.com wrote:

hello, another possible cause for this going off is a delay in i2c
response time. i have not tested with SPI, but i suspect it may be the same.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/espressif/arduino-esp32/issues/595#issuecomment-374270196,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjD5DvY2cnDw3HaMvK6ohQthM4xft53Zks5tf9mMgaJpZM4PD_Mh
.

Ningappaa on 20 Mar 2018

In the MAKE -menuconfig you can turn off the thread watchdog. I'm not sure if there is a dynamic solution.

tuskiomi on 23 Mar 2018

Anyone who still want to avoid that error should try
adding these three line to your continuous rtos function,

TIMERG0.wdt_wprotect=TIMG_WDT_WKEY_VALUE;
TIMERG0.wdt_feed=1;
TIMERG0.wdt_wprotect=0;

And add this header

#include "soc/timer_group_struct.h"
#include "soc/timer_group_reg.h"

akshar001 on 17 Aug 2018

👍6 🎉3

Anyone who still want to avoid that error should try
adding these three line to your continuous rtos function,

TIMERG0.wdt_wprotect=TIMG_WDT_WKEY_VALUE;
TIMERG0.wdt_feed=1;
TIMERG0.wdt_wprotect=0;

And add this header
#include "soc/timer_group_struct.h"
#include "soc/timer_group_reg.h"

This is the proper solution. The cause is arduino builtins not reporting to the watchdog.
If you're having issues with this, it means that some code/function is making the CPU wait too long. for the most part, the user has limited ability to do this.

tuskiomi on 23 Sep 2018

How i adding these three line to your continuous rtos function?

TIMERG0.wdt_wprotect=TIMG_WDT_WKEY_VALUE;
TIMERG0.wdt_feed=1;
TIMERG0.wdt_wprotect=0;

danielfabro on 23 Sep 2018

Anyone who still want to avoid that error should try
adding these three line to your continuous rtos function,

TIMERG0.wdt_wprotect=TIMG_WDT_WKEY_VALUE;
TIMERG0.wdt_feed=1;
TIMERG0.wdt_wprotect=0;

And add this header
#include "soc/timer_group_struct.h"
#include "soc/timer_group_reg.h"

The watchdog is still getting triggered after I added this in the main loop. I am using the Arduino SDK so don't have access to the RTOS functions. But what I am more concerned about is the module not getting reset. The watchdog is supposed to reset the module. If that;'s not happening then the watchdog is of no use.
What do I have to do the make the watchdog reset the device?

PriyankPa on 28 Dec 2018

Arduino does have access to all IDF things, but is built with WDT disabled for Core 1 (where loop runs). This is made on purpose to allow code written for other platforms to run on ESP32 without constantly causing resets. If you want to trigger WDT, then spin a task on core 0

me-no-dev on 28 Dec 2018

Looks that this bug is still exists and if you use BLE & wifi together board will drop to infinite WDT errors loop after random time:
Task watchdog got triggered. The following tasks did not reset the watchdog in time:

IDLE (CPU 0)
Tasks currently running:
CPU 0: wifi
CPU 1: IDLE
Task watchdog got triggered. The following tasks did not reset the watchdog in time:
IDLE (CPU 0)
Tasks currently running:
CPU 0: wifi
CPU 1: IDLE
And this continues for ever.
I understand that there is some bugs left at wifi code what can cause hangups with BLE. But I like to repeat @PriyankPa question that why TWDT does not reset board? WDT without reset function is quite pointless so my question is that how I will get TWDT to do reset when it is triggered? I use Arduino ide.

burner- on 5 Jan 2019

WDT is now enabled to reset the board (by default on Core0 only, but can be enabled for Core1 or the loop task also). Update your Arduino and try again ;)

me-no-dev on 5 Jan 2019

https://github.com/espressif/arduino-esp32/commit/f49c854ff3d2917f54c138339c729bab03ff574a#diff-2f6c51c0d9a7c54fe420b345f9b6f61eR336

me-no-dev on 5 Jan 2019

Looks that this bug is still exists and if you use BLE & wifi together board will drop to infinite WDT errors loop after random time:
Task watchdog got triggered. The following tasks did not reset the watchdog in time:

IDLE (CPU 0)
Tasks currently running:
CPU 0: wifi
CPU 1: IDLE
Task watchdog got triggered. The following tasks did not reset the watchdog in time:

IDLE (CPU 0)
Tasks currently running:
CPU 0: wifi
CPU 1: IDLE
And this continues for ever.
I understand that there is some bugs left at wifi code what can cause hangups with BLE. But I like to repeat @PriyankPa question that why TWDT does not reset board? WDT without reset function is quite pointless so my question is that how I will get TWDT to do reset when it is triggered? I use Arduino ide.

Same here ! did you find any solutions ?

MohRaouf on 6 Jan 2019

@MohRaouf did you just skip what I wrote above?

me-no-dev on 6 Jan 2019

@me-no-dev No i didn't, but nothing did work for me, WDT is getting triggered after about 30 mins on Core 0 which is running the WiFi and BLE, the problem that it doesn't reset the board, but hang the code on the Error message.

however, i tried to set or simulate a WDT interrupt manually but it runs on Core 1 which doesn't have any issues. so i think i'll give a try to spin my WDT task on Core 0.
i use Arduino SDK with Visual Studio.

MohRaouf on 6 Jan 2019

with latest master, wdt reset is enabled and is active on core 0. If you want it to reset also for core1, you can call enableCore1WDT();

me-no-dev on 7 Jan 2019

@me-no-dev
i updated the ESP libraries but still Reset doesn't happen when the Watchdog get triggered.

MohRaouf on 7 Jan 2019

are you using the package manager? Through the IDE? If so, see here: https://github.com/espressif/arduino-esp32/blob/master/docs/arduino-ide/windows.md

me-no-dev on 7 Jan 2019

I have this as my loop:

void loop(void) {
  delay(100);
}

I still get

E (15174) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (15174) task_wdt:  - IDLE1 (CPU 1)
E (15174) task_wdt: Tasks currently running:
E (15174) task_wdt: CPU 0: IDLE0
E (15174) task_wdt: CPU 1: loopTask

I disabled the WDT on CPU 1 and that fixes the problem for now, but is delay not sufficient to keep the IDLE task from choking?

nevercast on 18 Jan 2019

delay calls the FreeRTOS vTaskDelay so that should be plenty to feed the watchdog... I can not replicate with the following example (in Arduino IDE)

void setup() {
  enableCore1WDT();
}

void loop() {
  delay(100);
}

me-no-dev on 23 Jan 2019

@me-no-dev Hi, im having the same problem. I understand that the wtd is disable for Core 1, but how can i disable wdt from core 0 too?
Thank you

JoaquinPine on 22 Mar 2019

Oops, same issue here too!

Task watchdog got triggered. The following tasks did not reset the watchdog in time:
 - IDLE (CPU 0)
Tasks currently running:
CPU 0: wifi
CPU 1: IDLE

I tried every solution that I could think of. I tried varying the length of some loops. Then I tried this suggested fix/workaround - both with TIMERG0 and TIMERG1. I tried calling the (wdt feed) code from different places like the void loop() and before, after execution of some other loops etc.

TIMERG0.wdt_wprotect=TIMG_WDT_WKEY_VALUE;
TIMERG0.wdt_feed=1;
TIMERG0.wdt_wprotect=0;

The ESP32 works great for a few minutes ( mostly less than 5-10 mins) and then the watchdog triggers as shown above!

The most crazy workaround I tried was to call a simple task using a Task Scheduler to feed the watchdog. Lol, that didn't work either :) I am using Arduino IDE so that limits the options I have. Does anyone have a reliable fix for this issue?

m-menon on 28 Mar 2019

@m-menon it's because this things were not executed just send here the function where you have placed this three lines

akshar001 on 8 Apr 2019

Emmm, long story. But what is the proper solution ? I added vTaskDelay(10), but not useful.

Herwey on 22 Apr 2019

Guys, you have API to enable/disable WDT on each core, plus an extra function if you want to watch just the loop() task.
https://github.com/espressif/arduino-esp32/blob/master/cores/esp32/esp32-hal.h#L76-L91

As example, when SPIFFS is formatting, Arduino temporarily disables WDT on Core0 in order to not trigger and reboot the ESP.
https://github.com/espressif/arduino-esp32/blob/master/libraries/SPIFFS/src/SPIFFS.cpp#L73-L75

All headers are public, please take the time to read them :)

me-no-dev on 23 Apr 2019

👍2

Hi, i see strange things on WDT .. on some boards it can not reboot .. I don't know why ...

ESP-WROOM-32 is all same but not all do same
I've all two core 0 and core 1 wdt enabled

my log :

[SISTEMA] Inizio loop.

[INFO] Led backgroud Full
( at this start my loop while(true); )
E (36859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (36859) task_wdt: - IDLE1 (CPU 1)
E (36859) task_wdt: Tasks currently running:
E (36859) task_wdt: CPU 0: IDLE0
E (36859) task_wdt: CPU 1: loopTask
E (51859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (51859) task_wdt: - IDLE1 (CPU 1)
E (51859) task_wdt: Tasks currently running:
E (51859) task_wdt: CPU 0: IDLE0
E (51859) task_wdt: CPU 1: loopTask
E (66859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (66859) task_wdt: - IDLE1 (CPU 1)
E (66859) task_wdt: Tasks currently running:
E (66859) task_wdt: CPU 0: IDLE0
E (66859) task_wdt: CPU 1: loopTask
E (81859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (81859) task_wdt: - IDLE1 (CPU 1)
E (81859) task_wdt: Tasks currently running:
E (81859) task_wdt: CPU 0: IDLE0
E (81859) task_wdt: CPU 1: loopTask
E (96859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (96859) task_wdt: - IDLE1 (CPU 1)
E (96859) task_wdt: Tasks currently running:
E (96859) task_wdt: CPU 0: IDLE0
E (96859) task_wdt: CPU 1: loopTask
E (111859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (111859) task_wdt: - IDLE1 (CPU 1)
E (111859) task_wdt: Tasks currently running:
E (111859) task_wdt: CPU 0: wifi
E (111859) task_wdt: CPU 1: loopTask
E (126859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (126859) task_wdt: - IDLE1 (CPU 1)
E (126859) task_wdt: Tasks currently running:
E (126859) task_wdt: CPU 0: IDLE0
E (126859) task_wdt: CPU 1: loopTask
E (141859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (141859) task_wdt: - IDLE1 (CPU 1)
E (141859) task_wdt: Tasks currently running:
E (141859) task_wdt: CPU 0: IDLE0
E (141859) task_wdt: CPU 1: loopTask
E (156859) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (156859) task_wdt: - IDLE1 (CPU 1)
E (156859) task_wdt: Tasks currently running:
E (156859) task_wdt: CPU 0: IDLE0
E (156859) task_wdt: CPU 1: loopTask
E (171859) task_wdt: Task watchdog got triggered. The following tasks did not reset the

asetyde on 23 Apr 2019

WDT on Core1 is DISABLED by default. Just enable it

me-no-dev on 23 Apr 2019

I use this :

// Enable WDT
enableCore0WDT(); enableCore1WDT();
esp_task_wdt_init(TWDT_TIMEOUT_S, false);

asetyde on 23 Apr 2019

why esp_task_wdt_init(TWDT_TIMEOUT_S, false); ?

me-no-dev on 23 Apr 2019

I've founded to set 15 sec timer of wdt, it's wrong ?

asetyde on 23 Apr 2019

don't need to call any other API than what Arduino exposes

me-no-dev on 23 Apr 2019

there are no API to set time of wdt , on ESP IDF yes , How can I use wdt ? I don't know how time I ve and I can not set my custom

My WDT not work as aspected , therefore I come back to custom wdt and this work ... I can not now test about this issue but I do soon .

At now this work always :

void ICACHE_RAM_ATTR osWatch(void) {
unsigned long t = millis();
unsigned long last_run = abs(t - last_loop);
if (last_run >= (OSWATCH_RESET_TIME * 1000)) {
// save the hit here to eeprom or to rtc memory if needed
Serial.println("------------WDT RESET NEED-----------");
ESP.restart(); // normal reboot
}
} // wdt

asetyde on 23 Apr 2019

My error as below:
E (68253) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (68253) task_wdt: - IDLE0 (CPU 0)
E (68253) task_wdt: Tasks currently running:
E (68253) task_wdt: CPU 0: task1
E (68253) task_wdt: CPU 1: task2
E (73253) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (73253) task_wdt: - IDLE0 (CPU 0)
E (73253) task_wdt: Tasks currently running:
E (73253) task_wdt: CPU 0: task1
E (73253) task_wdt: CPU 1: task2
So what should I do?? Thanks in advance !

Herwey on 24 Apr 2019

what are you doing in task1 that is causing WDT?
from what you posted is not clear at all...

me-no-dev on 24 Apr 2019

My error as below:
E (68253) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (68253) task_wdt: - IDLE0 (CPU 0)
E (68253) task_wdt: Tasks currently running:
E (68253) task_wdt: CPU 0: task1
E (68253) task_wdt: CPU 1: task2
E (73253) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (73253) task_wdt: - IDLE0 (CPU 0)
E (73253) task_wdt: Tasks currently running:
E (73253) task_wdt: CPU 0: task1
E (73253) task_wdt: CPU 1: task2
So what should I do?? Thanks in advance !

Herwey , watchdog reboot your ESP32 or not ?

asetyde on 24 Apr 2019

Hi @asetyde, watchdog didn't reboot my esp32. I created two in core0 and core1, the n run at same time.
xTaskCreatePinnedToCore( task1, "task1", 102420, &camera_config, 6, NULL, 0 );
xTaskCreatePinnedToCore( task2, "task2", 102420, &camera_config, 6, NULL, 1 );

Herwey on 24 Apr 2019

Ook the problem is similar as mine, Esp32 not reboot and I don't know why !

I use enableWDT on core 0 and 1 , I simply put loop on setup function and system stay blocked .. it's strange .. same code on old devices work .. I suspect if old library 1.0 1.0.1 set something inside ESP32 .. it can be but I can't find bug visible on my level of programming

asetyde on 24 Apr 2019

xTaskCreatePinnedToCore( task1, "task1", 102420, &camera_config, 6, NULL, tskNO_AFFINITY );
xTaskCreatePinnedToCore( task2, "task2", 102420, &camera_config, 6, NULL, tskNO_AFFINITY );
Maybe this is ok. But the speed is not as fast as before. :D

Herwey on 24 Apr 2019

xTaskCreatePinnedToCore( task1, "task1", 102420, &camera_config, 6, NULL, tskNO_AFFINITY );
xTaskCreatePinnedToCore( task2, "task2", 102420, &camera_config, 6, NULL, tskNO_AFFINITY );
Maybe this is ok. But the speed is not as fast as before. :D

Now reboot ? therefore if yes in enableWDTCore0 .. seems something not work

asetyde on 24 Apr 2019

xTaskCreatePinnedToCore( task1, "task1", 102420, &camera_config, 6, NULL, tskNO_AFFINITY );
xTaskCreatePinnedToCore( task2, "task2", 102420, &camera_config, 6, NULL, tskNO_AFFINITY );
Now , esp32 works fine , no error, but speed is slower.

Herwey on 24 Apr 2019

@me-no-dev if I use this

        while (WiFi.status() != WL_CONNECTED)
        {
            ledcommand(1, 0, 0, 0, 0, 2, false, true, 250, 0, 0);
            delay(500);
            counter++;
                Serial.print("@");
            if (counter > 12)
            {
                break;
            }
            ledcommand(1, 1, 0, 0, 0, 2, false, true, 250, 0, 0);
            delay(500);
        }

using delay can be disturb watchdog ? because at now ..after some times .. on this function esp freeze

asetyde on 24 Apr 2019

problem is in that ledcommand code :) don't ask "where". You did not provide the code :P

me-no-dev on 25 Apr 2019

I can send you code, but not there, public. Do you ve an email address ?
I see watchdog not bale to reboot device .. i don't why ... my engeneers about electric scheme not find none, therefore is software .. but is possibile ??

asetyde on 25 Apr 2019

This thread has been very helpful. I have been running into watchdog errors (then reboot) using an ESP32 and multicore tasks with the Arduino IDE. My application puts a task onto core 0 that needs to cycle 5000+ times/second. It is processing interrupts from an accelerometer and increments a counter. When there are fewer interrupts or only the counter is getting updated then core 1 functions don't see the global variable updates and/or I get crashes having to do with the watchdog timer. I had to do two things from this thread to get high throughput and stability. The first was Akshar001's suggestion to add the following to the task:

TIMERG0.wdt_wprotect=TIMG_WDT_WKEY_VALUE;
TIMERG0.wdt_feed=1;
TIMERG0.wdt_wprotect=0;

And add this header:

include "soc/timer_group_struct.h"

include "soc/timer_group_reg.h"

That made it stable, but I still had issues with global variables being updated, so I had to add a delay to the task. Using delay(1) was too long, as were other forms of 1ms delays. So, I just put a microsecond loop in like this:

unsigned long thedelay;
thedelay = micros() + 100;
while (micros() < thedelay) {
}

This provides a .0001 second delay and allows the global variables to be updated. With this setup, I am reliably getting 10,000 cycles a second on the task code in core 0. That works for my application.

AllDigital33 on 12 Jul 2019

Hello,

I faces some issues when try to blink led without using delay() and used "if ((millis() - lastReport) >= 1000)" like this on the core 0 with the use of xTaskCreatePinnedToCore() function. It throws the errors

E (10169) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (10169) task_wdt: - IDLE0 (CPU 0)
E (10169) task_wdt: Tasks currently running:
E (10169) task_wdt: CPU 0: get reading
E (10169) task_wdt: CPU 1: IDLE1
E (10169) task_wdt: Aborting.
abort() was called at PC 0x400d5bd7 on core 0

I am also running core 1 to print "hello world" in the serial monitor.

Please, anyone, help to understand it.