I have two ESP32 devkit boards:
1. NodeMCU ESP32-S devkit board (from ebay)
2. ESP32_devkitc_V4
I can program both using the onboard FTDI/USB. It goes into bootloader mode and esptool is able to program it fine.
Now I need to be able to program the devkitc with an external FTDI, since I have a custom PCB that has the same ESP32 module on it but no onboard FTDI. This is where I run into a problem.
The devkitc board goes in to bootloader mode succesfully using the EN and BOOT onboard buttons:
Code: Select all
[2019-03-17_15:39:50]rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
[2019-03-17_15:39:50]waiting for download
Code: Select all
Serial port COM3
Connecting........_____....._____....._____....._____....._____....._____....._____
A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header
*** [upload] Error 2
Code: Select all
TX --> RX
RX --> TX
3v3, GND.
Using onboard EN/GPIO0 buttons
How is this possible?
Are there differences affecting the bootloader process between different ESP32-WROOM packages?
I have already spent several hours debugging this so I would really appreciate it if someone could help me!
I have added pictures of the boards I'm using.
Greetings, Stefan