-
-
Notifications
You must be signed in to change notification settings - Fork 346
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
intermittent watchdog messages on esp32/esp32c3 #2914
Comments
All changing in #2913 so should disappear. |
@pljakobs can you check if the latest |
@pljakobs I will close the issue for now. If it happens again in the latest |
By way of explanation, the message appears because the task watchdog is created for the |
built my current version using the current sming develop branch fails an assert on the esp32c3:
same on the esp32:
|
@mikee47 I can't reopen this since I can only re-open issues that I have closed myself. I don't know if you get a notification on a closed issue, so: ping |
That assert indicates the queue hasn't been created yet: I'll try Basic_Wifi on the esp32c3, see what I can dig up. |
So I've tried the Basic_Wifi sample on an esp32c3 and runs without issue. We need to know what called If you rebuild with |
I can't reproduce the issue but I suspect something is trying to post to the Sming event queue before it's been created, probably during network initialisation. Can you try this patch to
|
will try, I have not looked at this more deeply yet (day job taking excessive cycles) - it happens right after initializing ConfigDB, but I will need to debug it more. |
with this startup.cpp, the issue persists
|
Going to need a reproducible sample or backtrace to diagnose this further. |
so it took me a while to set this up, broke out the jtag interface. Here's what I got:
I'm unsure that this really shows the issue since this is an unconfigured chip, meaning it does not connect to the wifi yet but should open it's AP for configuration - which it doesn't seem to do. |
Using GDB on the esp32 requires the
Should be able to break out then run
NB. I'm forcing this exception by patching NOTE: For some reason the esp32c3 isn't responding to GDB over serial (esp32 is fine). I'm not sure why, but it's annoying. |
OK, so at least with my esp32c3 dev. board I suspect that the auto-reset lines (RTS/CTS) on the serial port aren't being set correctly with GDB (both should be low). Can't find any gdb commands to override that behaviour, closest is flow control (which is disabled). Here's a workaround:
Replacing the IP as required. |
not sure how helpful this is, seems that gdb cannot identify the error?
but, here's the resulting backtrace:
|
So this is a different error to the one you reported above. The inconsistency suggests memory corruption of some sort. |
let's pause this for a bit, there's currently too much going on otherwise, I can't fully concentrate. |
@pljakobs when you have more time make sure to get the latest |
I'm getting
intermittently.
Sometimes, that's followed by a restart, but I can't see any reason yet.
The text was updated successfully, but these errors were encountered: