-
Hi all, I'm putting together instructions to a fab house to flash the boards that they are making for us. I want to include our application files, but I don't want to "freeze" them in a firmware image, as I just want to use a stock image. Is it "supported" to do the following steps to achieve this:
This will list the data partitions. The filesystem is stored in the label=vfs Make note of the address and size of the vfs partition (mine were address=5177344, size=11599872) and convert them to hex (address=0x4f0000, size=0xb10000 in my case)
Also, is there any need to back-up and restore any of the other data partitions? (i.e. nvs, otadata, phy_init) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
@ma261065 Yes this is definitely supported. FWIW, I'm guessing you're using a 16MiB-OTA configuration, in which case these numbers come from the partiton table: https://github.com/micropython/micropython/blob/master/ports/esp32/partitions-16MiB-ota.csv (you can also extract this out of partition-table.bin, which is generated from that csv file) For a given flash size + configuration, these offsets and sizes must remain fix, otherwise new firmware updates will be unable to access the filesystem partition. For the other partitions, only |
Beta Was this translation helpful? Give feedback.
-
Got it, thanks. I wasn't sure if it was used by MicroPython itself for anything, but it looks like it's just a data store for the application to store key/value pairs in, which I'm not using. All clear now - appreciate the response. |
Beta Was this translation helpful? Give feedback.
@ma261065 Yes this is definitely supported.
FWIW, I'm guessing you're using a 16MiB-OTA configuration, in which case these numbers come from the partiton table: https://github.com/micropython/micropython/blob/master/ports/esp32/partitions-16MiB-ota.csv
(you can also extract this out of partition-table.bin, which is generated from that csv file)
For a given flash size + configuration, these offsets and sizes must remain fix, otherwise new firmware updates will be unable to access the filesystem partition.
For the other partitions, only
nvs
if you're using NVS (and want to restore that data).