Issue flashing Esp32 board: not able to define right board?

ESPHome
1

ciao guys,

maybe someone can help.
I bought 2 of these boards but can’t flash them:

I am pretty sure I am doing all ok as i flashed 20+ boards with EspHome…
Doubt I have is I am not sure i am using the right board type: couldn’t find a clear reference online!

Can someone help?

2

To be sure the best way I found is to use the esptool in command line with argument chip_id that will indicate the version of esp chipset it is and memory it contains :slight_smile:

3

hi vincen,

can you help a bit more about how to do it?

4

Tons of information on the esptool Github page:

Cheers!
DeadEnd

5

so it should be:

sudo esptool.py --port /dev/ttyUSB0 --baud 115200 chip_id

still having trouble all I get is

A fatal error occurred: Failed to connect to Espressif device: Invalid head of packet (0x20)

6

I found this - could be relevant:

Note that `--chip esp32` is required when reading ESP32 images. Otherwise the default is `--chip esp8266` and the image will be interpreted as an invalid ESP8266 image.

so try:

sudo esptool.py -- chip esp32 --port /dev/ttyUSB0 --baud 115200 chip_id

Also for the chipID there is a note about esp32:

On ESP32, there is no system_get_chip_id() function and this command is the same as esptool.py read_mac.

So you can try read_mac as well.

Cheers!
DeadEnd

7

ok so I think I have done it: I started from the assumption I couldn’t suddenly be not able to flash and, although i tried 2 units having same issues, i used an external USB to UART interface to program it connecting to the header pins.

issue i think was the integrated UART interface…finelly I did it but these boards are not nice!

8

I have some boards that requires you to keep the flash button pressed while loading via integrated USB port. Seems the board can reset the esp but cannot put it in program mode.

Just something to try

9

interesting: is it something happening only when flashing with integrated USB?

I am asking as I used standard procedure flashing while connecting with header pins.
I should be anyway something due to board design, hence you could be right, as happening on both samples I have.

I will give anyway a try this evening once back at home