- Build the project, if necessary.
- Parse the output of the idf.py build command to find out which build artefacts exist.
- Grab the build artefacts and copy them into a directory together with a script that calls esptool to flash.
- (Optionally) Zip everything up for sending.
idf.py export-manifest
-
- Posts: 168
- Joined: Sun May 22, 2022 2:42 pm
idf.py export-manifest
I wonder whether there is something like idf.py export-manifest (name made up) that does the following steps:
-
- Posts: 168
- Joined: Sun May 22, 2022 2:42 pm
Re: idf.py export-manifest
I just learned about uf2.bin that looks like it's a step in that direction, however it seems to be solely for the esp-usb-bridge -- or can I use uf2.bin also as input file for esptool?
-
- Posts: 1704
- Joined: Mon Oct 17, 2022 7:38 pm
- Location: Europe, Germany
Re: idf.py export-manifest
This would be pretty easy to do: Look at "flasher_args.json" or "flash_project_args" inside the build directory. If you zip up the .bin files named there and pass them on together with the flash_project_args file and a batch file likeDrMickeyLauer wrote: ↑Wed Feb 28, 2024 3:50 pm
- ...
- Parse the output of the idf.py build command to find out which build artefacts exist.
...
Code: Select all
@echo off
pushd build
%IDF_PYTHON% %IDF_PATH%\components\esptool_py\esptool\esptool.py -p COM7 -b 460800 --before default_reset --after hard_reset --chip esp32s3 write_flash @flash_project_args
popd
Who is online
Users browsing this forum: Bing [Bot] and 126 guests