Skip to content
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

Closed
3 tasks done
filzek opened this issue Mar 27, 2024 · 9 comments
Closed
3 tasks done

FatFS corruption in SDK 5.2.1 [bug] (IDFGH-12465) #13480

filzek opened this issue Mar 27, 2024 · 9 comments
Labels
Status: Opened Issue is new

Comments

@filzek
Copy link

filzek commented Mar 27, 2024

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

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.

@espressif-bot espressif-bot added the Status: Opened Issue is new label Mar 27, 2024
@github-actions github-actions bot changed the title FatFS corruption in SDK 5.2.1 [bug] FatFS corruption in SDK 5.2.1 [bug] (IDFGH-12465) Mar 27, 2024
@haberturdeur
Copy link
Collaborator

Hi, thank you for the report.
Does this happen consistently or is it just sometimes? Could there have been a power fluctuation (it is known to cause FS corruption)?
If it's somewhat consistent, could you provide an example that demonstrates the problem?

@filzek
Copy link
Author

filzek commented Apr 4, 2024

If you create 2 GPTIMER with this priority
gptimer_config_t timer_config_us_up = {
.clk_src = GPTIMER_CLK_SRC_DEFAULT,
.direction = GPTIMER_COUNT_UP,
.resolution_hz = 1 * 1000 * 1000, // 1MHz, 1 tick = 1us
.intr_priority = 1,
.flags.intr_shared = false,
};

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.

@filzek
Copy link
Author

filzek commented Apr 4, 2024

Hi, thank you for the report. Does this happen consistently or is it just sometimes? Could there have been a power fluctuation (it is known to cause FS corruption)? If it's somewhat consistent, could you provide an example that demonstrates the problem?

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.

@adokitkat
Copy link
Collaborator

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.

@AxelLin
Copy link
Contributor

AxelLin commented May 6, 2024

@filzek
Any update for the issue and any feedback for the comment #13480 (comment) ?

@filzek
Copy link
Author

filzek commented May 6, 2024

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.

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.

@filzek
Copy link
Author

filzek commented May 6, 2024

@AxelLin we thing we can do it in about 10 days so far.

@AxelLin
Copy link
Contributor

AxelLin commented Jun 5, 2024

@AxelLin we thing we can do it in about 10 days so far.

@filzek Do you still hit this issue?

@filzek
Copy link
Author

filzek commented Jun 5, 2024

@AxelLin we thing we can do it in about 10 days so far.

@filzek Do you still hit this issue?

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

@filzek filzek closed this as completed Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Opened Issue is new
Projects
None yet
Development

No branches or pull requests

5 participants