-
|
Is it actually normal that the WiFi access data remains after downloading/flashing the firmware again with VS Code? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The persistent data is stored in the NVS(Non Volatile Storage) partition which is not overwritten during flashing, not my choice, just just PlatformIO operates by default. There are currently 5 partitions as defined by the with_ota.csv out of which 1(spiffs) is currently unused, the one nvs partition, another one(otadata) stores data for OTA updating, and 2(app0 and app1) store the actual code of this project which is what is actually overwritten upon flashing, there's two since when you want to OTA update you can't just overwrite the current running software therefore you need to write it somewhere else and keep of track of what partition should be used at boot which is what otadata does. A brief introduction on how you can do OTA updates is available at the bottom of the README.md and i have it on my backlog to have it moved to the wiki and improve it. |
Beta Was this translation helpful? Give feedback.
The persistent data is stored in the NVS(Non Volatile Storage) partition which is not overwritten during flashing, not my choice, just just PlatformIO operates by default.
There are currently 5 partitions as defined by the with_ota.csv out of which 1(spiffs) is currently unused, the one nvs partition, another one(otadata) stores data for OTA updating, and 2(app0 and app1) store the actual code of this project which is what is actually overwritten upon flashing, there's two since when you want to OTA update you can't just overwrite the current running software therefore you need to write it somewhere else and keep of track of what partition should be used at boot which is what otadata does.
…