Issue with ESP32 C3 mini 1 (ESPTOOL-987)

[FrimeNotInformatician]

Operating System

Windows 11

Esptool Version

v4.8.1

Python Version

3.12.3

Chip Description

ESPRESSIF ESP32 C3 mini

Device Description

It's just an esp32 chip on an pcb .

Hardware Configuration

the connection are : GND on GND , EN into connected to the port 8 (EN) , IO0 into the port 23 (IO9), RXD0 into 30 and TXD0 into 31

How is Esptool Run

terminal windows

Full Esptool Command Line that Was Run

python -m esptool --chip esp32 --trace --port COM9 --baud 9600 flash_id

Esptool Output

.TRACE +0.055 command op=0x08 data len=36 wait_response=1 timeout=0.100 data=
    0707122055555555 5555555555555555 | ... UUUUUUUUUUUU
    5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU
    55555555                          | UUUU
TRACE +0.001 Write 46 bytes:
    c000082400000000 0007071220555555 | ...$........ UUU
    5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU
    5555555555555555 5555555555c0     | UUUUUUUUUUUUU.
TRACE +0.004 Read 1 bytes: c0
TRACE +0.000 Read 2 bytes: 0008
TRACE +0.016 Read 1 bytes: 24
TRACE +0.000 Read 15 bytes: 000000000007071220555555555555
TRACE +0.017 Read 1 bytes: 55
TRACE +0.000 Read 14 bytes: 5555555555555555555555555555
TRACE +0.015 Read 1 bytes: 55
TRACE +0.000 Read 11 bytes: 55555555555555555555c0
TRACE +0.000 Received full packet:
    0008240000000000 0707122055555555 | ..$........ UUUU
    5555555555555555 5555555555555555 | UUUUUUUUUUUUUUUU
    5555555555555555 55555555         | UUUUUUUUUUUU
TRACE +0.112 Serial data stream stopped: Possible serial noise or corruption.
.

A fatal error occurred: Failed to connect to ESP32: Serial data stream stopped: Possible serial noise or corruption.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html

More Information

As i understood the first connection between the esp and the pc work after that i t stop

Other Steps to Reproduce

No response

I Have Read the Troubleshooting Guide

• I confirm I have read the troubleshooting guide.

[fhrbata]

Hello @FrimeNotInformatician,

it appears that in the trace output, the response is identical to the request, which seems incorrect. The response should resemble the SLIP packet c0010804000707122000000000c0 from the ROM bootloader. It seems that whatever is running on the target is echoing the UART input. Perhaps the chip isn't actually in bootloader mode, and the automatic switch to bootloader might have failed. You could try putting the chip into bootloader mode manually and then run esptool without resetting the chip e.g. python -m esptool --before no_reset --chip esp32 --trace --port COM9 --baud 9600 flash_id. To automatically enter bootloader mode, some additional circuitry might be needed, as shown in the schematic of the ESP32 DevKitC development board. The entire Boot Mode Selection documentation might also be helpful.

Can you connect to the chip using another serial program like PuTTY as explained in verify serial connection?

Thank you