-
Notifications
You must be signed in to change notification settings - Fork 306
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
[develop-v3] Core panics after connection to AP #588
Comments
Could you decode the backtrace? |
I don't use config mode, so I did not tested it yet. What happesn, if you upload a |
@euphi Works like a charm and solves at least my problem for now. But of course not the problem in general. @bertmelis I am not that skilled. Is there a simple way to do it? I am working with PlatformIO on Windows. A quick research brought nothing up. |
@EinfachArne Yes this is a big gap in PlatformIO. There is still missing decoding of back traces.
Hope this helps. |
You could also do it manually (or create a Windows batch file):
if you run |
Thank you guys! I think I got it. :) Ok, for the record: Tested on Wemos Lolin32 V1.0.0 and ESP32 DevModule - both show the same result. This is based on the DevModule:
Decoded:
|
Oh.. doesn't look good. Maybe a heap corruption? |
Hi all, I am experiencing the same thing using an espduino-32, platformio and ubuntu 18.04.
Demangled :
I did go to
and verified the ssid string at that point is empty, not sure if that is causing the later crash. I will try to debug it and see if I can get to the bottom. If you have any suggestions on what to look for please let me know. Thanks. |
I reproduced this in the Arduino IDE with just the WiFi library. This is not a Homie bug, it is some bug with the WiFi library and esp32, and setting up a STA_AP. Whenever you re-upload a sketch with the same AP SSID string, it will crash. The only work around I have found so far is to provide a new AP name prior to uploading the sketch. |
I created a pull request for a workaround of this issue. Disabling WiFi persistence will get rid of this problem, but may slightly increase the WiFi connection time. The memory (or at least the part where the WiFi persistence data is stored) needs to be wiped beforehand if a firmware with WiFi persistence enabled has already been used prior. |
Hey,
everything works fine until I connect to my ESP32 via WiFi. After that I keep getting the following error message in an endless loop:
After I disconnect the core stops to panic but that makes it impossible to upload a config.
I used the current development version of Homie-V3 on a Wemos Lolin32 V1.0.0.
Any ideas what the cause could be?
The text was updated successfully, but these errors were encountered: