ESP32-C3-MINI-1 Issues with bootlooping or Else!

I'm using esp32 c3 mini in a STM32WLxx based MCU. I'm trying to send AT Command through pUTTY terminal and my esp32 c3 mini is connected via FTDI Serial to USB Adapter. But Whenever I connect to the COM port I get the Following Message Continuously on the terminal

ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0xf (BROWNOUT_RST),boot:0xd (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:2
load:0x3fcd6100,len:0x18c8
load:0x403ce000,len:0x8d4
load:0x403d0000,len:0x2d6c
entry 0x403ce000
I (31) boot: ESP-IDF qa-test-v4.3.3-20220423 2nd stage bootloader
I (31) boot: compile time 07:45:53
I (32) boot: chip revision: 4
I (35) boot_comm: chip revision: 4, min. bootloader chip revision: 3
I (42) boot.esp32c3: SPI Speed      : 40MHz
I (46) boot.esp32c3: SPI Mode       : DIO
I (51) boot.esp32c3: SPI Flash Size : 4MB
I (56) boot: Enabling RNG early entropy source...
I (61) boot: Partition Table:
I (65) boot: ## Label            Usage          Type ST Offset   Length
I (72) boot:  0 otadata          OTA data         01 00 0000d000 00002000
I (80) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (87) boot:  2 nvs              WiFi data        01 02 00010000 0000e000
I (95) boot:  3 at_customize     unknown          40 00 0001e000 00042000
I (102) boot:  4 ota_0            OTA app          00 10 00060000 001d0000
I (110) boot:  5 ota_1            OTA app          00 11 00230000 001d0000
I (117) boot: End of partition table
I (121) boot_comm: chip revision: 4, min. application chip revision: 3
I (129) esp_image: segment 0: paddr=00060020 vaddr=3c140020 size=2a620h (173600) map
I (175) esp_image: segment 1: paddr=0008a648 vaddr=3fc91200 size=03c6ch ( 15468) load
I (179) esp_image: segment 2: paddr=0008e2bc vaddr=40380000 size=01d5ch (  7516) load
I (183) esp_image: segment 3: paddr=00090020 vaddr=42000020 size=133ab0h (1260208) map
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x1 (POWERON),boot:0xd (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:2
load:0x3fcd6100,len:0x18c8
load:0x403ce000,len:0x8d4
load:0x403d0000,len:0x2d6c
entry 0x403ce000
I (31) boot: ESP-IDF qa-test-v4.3.3-20220423 2nd stage bootloader
I (31) boot: compile time 07:45:53
I (32) boot: chip revision: 4
I (35) boot_comm: chip revision: 4, min. bootloader chip revision: 3
I (42) boot.esp32c3: SPI Speed      : 40MHz
I (46) boot.esp32c3: SPI Mode       : DIO
I (51) boot.esp32c3: SPI Flash Size : 4MB
I (56) boot: Enabling RNG early entropy source...
I (61) boot: Partition Table:
I (65) boot: ## Label            Usage          Type ST Offset   Length
I (72) boot:  0 otadata          OTA data         01 00 0000d000 00002000
I (80) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (87) boot:  2 nvs              WiFi data        01 02 00010000 0000e000
I (95) boot:  3 at_customize     unknown          40 00 0001e000 00042000
I (102) boot:  4 ota_0            OTA app          00 10 00060000 001d0000
I (110) boot:  5 ota_1            OTA app          00 11 00230000 001d0000
I (117) boot: End of partition table
I (121) boot_comm: chip revision: 4, min. application chip revision: 3
I (129) esp_image: segment 0: paddr=00060020 vaddr=3c140020 size=2a620h (173600) map
I (175) esp_image: segment 1: paddr=0008a648 vaddr=3fc91200 size=03c6ch ( 15468) load
I (179) esp_image: segment 2: paddr=0008e2bc vaddr=40380000 size=01d5ch (  7516) load
I (183) esp_image: segment 3: paddr=00090020 vaddr=42000020 size=133ab0h (1260208) map
I (465) esp_image: segment 4: paddr=001c3ad8 vaddr=40381d5c size=0f3c4h ( 62404) load
I (480) esp_image: segment 5: paddr=001d2ea4 vaddr=50000000 size=00014h (    20) load
I (481) esp_image: segment 6: paddr=001d2ec0 vaddr=50000018 size=00010h (    16) load
I (492) boot: Loaded app from partition at offset 0x60000
I (492) boot: Disabling RNG early entropy source...

Due the message is keeps running on terminal there was no way I can send the AT command.
The FTDI adapter is Connected to TXDO,RXDO,3.3V,GND of ESP32 C3 MINI-1.
Then, I connect the GPIO9 Pin to GND to flash the firmware and the following message pops on the terminal continuously

Build:Feb  7 2021
rst:0x1 (POWERON),boot:0x5 (DOWNLOAD(USB/UART0/1))
waiting for download
ESP-ROM:esp32c3-api1-20210207

will Flashing the firmware solve this issues? How to get this issue solved? I tried to erase the flash Using [ESP Tool](https://ESP Tool) tool but couldn't get connected.
Your kind feedback is much appreciated.

When I try to flash the firmware to ESP32 C3 MINI using ESP flash TOOL, I receive the following Error message
Invalid head of packet (0x45): Possible serial noise or corruption. [2024-06-05 22:54:42,367][ESP8266Loader_spi[1]][espDownloader.py][line:782][ERROR]: ESP32C3 Chip stub error esp_stub_and_set_baud.
My RTS pin of FTDI adapter is connected EN ,1μF capacitor, 10k resistor like the picture1.
Also DTR Pin Connected like the picture2.
waiting for your kind feedback.


When i Check the boot log message using pUTTY the following message keeps continuously
rst:0x1 (POWERON),boot:0x5 (DOWNLOAD(USB/UART0/1)) waiting for download ESP-ROM:esp32c3-api1-20210207

Thanks

I think my schematics are not suitable for achieving Automatic bootloader option for
ESP32-C3-MINI . What would be the correct schematics to achieve it. How the FTDI Connected correctly. Should I worry about RTS and DTR pin. Should The VCC=3.3 Voltage should connect instead of RTS pin in the picture 1? How about DTR pin? I will really appreciate any help.
Links: Boot Mode Selection - ESP32-C3 - — esptool.py latest documentation

I kept the RTS and DTR Pin of FTDI adapter not connected, I used the 1μF capacitor between ground and EN pin of ESP32-C3-MINI, Check the voltage the capacitor across -which is 4.3V. Also I'm using 5V instead of 3.3V from the FTDI Adapter. The GPIO9 strapping pin is directly connected GND.

Build:Feb  7 2021
rst:0x1 (POWERON),boot:0x5 (DOWNLOAD(USB/UART0/1))
waiting for download

During flashing of any program i receive the following problem:

Invalid head of packet (0x45): Possible serial noise or corruption.

But whenever I disconnect the GPIO9 pin from GND and leave it disconnected, I experience Brownout_Reset on my Board. Due to limited physical pinout I cannot check the status of other Strapping pin like GPIO8. but it is connected to 5V with 10k pullup resistor internally instead of 3.3V.
It seems to me the this is a Power Issue of the ESP32-C3-Mini, I would like to know your opinion and any way out to resolve this issue.

The problem with device is solved. The device is connect via UART to another Microcontroller which is causing the issue for ESP32-C3. It is a more of device design issue than SDK.

Long shot, but did you set "USB CDC On Boot" to "disabled".
The TX/RX pins might not work without that.
Leo..

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.