-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
FatFS corruption in SDK 5.2.1 [bug] (IDFGH-12465) #13480
Comments
Hi, thank you for the report. |
If you create 2 GPTIMER with this priority and this being tirggered even in IRAM with saving to flash and using a SPIRAM memory this will create a panic (boot reason 5) and corrupting the flash. we arent able to solve it yet. |
We can recreate all the time the bug, we are tracking it right now, the panic is o hard that the debug doesnt even show anything, just crash and reboot. |
Hi. Could you please share a zip file with the folder of your project which can be build to reproduce the issue? Please also set log level to verbose in the menuconfig and share the output here as well. Thank you. |
@filzek |
Sure, I understand. We're currently focused on ensuring that SDK version 5.2.1 operates flawlessly. We're close to completing all necessary adjustments and fixes. Once we're done, we will prepare and share a split version of the firmware code, which includes the fatfs corruption issue, for your review. Thank you for your patience and understanding. |
@AxelLin we thing we can do it in about 10 days so far. |
In sdk 5.2.2 we are testing now, issue have almost solved but still happen on 5.2.1, now we are testing again with forcing ble, wifi, udp, and all channes requests with massive gpio isrs acting over while saving small data and large data, lets see if it survives |
Answers checklist.
General issue report
Using SDK release v5.2.1, the FatFS with Wearleaveling when concurrence happen in ISR, GPTIMER, Console or UART exchange information and File Read/Write the partition get full corrupted, we will also open a ticket for it.
The text was updated successfully, but these errors were encountered: