-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Changes from SPIFFS to FS #2482
Changes from SPIFFS to FS #2482
Conversation
Small change for people that want to use the esp8266 GIT core where they changed from SPIFFS to LittleFS. Still uses SPIFFS format though but some variables changed. _SPIFFS_* => _FS_* See also: esp8266/Arduino@a389a99
Sorry, I just saw, that @TD-er already has a PR for this... which is more sophisticated...;) |
Could you also test my PR? I did find some strange timing issues while appending to a file. See esp8266/Arduino#5932 (comment) |
Just included the changes to be able to use GIT version, but never changed to the actual LitteFS format. |
Yep, that's why it hasn't been merged. |
Hmm, I could not imagine I did not think about that and looked at my PR. Lines 570 to 581 in 4cce923
ESPEasy/src/define_plugin_sets.h Lines 59 to 63 in 4cce923
So it is possible to swap it by using simply a define to force using LittleFS. |
yes to swap between the libraries, but as soon as However somethign does not seem to work, after installing this PR I get an exception:
|
I think you assume in your code changes that if I guess we would need to adapt this to
IMHO |
I don't see why option 2 should be a useful use case Or do you see a useful use case for option 2? |
yes, if you switch FS type, you need to reformat (and therefore reconfigure) all your units... with case 2 you just stay with the old FS, keep all your configs but use the new library and new ESP core... for me that's a point, as I have some 50 nodes running ;) EDIT: but yes, only 1 should be used and decided at compile time!! absolutely agree on that!! |
My idea was to only use LittleFS for builds which need a filesystem > 1 MB. |
this still does not solve backwards compatibility ;) and I think you should not force people to reformat their unit if not absolutely necessary.. IMHO.. I do have a number of 16MB Builds with 14MB SPIFFS, which is ok, for what I need.... I think no one will use such an arduino as a file-server ;) |
The builds will have proper indicators showing the LittleFS filesystem, so I will not force people to format stuff. |
I'm not too worried, I do my own builds anyways ;) but how will you do that when the core is upgraded to the new version? then you can't use it as it is anymore as |
Oh, I didn't notice the SPIFFS part was removed from the core. |
nope, it seems that the old SPIFFS part has completely vanished... That's why I did this PR in the first place, these 6 or so lines are the minimal change it needs to compile (and run/work) with esp core since commit esp8266/Arduino@a389a99 |
on a side note: since using core 2.5.2 or even the latest pre 2.6.0 git-version I have nearly no reboots/wd resets anymore! With my 20 or so "productive" nodes I'm down to a reboot of one individual node every few hours from once every half hour or so... uptimes are mostly a few days.... so I think there is a real advantage moving afap to the latest core... |
Yep, the core 2.5.2 is really good. |
Core 2.6.x has changed _SPIFFS_* to _FS_* See letscontrolit#2482
Small change for people that want to use the esp8266 GIT core where they changed from SPIFFS to LittleFS. Still uses SPIFFS format though but some variables changed.
SPIFFS* => FS*
See also: esp8266/Arduino@a389a99