ESP8266 Community Forum

- Tue Jan 26, 2016 4:28 am #39720 most likely to use with "EEPROM" ???
viewtopic.php?f=33&t=2418

- Tue Jan 26, 2016 9:43 am #39732 Well, that doesn't make any sense at all! There is no reason to allocate 2MB to the EEPROM section.

I read the files system chapter og the Github wiki, but it doesn't say anything about this
If I choose the 512k no SPIFFS option, the IDE tells me that the maximum program size is 499,696 bytes (~12k is used by the system i guess (SDK etc.)

If I choose the 512k 64k SPIFFS option, the IDE tells me that the maximum program size is 434,160 bytes.

It clearly doesn't affects the smaller flash sizes (tested on 512k, 1M and 2M). Haven't anybody warders where those 2MB went?

- Tue Jan 26, 2016 10:20 am #39738 Due to Flash caching mechanism done by the SDK, the code is limited to the first 1M, and since it can support OTA, this 1M is divided in 2x 512K, and the end of those 512K still need to keep space for WiFi configs.
The rest of the Flash can be used for SPIFFS with little space for EEPROM.
This means that if you choose 1M SPIFFS withing 4M, the 2MB remaining is not gone, but simply unused and left empty.

- Tue Jan 26, 2016 10:30 am #39741 ah, That makes sense. So the code cannot be larger than 1MB (without OTA) no matter what flash size your module has.
So basically, there is no way to assign these 2 MB's to the program flash, making it possible to write code as large as ~1,5MB and still be able to use Over The Air programming?