-
Notifications
You must be signed in to change notification settings - Fork 146
Closed
Description
Describe the problem
When flashing my firmware to an ESP32-C3 using cargo-espflash 4.0-dev (commit 4006bd0), the device fails to boot, and the log shows the following error:
ESP-ROM:esp32c3-api1-20210207
Build:Feb 7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x40048b82
SPIWP:0xee
mode:DIO, clock div:2
load:0x3fcd5820,len:0x1574
load:0x403cc710,len:0xc34
load:0x403ce710,len:0x2f64
entry 0x403cc71a
I (35) boot: ESP-IDF v5.4.1-426-g3ad36321ea 2nd stage bootloader
I (35) boot: compile time Apr 24 2025 15:55:47
I (35) boot: chip revision: v0.3
I (37) boot: efuse block revision: v1.2
I (40) boot.esp32c3: SPI Speed : 40MHz
I (44) boot.esp32c3: SPI Mode : DIO
I (48) boot.esp32c3: SPI Flash Size : 4MB
I (51) boot: Enabling RNG early entropy source...
I (56) boot: Partition Table:
I (59) boot: ## Label Usage Type ST Offset Length
I (65) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (71) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (78) boot: 2 factory factory app 00 00 00010000 003f0000
I (84) boot: End of partition table
I (88) esp_image: segment 0: paddr=00010020 vaddr=3c000020 size=08d10h ( 36112) map
E (95) boot_comm: Image requires efuse blk rev >= v419.62, but chip is v1.2
E (102) boot: Factory app partition is not bootable
E (106) boot: No bootable app partitions in the partition table
I’m not sure if I might be missing a required setting or configuration to support this chip revision, or if this could be related to how espflash generates or flashes the image.
If you have any suggestions or workarounds, I would greatly appreciate your guidance.
Environment
- Chip: ESP32-C3 (rev v0.3, efuse block rev v1.2)
- cargo-espflash version: 4.0-dev (
4006bd0) - esp-hal version: 1.0.0-beta.0 (
e5c66e8) - Rust toolchain: rustc 1.89.0-nightly (4d051fb30 2025-05-18)
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done