ESP32-DevKitS Arduino IDE: Timed out waiting for packet header

dk4one
Posts: 3
Joined: Thu Aug 06, 2020 6:36 pm

ESP32-DevKitS Arduino IDE: Timed out waiting for packet header

Postby dk4one » Thu Aug 06, 2020 7:02 pm

Hi everyone,
I am tinkering with the ESP32-DevKitS from ESP. I couldn't get it to receive the code from the Arduino IDE. For the specific board, I choose ESP32-DevModule. I'm not really sure if it is the correct one but otherwise I couldn't find the exact board.
The error is A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header

Please let me know what I could do to make it works. As for the guide of the ESP32 DevKitS guide site, I couldn't find the exact guide to get it to work on Arduino IDE.

lbernstone
Posts: 637
Joined: Mon Jul 22, 2019 3:20 pm

Re: ESP32-DevKitS Arduino IDE: Timed out waiting for packet header

Postby lbernstone » Fri Aug 07, 2020 2:45 am

Instructions for the devkits are at https://docs.espressif.com/projects/esp ... sh-a-board.
Using the default "esp32 dev module" in Arduino IDE is just fine. There are many articles here and on the github repo about these timeout issues (https://github.com/espressif/arduino-es ... +timed+out+). The most likely culprit is a bad usb cable. The devkits has the additional problem of an improperly mounted module (or just bad connections on the spring pins). Look carefully at the contacts and make sure each of the castellations on the module has a wire locked in place.

dk4one
Posts: 3
Joined: Thu Aug 06, 2020 6:36 pm

Re: ESP32-DevKitS Arduino IDE: Timed out waiting for packet header

Postby dk4one » Fri Aug 07, 2020 4:12 pm

lbernstone wrote:
Fri Aug 07, 2020 2:45 am
Instructions for the devkits are at https://docs.espressif.com/projects/esp ... sh-a-board.
Using the default "esp32 dev module" in Arduino IDE is just fine. There are many articles here and on the github repo about these timeout issues (https://github.com/espressif/arduino-es ... +timed+out+). The most likely culprit is a bad usb cable. The devkits has the additional problem of an improperly mounted module (or just bad connections on the spring pins). Look carefully at the contacts and make sure each of the castellations on the module has a wire locked in place.
Yeah, the cullbrit is the bad USB cable, it is only charge one.

Who is online

Users browsing this forum: No registered users and 67 guests