How to deal with "timed out waiting for packet header"

How to deal with "timed out waiting for packet header"


5 min read

If you work with ESP32 or ESP8266 boards, you likely encounter this error sooner or later. But what does it mean, and how can you get rid of it?

ESP8266 upload error in Arduino

What does "error: espcomm_open failed" mean?

The espcomm_open error is not a compiler error. It appears when you try to upload firmware, but esptool fails to establish a connection.

Besides espcomm_open, other common errors include espcomm_sync and Timed out waiting for packet header.

warning: espcomm_sync failed
error: espcomm_open failed
Failed to connect to ESP8266: Timed out waiting for packet header
serial.serialutil.SerialTimeoutException: Write timeout 
  does not exist or your board is not connected

Esptool is a python script made for flashing the ESP32 or ESP8266. It can be used directly through the command line or indirectly through an IDE like Arduino.

If it fails to open a connection to your development board, check these things:

  • Make sure to have the correct serial (COM) port selected

  • Install missing drivers

  • Try another USB cable (some only provide power and transfer no data)

  • Try a different USB port and avoid USB hubs, dongles, or adapters

  • Make sure the serial connection isn't already in use by another program

  • Hold down the flash button or connect GPIO-0 (D3) to GND

  • If everything fails, try it on another computer

Select the right port

Arduino IDE Port selector

Before you can flash firmware onto a development board, you must select a serial port (also called COM port).

In Arduino IDE, you select it by going to Tools and then port.

To figure out which serial port corresponds to your dev board, look at the list (without your board plugged in), then plug in your dev board and observe which new serial port appeared in the list.

If you don't see a new port appear when you plug in your board, or the menu is grayed out completely, then no new serial port was detected. This can be caused by a missing driver or a defective USB cable. Continue reading in this case.


๐Ÿ˜” Bad news: There are multiple drivers, and we can't tell you which one you need. It depends on the hardware you have.

๐Ÿ˜ƒ Good news: There are only 3 different families of serial chips used on almost all development boards. So worst case, you just install all of them.

Below is a list of those chips with links to their manufacturer's drivers' download page. The pictures shown are examples. All these chip families exist in different sizes (packages) and can look different on your development board.

CH340 & CH341

CH340C Serial Chip on Lolin D1 mini Development Board

The CH340/CH341 is a very common USB to serial chip family, used often in cheap development boards thanks to its affordable pricing.

๐Ÿ”— CH340/CH341 Drivers: [](\


CP2102N Serial Chip on ESP32 DevKit

Due to their speed and small form factor, the CP2102 and CP2104 from Silicon Labs are popular among most development boards.

๐Ÿ”— CP210x Drivers:


FTDI Serial Chip FT231XS on Spacehuhn Andromeda Board

FTDI Chip makes Hi-Speed USB serial ICs. For example, we used an FTDI chip for our Andromeda board.

๐Ÿ”—FTDI Drivers:

The USB connection

USB cables unsplash QM9yzAoX-GQ

If you installed the drivers, but no new serial port is detected, it might be the cable itself. Some USB cables are made for charging only and can't transmit data. Try another cable.

Sometimes it can also be enough to simply use a different physical USB port.

Try to avoid USB hubs, dongles, or other adapters in between the connection that could cause problems.

Flash button

Flash Button of NodeMCU ESP8266 Development Board

If your board is detected and you are sure to have selected the correct port, but uploading firmware still doesn't work, it might be because of the development board itself. The ESP has to be in flash mode to accept new firmware.

Most ESP32 and ESP8266 boards have an automatic reset and flash circuit. Meaning they can be restarted and put into flashing mode automatically. But sometimes, that circuit is defective or hasn't been implemented correctly.

To manually put the ESP32 or ESP8266 into flashing mode, you need to connect GPIO-0 (D3) to GND. Some boards have a dedicated button for that. Other boards don't - in which case you'd have to connect those two pins with a wire.
If you have something else connected to GPIO-0 (D3), try disconnecting it to keep it from interfering with the boot selection.

With the flash button pressed or GPIO-0 connected to GND, plug in your board or hit the reset button. Then start uploading the firmware. In some cases, you might need to keep the button pressed or the pins connected until the upload begins. This part is sometimes tricky and might require a bit of trial and error.

Then you have to disconnect the pins and restart the board (unplug and plug it in again). It should then be back to the regular boot mode and run your newly flashed firmware.

What else?

Make sure no other software is using the serial port.

If nothing seems to work, try it on another computer.

Still no luck? If you have tried everything mentioned here so far, and nothing seems to work, then maybe the hardware has an issue. Unfortunately, this can happen, especially with cheap development boards. Try reaching out to the seller or manufacturer.

Do you have any tips?

Let us know in the comments below if this guide helped you! What was the issue for you? Do you have any more tips?

We hope to hear from you โ˜บ๏ธ