-
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
SPIFFS filesystem problem #7634
Comments
we added a new partition in order to have ESP-Insights working. That resulted in 64K less FS partition. We need to update all labels still |
Is this the reason why when we update from 2.0.5 to 2.0.6 it always reformat my SPIFFS partition ?? If yes is there a way to avoid that because it errase all saved data doing that!! Thanx a lot! |
@Speedy2k the one thing that comes to mind is to have a custom partitions.csv in your sketch folder that does not have that extra partition and extends the SPIFFS to the previous value (more or less copy the partition scheme from 2.0.5) |
@me-no-dev I encountered errors about core dump partition. I have a question - what if I OTA update my boards that doesn't have this partition? Is it needed or can I continue without using it (use older partition format)? What are benefits? I hope it won't cause any issues once we move to ESP-IDF 5.X based Arduino core? |
It is required by esp-insights. If you aren't using that, then you don't need the crash dump partition. OTA updates will work just fine, the size of the firmware partitions has not changed. |
Board
LILYGO TTGO T-Call V1.4 SIM800L
Device Description
LILYGO TTGO T-Call V1.4 SIM800L on breadboard
Hardware Configuration
ND
Version
latest master (checkout manually)
IDE Name
Arduino IDE
Operating System
Windows 11
Flash frequency
80Mhz
PSRAM enabled
no
Upload speed
921600
Description
Incorrect file size after creation with ESP32 FS tool. The problem only occurs with core version 2.0.6.
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: