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
When running autoConnect() on an ESP32-Solo, the access point gets created, but the watchdog resets the board while waiting for a connection on the access point. This is the output:
*WM: HTTP server started
E (16471) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (16471) task_wdt: - IDLE0 (CPU 0)
E (16471) task_wdt: Tasks currently running:
E (16471) task_wdt: CPU 0: loopTask
E (16471) task_wdt: Aborting.
abort() was called at PC 0x400dc48b on core 0
Backtrace: 0x4008b4c0:0x3ffbe370 0x4008b6d1:0x3ffbe390 0x400dc48b:0x3ffbe3b0 0x4008420e:0x3ffbe3d0 0x4000bfed:0x3ffb1db0 0x40088f5d:0x3ffb1dc0 0x4008810f:0x3ffb1de0 0x4012ebb6:0x3ffb1e20 0x4011d079:0x3ffb1e40 0x40139703:0x3ffb1e60 0x400d3aae:0x3ffb1ea0 0x400d873a:0x3ffb1ef0 0x400d88c6:0x3ffb1f30 0x400d138f:0x3ffb1f80 0x400da6e7:0x3ffb1fb0 0x4008835d:0x3ffb1fd0
Rebooting...
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
This is because the yield() in startConfigPortal() line 237 does not work as intended. If I replace it with a vTaskDelay(10), it works.
The text was updated successfully, but these errors were encountered:
peterfoers
added a commit
to peterfoers/WIFIMANAGER-ESP32
that referenced
this issue
Jan 9, 2020
When running
autoConnect()
on an ESP32-Solo, the access point gets created, but the watchdog resets the board while waiting for a connection on the access point. This is the output:This is because the
yield()
instartConfigPortal()
line 237 does not work as intended. If I replace it with avTaskDelay(10)
, it works.The text was updated successfully, but these errors were encountered: