-
Notifications
You must be signed in to change notification settings - Fork 26
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
STM32L5 Crash while reading SD card or calling .end() #83
Comments
Fixes stm32duino#83 Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
OK this did fix the issue with
And here's the logs I get. Note that it resets itself (the watchdog does this, I think) but without the watchdog, it will just hang.
I'm running the latest pull request and board defs for the STM32L5 DK. I can share if you want but it's right from here: |
Using your sketch, I have no crash. Running ~10min. last part of the log19:09:42.404 -> Loop count: 137 |
Welp, the issue must be on my end then, I'll push some buttons until it works. Thanks for your help |
I'm experiencing an issue with the SD card reader and the STM32L5. This is using the STM32 DK board referenced here:
stm32duino/Arduino_Core_STM32#2694
The issue is that reading from the SD card causes the microcontroller to either freeze, or crash and restart if the watchdog is enabled (i have watchdog enabled).
To Reproduce a Crash
And here's what the serial log looks like as this runs.
So it appears to be crashing every few SD card reads - it's really unpredictable. Sometimes it goes for a while and sometimes it will only do 2-3 loops before there's a crash.
Here's how I build an upload
And to reproduce a crash even simpler:
I've tried a few things, including changing the heap size and tweaking some timing but I can't seem to figure out why it's doing this. If I have it dump crash information, it looks like this. not sure if helpful.
I've tried different SD cards, of different sizes and can't seem to find a pattern. It does this with all of them. It is especially reproducible by calling the .end() method.
The text was updated successfully, but these errors were encountered: