Merging all bin files to make production flashing more convenient
Posted: Mon Nov 21, 2022 11:30 am
Hello. I have read a 2019 discussion where someone had discussed about plans of implementing such feature to merge all bin files (bootloader, partition table, and etc.. into one):
https://esp32.com/viewtopic.php?t=8687
I would like to clarify, is there such option for ESP32 as of right now as it would greatly reduce the complexity of flashing the firmware via the custom app that I am making (which uses the esptool.py to flash). I could avoid copying partition table, ota_data_initial and etc.. and instead would need to copy just a single .bin file.
I have found some 3rd party code (not esp-idf official):
https://github.com/vtunr/esp32_binary_merger
But I am quite concerned if it fully reliable and not going to break my app so I would prefer esp-idf official method.
Currently I use:
https://esp32.com/viewtopic.php?t=8687
I would like to clarify, is there such option for ESP32 as of right now as it would greatly reduce the complexity of flashing the firmware via the custom app that I am making (which uses the esptool.py to flash). I could avoid copying partition table, ota_data_initial and etc.. and instead would need to copy just a single .bin file.
I have found some 3rd party code (not esp-idf official):
https://github.com/vtunr/esp32_binary_merger
But I am quite concerned if it fully reliable and not going to break my app so I would prefer esp-idf official method.
Currently I use:
Code: Select all
esptool.py -p COM33 -b 921600 --before default_reset --after hard_reset --chip esp32 write_flash --flash_mode dio --flash_freq 80m --flash_size detect 0x1000 bootloader/bootloader.bin 0x10000 FIRMWARE.bin 0x8000 partition_table/partition-table.bin 0xd000 ota_data_initial.bin 0xf000 phy_init_data.bin 0x4f0000 storage.bin