Unable to flash ESP32-s3 with ESP-prog; ESP-prog only outputs serial data on RX->RX0 or TX->TX0
Posted: Sat Mar 11, 2023 5:17 pm
Hi everyone,
I am having a weird problem when using an ESP-Prog to flash an ESP32-S3-WROOM-1u on a custom PCB. When the TX wire on the ESP-prog serial header is connected to the RX0 pin of the ESP32 the serial output stops. Using platformio in VSCODE, the serial monitor receives the following output from the ESP32 when TX0 (ESP32) -> TX (ESP-prog) or RX0 (ESP32) -> RX (ESP-prog):
In this configuration the module will detect being in download mode if the boot button is healed and the reset button is pressed:
With the module in download mode, I can try and upload sample code https://github.com/espressif/esp-idf/bl ... rld_main.c:
So it is upset about the lack of a TX wire (still unconnected). Reconnecting the TRX wire yields the following (with the module placed into download mode and verified prior):
Please recall that the exp32 is outputting data with TX0->TX and RX0->RX. Trying placing the ESP32 into download mode and making RX0->TX and TX0->RX yields the following:
Previously, I have received errors about invalid heads of packets but I am unable to reproduce this error. Additionally, the ESP32 did being to flash at one point but it stopped in the middle of it. I have been unable to reproduce this as well:
At this point, the ESP32 definitely has a corrupted flash but I am unable to wipe it due to not being able to interface it with UART. I also can not connect with it using serial to set the EFUSE and communicate with it using JTAG. I am not sure if the issue is with the ESP32 or the ESP-prog at this point, but I am leaning towards the prog as the ESP32 is at least outputting some data over serial.
The circuit schematic can be found here:
There are no signs of shorts on the custom board and it passed a continuity check prior to soldering. When trying to upload with RX0 -> TX and TX0-> RX, the green light on the ESP-prog board blinks indicating that it is trying to download data to the ESP32 but it never connects:
Trying to place the module into download mode during the connection does not work and neither does holding boot when plugging in the USB cable to the ESP-prog to power everything.
Can anyone offer suggestions as for how to proceed or how to fix my circuit? Please let me know, thank you!
I am having a weird problem when using an ESP-Prog to flash an ESP32-S3-WROOM-1u on a custom PCB. When the TX wire on the ESP-prog serial header is connected to the RX0 pin of the ESP32 the serial output stops. Using platformio in VSCODE, the serial monitor receives the following output from the ESP32 when TX0 (ESP32) -> TX (ESP-prog) or RX0 (ESP32) -> RX (ESP-prog):
Code: Select all
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0x9 (SPI_FAST_FLASH_BOOT)
Saved PC:0x403cdc76
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x1660
load:0x403c9700,len:0xbcc
load:0x403cc700,len:0x2fac
entry 0x403c9954
I (29) boot: ESP-IDF 4.4.4 2nd stage bootloader
I (29) boot: compile time 20:42:44
I (29) boot: chip revision: v0.1
I (31) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (38) boot.esp32s3: Boot SPI Speed : 80MHz
I (43) boot.esp32s3: SPI Mode : DIO
I (47) boot.esp32s3: SPI Flash Size : 16MB
I (52) boot: Enabling RNG early entropy source...
I (58) boot: Partition Table:
I (61) boot: ## Label Usage Type ST Offset Length
I (68) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (76) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (83) boot: 2 factory factory app 00 00 00010000 00100000
I (91) boot: End of partition table
I (95) boot_comm: chip revision: 1, min. application chip revision: 0
I (102) esp_image: segment 0: paddr=00010020 vaddr=3c060020 size=20a24h (133668) map
I (135) esp_image: segment 1: paddr=00030a4c vaddr=3fc92ed0 size=02c34h ( 11316) load
I (137) esp_image: segment 2: paddr=00033688 vaddr=40374000 size=0c990h ( 51600) load
E (152) esp_image: invalid segment length 0xffffffff
E (152) boot: Factory app partition is not bootable
E (152) boot: No bootable app partitions in the partition table
Code: Select all
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x3 (DOWNLOAD(USB/UART0))
waiting for downloadCode: Select all
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32-s3-devkitc-1.html
PLATFORM: Espressif 32 (6.1.0) > Espressif ESP32-S3-DevKitC-1-N8 (8 MB QD, No PSRAM)
HARDWARE: ESP32S3 240MHz, 320KB RAM, 16MB Flash
DEBUG: Current (esp-builtin) On-board (esp-builtin) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
- framework-espidf @ 3.50001.0 (5.0.1)
- tool-cmake @ 3.16.4
- tool-esptoolpy @ 1.40500.0 (4.5.0)
- tool-idf @ 1.0.1
- tool-mconf @ 1.4060000.20190628 (406.0.0)
- tool-mkfatfs @ 2.0.1
- tool-mklittlefs @ 1.203.210628 (2.3)
- tool-mkspiffs @ 2.230.0 (2.30)
- tool-ninja @ 1.9.0
- tool-openocd-esp32 @ 2.1100.20220706 (11.0)
- toolchain-esp32ulp @ 1.23500.220830 (2.35.0)
- toolchain-riscv32-esp @ 11.2.0+2022r1
- toolchain-xtensa-esp32s3 @ 11.2.0+2022r1
Reading CMake configuration...
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 0 compatible libraries
Scanning dependencies...
No dependencies
Building in release mode
Retrieving maximum program size .pio\build\esp32-s3-devkitc-1\firmware.elf
Checking size .pio\build\esp32-s3-devkitc-1\firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM: [ ] 3.5% (used 11552 bytes from 327680 bytes)
Flash: [== ] 19.2% (used 201345 bytes from 1048576 bytes)
Configuring upload protocol...
AVAILABLE: cmsis-dap, esp-bridge, esp-builtin, esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esptool
Looking for upload port...
Using manually specified: COM9
Uploading .pio\build\esp32-s3-devkitc-1\firmware.bin
esptool.py v4.5
Serial port COM9
Connecting......................................
A fatal error occurred: Failed to connect to ESP32-S3: Download mode successfully detected, but getting no sync reply: The serial TX path seems to be down.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html
*** [upload] Error 2
Code: Select all
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32-s3-devkitc-1.html
PLATFORM: Espressif 32 (6.1.0) > Espressif ESP32-S3-DevKitC-1-N8 (8 MB QD, No PSRAM)
HARDWARE: ESP32S3 240MHz, 320KB RAM, 16MB Flash
DEBUG: Current (esp-builtin) On-board (esp-builtin) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
- framework-espidf @ 3.50001.0 (5.0.1)
- tool-cmake @ 3.16.4
- tool-esptoolpy @ 1.40500.0 (4.5.0)
- tool-idf @ 1.0.1
- tool-mconf @ 1.4060000.20190628 (406.0.0)
- tool-mkfatfs @ 2.0.1
- tool-mklittlefs @ 1.203.210628 (2.3)
- tool-mkspiffs @ 2.230.0 (2.30)
- tool-ninja @ 1.9.0
- tool-openocd-esp32 @ 2.1100.20220706 (11.0)
- toolchain-esp32ulp @ 1.23500.220830 (2.35.0)
- toolchain-riscv32-esp @ 11.2.0+2022r1
- toolchain-xtensa-esp32s3 @ 11.2.0+2022r1
Reading CMake configuration...
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 0 compatible libraries
Scanning dependencies...
No dependencies
Building in release mode
Retrieving maximum program size .pio\build\esp32-s3-devkitc-1\firmware.elf
Checking size .pio\build\esp32-s3-devkitc-1\firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM: [ ] 3.5% (used 11552 bytes from 327680 bytes)
Flash: [== ] 19.2% (used 201345 bytes from 1048576 bytes)
Configuring upload protocol...
AVAILABLE: cmsis-dap, esp-bridge, esp-builtin, esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esptool
Looking for upload port...
Using manually specified: COM9
Uploading .pio\build\esp32-s3-devkitc-1\firmware.bin
esptool.py v4.5
Serial port COM9
Connecting......................................
A fatal error occurred: Failed to connect to ESP32-S3: Serial data stream stopped: Possible serial noise or corruption.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html
*** [upload] Error 2
Code: Select all
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32-s3-devkitc-1.html
PLATFORM: Espressif 32 (6.1.0) > Espressif ESP32-S3-DevKitC-1-N8 (8 MB QD, No PSRAM)
HARDWARE: ESP32S3 240MHz, 320KB RAM, 16MB Flash
DEBUG: Current (esp-builtin) On-board (esp-builtin) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
- framework-espidf @ 3.50001.0 (5.0.1)
- tool-cmake @ 3.16.4
- tool-esptoolpy @ 1.40500.0 (4.5.0)
- tool-idf @ 1.0.1
- tool-mconf @ 1.4060000.20190628 (406.0.0)
- tool-mkfatfs @ 2.0.1
- tool-mklittlefs @ 1.203.210628 (2.3)
- tool-mkspiffs @ 2.230.0 (2.30)
- tool-ninja @ 1.9.0
- tool-openocd-esp32 @ 2.1100.20220706 (11.0)
- toolchain-esp32ulp @ 1.23500.220830 (2.35.0)
- toolchain-riscv32-esp @ 11.2.0+2022r1
- toolchain-xtensa-esp32s3 @ 11.2.0+2022r1
Reading CMake configuration...
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 0 compatible libraries
Scanning dependencies...
No dependencies
Building in release mode
Retrieving maximum program size .pio\build\esp32-s3-devkitc-1\firmware.elf
Checking size .pio\build\esp32-s3-devkitc-1\firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM: [ ] 3.5% (used 11552 bytes from 327680 bytes)
Flash: [== ] 19.2% (used 201345 bytes from 1048576 bytes)
Configuring upload protocol...
AVAILABLE: cmsis-dap, esp-bridge, esp-builtin, esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esptool
Looking for upload port...
Using manually specified: COM9
Uploading .pio\build\esp32-s3-devkitc-1\firmware.bin
esptool.py v4.5
Serial port COM9
Connecting......................................
A fatal error occurred: Failed to connect to ESP32-S3: Serial data stream stopped: Possible serial noise or corruption.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html
*** [upload] Error 2
At this point, the ESP32 definitely has a corrupted flash but I am unable to wipe it due to not being able to interface it with UART. I also can not connect with it using serial to set the EFUSE and communicate with it using JTAG. I am not sure if the issue is with the ESP32 or the ESP-prog at this point, but I am leaning towards the prog as the ESP32 is at least outputting some data over serial.
The circuit schematic can be found here:
There are no signs of shorts on the custom board and it passed a continuity check prior to soldering. When trying to upload with RX0 -> TX and TX0-> RX, the green light on the ESP-prog board blinks indicating that it is trying to download data to the ESP32 but it never connects:
Code: Select all
Serial port COM9
Connecting......................................
A fatal error occurred: Failed to connect to ESP32-S3: Serial data stream stopped: Possible serial noise or corruption.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html
*** [upload] Error 2
================================================
Trying to place the module into download mode during the connection does not work and neither does holding boot when plugging in the USB cable to the ESP-prog to power everything.
Can anyone offer suggestions as for how to proceed or how to fix my circuit? Please let me know, thank you!