-
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
Serial flashing big spiffs fails (IDFGH-8905) #10323
Comments
Hi @higaski. We are sorry for this issue. I think this is the same as espressif/esptool#795 and it is not related just to SPIFFS. All flashing accessing >= 16MB area are affected. |
Yeah I figured that the python script doing the writing doesn't really care if it's code, data or 🍌 s. 😄 You're right, looks like a duplicate. And I even managed to open the issue in the wrong repo... sry for that. |
Octal flash support tested up to 32MB. Quad flash support is limited to 16MB at this moment. Closes #795 Closes #745 The next release will solve espressif/esp-idf#10323 as well.
This is just a note that the next esptool release (v4.5) should address this. And it also improves the error message in case of |
@dobairoland |
@robbietree8 It depends on the HW. I don't have anything like that right now. If I'm not mistaken, Espressif sells ESP32-S3s only with Quad flash and 32 MB Octal flash right now. |
@dobairoland we have custom board made with 32MB quad flash. |
esptool v4.5 has been released and it is included with ESP-IDF v5.0+ after you re-run the install script. |
Octal flash support tested up to 32MB. Quad flash support is limited to 16MB at this moment. Closes espressif/esptool#795 Closes espressif/esptool#745 The next release will solve espressif/esp-idf#10323 as well.
Answers checklist.
IDF version.
v5.0
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
What is the expected behavior?
Writing big spiffs images (>16MB?) using
idf.py flash
doesn't seem to work yet.Here's the partition table I'm currently using
I've attached a log of some attempted writes below. The percent-mark it keeps failing on seems to depend on the amount of actual data inside the image. Having a 20MB spiffs image with only 2.9MB of actual data fails at 100% whereas an image with the same size but 13MB of data in it fails way earlier...?
What is the actual behavior?
20MB spiffs image, 2.9MB of actual data in it
20MB spiffs image, 13MB of data in it
Steps to reproduce.
Build or installation Logs.
No response
More Information.
No response
The text was updated successfully, but these errors were encountered: