Open roysG opened 2 years ago
I'm also getting same trouble:
(319187) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (319187) task_wdt: - IDLE (CPU 0)
E (319187) task_wdt: Tasks currently running:
E (319187) task_wdt: CPU 0: Gsm Connection
E (319187) task_wdt: CPU 1: loopTask
E (319187) task_wdt: Aborting.
abort() was called at PC 0x40127834 on core 0
Backtrace:0x40084505:0x3ffbea000x400950f1:0x3ffbea20 0x4009a3b1:0x3ffbea40 0x40127834:0x3ffbeac0 0x40085695:0x3ffbeae0 0x40084445:0x3ffe7030 0x400966df:0x3ffe7050 0x4011b521:0x3ffe7070 0x400fa773:0x3ffe7090 0x400faa72:0x3ffe70f0 0x400fd0e2:0x3ffe7150 0x400fd29c:0x3ffe7190 0x400fc0d5:0x3ffe71b0
ELF file SHA256: 0000000000000000
Rebooting...
Any thoughts, @SRGDamia1 ?
I'm not familiar with the ESP32's watchdog system, but the GSM connection can take a long time (1-5+ minutes, depending on the modem). This library blocks for the entire time. If your watchdog fires too quickly, you'll get a reset.
The first connection with a new modem or a new tower often takes longer than subsequent connections.
You can set a yield time like so:
This will make the Task WDT reset itself.
I am using in the latest version of TinyGsm. I am using sim7070g in esp32
As you can see in the logs in the bottom, the code is stack over and over again... Is there any solution for free the loop and restart the esp32. cause for now it looks that it stack the loop from running the rest of the code!
This are the errors i get: