ESP32 Forum

Hello,

I've tested ESP32-C3-MINI-1 module thanks to ESP32-C3-DevKit-1.
Very satisfied, I plan to use ESP32-C3-MINI-1 module on my futures PCB projects.

When my PCB manufacturer will source some ESP32-C3-MINI-1 module, is there a firmware pre-programmed ?
Does that default firmware/bootloader allows me to upload my Arduino application via uart (RX0/TX0, or build in USB Serial) like I do with my ESP32-C3-DevKit-1 with Arduino IDE ?

Or do I need to firstly flash a bootloader through some JTAG or SPI ?

Thank you !

PeterMikeSmooth3 wrote: ↑

Wed Aug 31, 2022 12:17 pm

When my PCB manufacturer will source some ESP32-C3-MINI-1 module, is there a firmware pre-programmed ?

There either is no firmware in flash, or a testing or AT firmware that is likely not useful. That doesn't matter, however, because:

Does that default firmware/bootloader allows me to upload my Arduino application via uart (RX0/TX0, or build in USB Serial) like I do with my ESP32-C3-DevKit-1 with Arduino IDE ?

Every ESP32 (including C3, S3, ...) has a hardcoded, unchangable and un-erasable ROM that contains a bootloader that allows you to do these things (as long as you don't set the efuse to disable them). So whatever firmware the module comes with, you will be able to reprogram it using UART or USB.

Very clear answer, thank you very much !

I am also trying to flash the first firmware on my ESP32 S2 fh4, but i cannot get a connection to the esp.

Via USB (pins 19 and 20/ D- and D+)
I tried to put the esp in boot mode (pulling IO0 low on startup) and connecting to it but nothing get recognized.

Via Serial uart0 tx and rx (pins 48 and 49)
Connecting the pins to my cp2102 gets only the com port of the cp2102, but no serial connection can be established.

The chip gets 3v3 on the pins, but still can't get any connection to the board.

Any suggestions what to check or how to connect to it?

Update
The ESP32 S2 fh4 seems to not get into boot mode, the usb D- and D+ stay 0 while on my modified lilygo esp32s2 i see that in boot mode the two pins have some activity.

Can you start a new topic for that? It's an entirely different chip than the C3. Please also add schematics if you have them.

I also have a problem with first upload factory module ESP32-C3-MINI-1, but i have connect the BOOT button to the GPIO9 pin (inside the wrong pin0)
pin 8 with pullup 10k

the module try to going in downlod mode (when LOW EN pin and LOW GPIO9) but loop a reset whit this error:

ESP-ROM:esp32c3-api1-20210207
Build:Feb 7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0x4 (DOWNLOAD(USB/UART0/1))
Saved PC:0x40048b82
Download boot modes disabled
ESP-ROM:esp32c3-api1-20210207
Build:Feb 7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0x4 (DOWNLOAD(USB/UART0/1))
Saved PC:0x40048b82
Download boot modes disabled
ESP-ROM:esp32c3-api1-20210207
Build:Feb 7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0x4 (DOWNLOAD(USB/UART0/1))
Saved PC:0x40048b82
Download boot modes disabled

the strange is "Download boot modes disabled"

thanks for help

Marco

That is something that happens when a certain eFuse is burned. Did you do something with espefuse.py, or did you get a specific C3 module that e.g. is pre-flashed to work with a cloud provider?

Dear
I haven't changed any efuse and i have 2 different forniture (one from mouser XXN4-A and one from digikey M-4N4A).
both have the same problem.
We thought to have a wromg PCB, then we have tke off a module C3 from a C£-MINI devKitM-1 and soldered it on or PCB and the new modukle (that with issue) on the devKit.
our PCB is ok because all work with the C3 taken from devkit and the new module wired on the devKit have the same issue
we have only soldered the essential wire:
1 - GND
3 - +3.3
5 – GPIO2
8 – EN
22 – GPIO8
23 – GPIO9
30 – RXD0
31 – TXD0

We have also tryed to program with the USB/Jtag but it's the same because the module don't go in program mode

I have checked better on mouser order and i can see that:
Multiprotocol Modules AWS IoT ExpressLink Module, Pre-provisioned w/req'd Certs & ExpressLink Firmware, for Out-of-the-Box connectivity to AWS IoT Core

this coud be for AWS IoT

but in digikey there is not this description, we have ordered the same code.

is there a way to unlock firmware?

Marco

I'm afraid that that is your problem, then. No, there is no way to unlock the firmware; once those eFuses are blown, they cannot be un-blown.