-
Notifications
You must be signed in to change notification settings - Fork 68
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
LITTLEFSFS::begin() unexpected behavior #27
Comments
@robcazzaro |
I used the code at the end of this message, inside your LITTLEFS_test() example In order to get the messages below, I had to add the delay(500), otherwise it looks as if your code was running in a separate thread from the Arduino code, and my Serial.print() were overwritten. That is purely a Serial.print() timing problem: I built a different version where I saved the values and printed those at the end, and that showed 0, 0, 1, 1 I get the following output
As you can see, using begin(false) on a unintialized/invalid SPIFFS it returns 0, as it should, and doesn't initialize the SPIFFS. While the second call with begin(true) returns 1, and formats the SPIFFS. There were two problems masked by the timing issue.
|
Hi, the messages like "Corrupted dir pair at {0x0, 0x1} E (4349)" are from lower level of the driver. |
Agreed. This was mostly a misunderstanding on my side, not a real issue in your code. Thanks again for adding the multiple SPIFFS functionality |
@robcazzaro |
Thanks! |
Relatively minor issue. The code behaves as expected, but doesn't return the right value
I used the following code in the setup() part of my project
I expected to see the "Init failed! AutoFormatting." message on my terminal window, instead I get
It actually auto-formats the SPIFFS partition, just doesn't return false, so the code doesn't know it's been auto formatted. In some cases, the code needs to know if the SPIFFS area has been auto formatted, so would be nice to fix
The text was updated successfully, but these errors were encountered: