What files to keep from a specific revision build, and how to flash
Posted: Thu Apr 16, 2020 1:21 pm
While in development mode, I am continuously using the command 'idf.py -p COMX flash monitor' (X=port#) at the top of my source and build tree.
I would like to regularly save specific revisions, with as few files as possible, which I may at a later time flash my device with.
So, what files do I minimum need to keep, and how do I flash those to an ESP32-WROOM-32?
While developing for the ESP32-WROOM-32 using the 'idf.py flash' command, it always compares with the source tree and builds it if changes have been made, and I would like to avoid that.
I just want to flash a device with previously made binary or binaries, if possible.
With STM32 I can keep just one .hex file and then use an ST-LINK to flash the hardware, and I would like to know the equivalent method of this on ESP32?
I am working from both Win10 and Linux platforms, but I don't suppose there are differences regarding this?
Please let me know of any pointers you may have, or feel free to ask if it is unclear?
I would like to regularly save specific revisions, with as few files as possible, which I may at a later time flash my device with.
So, what files do I minimum need to keep, and how do I flash those to an ESP32-WROOM-32?
While developing for the ESP32-WROOM-32 using the 'idf.py flash' command, it always compares with the source tree and builds it if changes have been made, and I would like to avoid that.
I just want to flash a device with previously made binary or binaries, if possible.
With STM32 I can keep just one .hex file and then use an ST-LINK to flash the hardware, and I would like to know the equivalent method of this on ESP32?
I am working from both Win10 and Linux platforms, but I don't suppose there are differences regarding this?
Please let me know of any pointers you may have, or feel free to ask if it is unclear?