You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to #3135, the erase_otadata and read_otadata targets still don't always use the same port as the rest of the flashing commands, because they don't honor ESPPORT and ESPBAUD.
The documentation for e.g. using idf.py says "The environment variables ESPPORT and ESPBAUD can be used to set default values for the -p and -b options" but the otadata commands only use what's set in the sdkconfig.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
"erase_otadata" and "read_otadata" targets don't honor ESPPORT
"erase_otadata" and "read_otadata" targets don't honor ESPPORT (IDFGH-3289)
May 12, 2020
I'm working on converting my project to CMake and it seems like the same problem is there -- esp_idf/components/app_update/CMakeLists.txt passes CONFIG_ESPTOOLPY_BEFORE and CONFIG_ESPTOOLPY_AFTER to otatool.py, but doesn't pass the port at all, and doesn't honor ESPPORT, ESPBAUD, etc.
My guess is this also affects commands like idf.py partition_table-flash but I haven't dug in enough to figure it out.
esp-idf version v4.0-386-gb0f053d82dc4
Related to #3135, the
erase_otadata
andread_otadata
targets still don't always use the same port as the rest of the flashing commands, because they don't honorESPPORT
andESPBAUD
.The documentation for e.g. using idf.py says "The environment variables ESPPORT and ESPBAUD can be used to set default values for the -p and -b options" but the otadata commands only use what's set in the sdkconfig.
The text was updated successfully, but these errors were encountered: