You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deprecate SPIFFS, move examples to LittleFS (esp8266#7263)
* Deprecate SPIFFS, move examples to LittleFS
SPIFFS has been a great filesystem, but it has significant problems in
many cases (and it's also pretty slow). Development seems to have
slowed/stopped on the upstream version, and we're not able to provide
support or fix the known issues with it as-is.
Deprecate SPIFFS variable.
Update all examples to use LittleFS instead of SPIFFS.
Also, minor cleanup on very old examples which has obsolete delays
waiting for the Serial port to come up, or which were stuck at 9600 baud
because of their ancient AVR heritage.
Fixesesp8266#7095
* Remove leftover debug code
* Clean up comments in some examples
* Update documentation on SPIFFS deprecation
* Fix host tests to avoid deprecation warnings
* Fix cut-n-paste error
* Restore SpeedTest.ino, adjust to allow custom FSes
Co-authored-by: Develo <[email protected]>
Copy file name to clipboardExpand all lines: doc/esp8266wifi/bearssl-client-secure-class.rst
+2-2
Original file line number
Diff line number
Diff line change
@@ -102,9 +102,9 @@ The web browser you're using to read this document keeps a list of 100s of certi
102
102
103
103
In many cases your application will know the specific CA it needs to validate web or MQTT servers against (often just a single, self-signing CA private to your institution). Simply load your private CA in a `BearSSL::X509List` and use that as your trust anchor.
104
104
105
-
However, there are cases where you will not know beforehand which CA you will need (i.e. a user enters a website through a keypad), and you need to keep the list of CAs just like your web browser. In those cases, you need to generate a certificate bundle on the PC while compiling your application, upload the `certs.ar` bundle to SPIFFS or SD when uploading your application binary, and pass it to a `BearSSL::CertStore()` in order to validate TLS peers.
105
+
However, there are cases where you will not know beforehand which CA you will need (i.e. a user enters a website through a keypad), and you need to keep the list of CAs just like your web browser. In those cases, you need to generate a certificate bundle on the PC while compiling your application, upload the `certs.ar` bundle to LittleFS or SD when uploading your application binary, and pass it to a `BearSSL::CertStore()` in order to validate TLS peers.
106
106
107
-
See the `BearSSL_CertStore` example for full details as the `BearSSL::CertStore` requires the creation of a cookie-cutter object for filesystem access (because the SD and SPIFFS filesystems are presently incompatible with each other). At a high level in your `setup()` you will call `BearSSL::initCertStore()` on a global object, and then pass this global certificate store to `client.setCertStore(&gCA)` before every connection attempt to enable it as a validation option.
107
+
See the `BearSSL_CertStore` example for full details.
Copy file name to clipboardExpand all lines: doc/faq/readme.rst
+2-2
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ perform. It is not listed among libraries verified to work with ESP8266.
79
79
80
80
`Read more <a03-library-does-not-work.rst>`__.
81
81
82
-
In the IDE, for ESP-12E that has 4M flash, I can choose 4M (1M SPIFFS) or 4M (3M SPIFFS). No matter what I select, the IDE tells me the maximum code space is about 1M. Where does my flash go?
82
+
In the IDE, for ESP-12E that has 4M flash, I can choose 4M (1M FS) or 4M (3M FS). No matter what I select, the IDE tells me the maximum code space is about 1M. Where does my flash go?
Copy file name to clipboardExpand all lines: doc/libraries.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ This is a bit different from standard EEPROM class. You need to call ``EEPROM.be
25
25
26
26
``EEPROM.write`` does not write to flash immediately, instead you must call ``EEPROM.commit()`` whenever you wish to save changes to flash. ``EEPROM.end()`` will also commit, and will release the RAM copy of EEPROM contents.
27
27
28
-
EEPROM library uses one sector of flash located just after the SPIFFS.
28
+
EEPROM library uses one sector of flash located just after the embedded filesystem.
Copy file name to clipboardExpand all lines: doc/ota_updates/readme.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -360,7 +360,7 @@ If this is the case, then most likely ESP module has not been reset after initia
360
360
The most common causes of OTA failure are as follows:
361
361
362
362
- not enough physical memory on the chip (e.g. ESP01 with 512K flash memory is not enough for OTA).
363
-
- too much memory declared for SPIFFS so new sketch will not fit between existing sketch and SPIFFS – see `Update process - memory view <#update-process-memory-view>`__.
363
+
- too much memory declared for the filesystem so new sketch will not fit between existing sketch and the filesystem – see `Update process - memory view <#update-process-memory-view>`__.
364
364
- too little memory declared in Arduino IDE for your selected board (i.e. less than physical size).
365
365
- not resetting the ESP module after initial upload using serial port.
0 commit comments