From 527720fb5b2dc052144169e3c7695e79dea99876 Mon Sep 17 00:00:00 2001 From: Angus Gratton Date: Fri, 3 Mar 2017 11:22:25 +1100 Subject: [PATCH] esptool: Update esptool.py to integrate reset fix for older dev boards Originally marked "Reset with ESP32R0 Windows workaround", but proven to be necessary on some other platforms as well. This is now integrated into the default esptool.py reset behaviour. Closes #305 https://github.com/espressif/esp-idf/issues/305 --- components/esptool_py/Kconfig.projbuild | 8 -------- components/esptool_py/esptool | 2 +- 2 files changed, 1 insertion(+), 9 deletions(-) diff --git a/components/esptool_py/Kconfig.projbuild b/components/esptool_py/Kconfig.projbuild index 3ce1b7f3f8..84ca5d6831 100644 --- a/components/esptool_py/Kconfig.projbuild +++ b/components/esptool_py/Kconfig.projbuild @@ -140,24 +140,16 @@ choice ESPTOOLPY_BEFORE wired from the serial port to the ESP32. Most USB development boards do this internally. - The "Reset with ESP32R0 Windows workaround" option works - around an automatic reset bug in hardware, when using Windows - with some development boards. This fix only works if you're - using a silicon revision 0 ESP32. - config ESPTOOLPY_BEFORE_RESET bool "Reset to bootloader" config ESPTOOLPY_BEFORE_NORESET bool "No reset" -config ESPTOOLPY_BEFORE_ESP32R0 - bool "Reset with ESP32R0 Windows workaround" endchoice config ESPTOOLPY_BEFORE string default "default_reset" if ESPTOOLPY_BEFORE_RESET default "no_reset" if ESPTOOLPY_BEFORE_NORESET - default "esp32r0" if ESPTOOLPY_BEFORE_ESP32R0 choice ESPTOOLPY_AFTER prompt "After flashing" diff --git a/components/esptool_py/esptool b/components/esptool_py/esptool index c1d00094d5..907273664a 160000 --- a/components/esptool_py/esptool +++ b/components/esptool_py/esptool @@ -1 +1 @@ -Subproject commit c1d00094d564451636b01308625119901e2257ac +Subproject commit 907273664ada32fc33f3fbfeba99550512c67e4d -- 2.40.0