ESP32: feature request Partition
related to: #8380
it would be nice if Partition.get_next_update() would also accept the block_size argument.
This way you won't be locked in to a certain block_size after initial deployment when doing OTA updates.
ESP 32 OTA with v1.18
Hi Team,
I have flashed " esp32-ota-20220117-v1.18.bin " to my esp32 with 4MB flash device, After flashing it it took almost 1.5 MB for firmware partition and rest for others as per given below partition table.
As per below table and v1.18 bin file size, there is no possibility for OTA updates with provision of having factory , OTA_0 & OTA_1, along with application code. please correct me if my understanding is not valid.
Also, I did not find any sample code for implementation of OTA along with application code . Requesting team to include sample files or guide us the implementation instructions with this version.
Partition table for MicroPython with OTA support using 4MB flash
Notes: the offset of the partition table itself is set in
$IDF_PATH/components/partition_table/Kconfig.projbuild.
Name, Type, SubType, Offset, Size, Flags
nvs, data, nvs, 0x9000, 0x4000,
otadata, data, ota, 0xd000, 0x2000,
phy_init, data, phy, 0xf000, 0x1000,
ota_0, app, ota_0, 0x10000, 0x180000,
ota_1, app, ota_1, 0x190000, 0x180000,
vfs, data, fat, 0x310000, 0x0f0000,
Thank you