How to program DevKitC using TXD and RXD instead of USB
Posted: Tue May 21, 2019 3:09 pm
I am trying to demonstrate to my management that we will be able to reprogram installed ESP32-WROOM-32D using the serial lines.
Right now, we are using DevKitC for prototypes, but production will have a bare ESP32-WROOM-32D soldered onto a board of our design.
I have a DevKitC which works fine from the USB port.
I have disconnected the USB cable from the USB port, connected an FTDI cable to the DevKitC. I am powering the DevKitC on the 3v3 pin from the FTDI friend, connecting ground to ground, and have the TX on the FTDI connected to RXD pin on the DevKitC, and RX on the FTDI connected to the TXD on the DevKitC.
With this setup, I can connect to the ESP32 over the FTDI cable just fine at 115200; I can see the output from my program using miniterm.
If I ground IO0 and cycle EN, I get this on the terminal:
If I then close miniterm and execute
it doesn't find the ESP32:
How can I load code to a DevKitC without using the onboard USB chip?
Right now, we are using DevKitC for prototypes, but production will have a bare ESP32-WROOM-32D soldered onto a board of our design.
I have a DevKitC which works fine from the USB port.
I have disconnected the USB cable from the USB port, connected an FTDI cable to the DevKitC. I am powering the DevKitC on the 3v3 pin from the FTDI friend, connecting ground to ground, and have the TX on the FTDI connected to RXD pin on the DevKitC, and RX on the FTDI connected to the TXD on the DevKitC.
With this setup, I can connect to the ESP32 over the FTDI cable just fine at 115200; I can see the output from my program using miniterm.
If I ground IO0 and cycle EN, I get this on the terminal:
Code: Select all
rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download
Code: Select all
esptool.py --port /dev/ttyUSB0 --baud 115200 read_mac
Code: Select all
esptool.py v2.5.0
Serial port /dev/ttyUSB0
Connecting........_____....._____....._____....._____....._____....._____....._____
A fatal error occurred: Failed to connect to Espressif device: Timed out waiting for packet header