-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wifi.connect() causes esp32c3 to reboot if log verbosity is set to "Info" #3660
Comments
I did some more research. This issue is common to all ESPs. ESP32 has the same error. Log for ESP32 on IDF 5.0.2
EDIT.
For esp32c3 this trick does not work. |
I can confirm that I can reproduce this on an esp32c3 at least; I will investigate. |
Fixes the crash reported in nodemcu#3660.
@serg3295 This crash seems to be another stack overrun. Increasing the system event task stack size resolves it for me. Are you able to take it for a spin on your end too? The branch is here (I never remember how to fetch a PR 😅). Make sure you remove your old |
I can confirm that PR #3665 solves this issue for esp32-c3. |
Great, thank you for testing! I'll get that merged right away. |
Fixes the crash reported in #3660.
Expected behavior
The ESP does not reboot after connecting to Wi-Fi if the "Log output" → "Default log detail" is set to "Info".
EDIT.
Added Log for succsesful wifi connection.
"Log output" → "Default log detail" -> "Warn"
IDF v5.2.2, console JTAG
Log for succsesful wifi connection
Actual behavior
If
Component config → Log output → Default log verbosity ->
"Info" is set, the ESP reboots immediately after connecting to WiFi.Everything works until this command.
If the default log verbosity level is set to "Warning", the ESP connects to Wi-Fi and no reboot occurs. Because LOGI is not executed.
Сurrent settings are:
(Top) → Component config → ESP System Settings → Channel for console output -> (X) Default: UART0
Channel for console secondary output (No secondary console)
The error occurs with both UART and JTAG console. Also it occurs on IDF 5.2.2
Crash log
Added crash log on IDF 5.2.2 and Channel for console output -> JTAG
Crash log on IDF 5.2.2
Test code
NodeMCU startup banner
Startup banner
Hardware
esp32c3 supermini
The text was updated successfully, but these errors were encountered: