You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
esptool reports flash encryption enabled on factory-new esp32-c61 (ESPTOOL-1371) #1182
$ esptool write-flash 0x10000 firmware.bin
esptool v5.3.1
Connected to ESP32-C61 on /dev/ttyAMA0:
Chip type: Unknown ESP32-C61 (revision v1.0)
Features: Wi-Fi 6, BT 5 (LE), Single Core, 160MHz
Crystal frequency: 40MHz
MAC: 88:56:a6:cb:25:74
Stub flasher is already running. No upload is necessary.
Hard resetting via RTS pin...
A fatal error occurred: Detected flash encryption enabled and download manual encrypt disabled.
Data must be encrypted appropriately before flashing.
Flashing plaintext data may brick your device! Use the force argument to override the warning.
More Information
I am using a brand new QFN40 ESP32-C61 from Digikey. I soldered the chip to the board and esptool can talk to it over serial. I tried to flash a hello world application but the tool says flash encryption is enabled.
checking espefuse reports
SPI_BOOT_CRYPT_CNT (BLOCK0) Enables flash encryption when 1 or 3 bits are set = Enable r/W (0b111)
which is hard to believe from a factory-new chip from a reputable dealer. Could this be an incompatibility with esptool because the ESP32-C61 is still a very new chip? I've added the efuse dump below.
changed the title [-]esptool reports flash encryption enabled on factory-new esp32-c61[/-][+]esptool reports flash encryption enabled on factory-new esp32-c61 (ESPTOOL-1371)[/+]on Aug 21, 2026
Hi @donpdonp! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.
Here is a response you can post to the GitHub issue:
Hi,
Thank you for reporting this.
Why this happens
esptool checks eFuse settings before writing to flash to protect devices from being bricked by accidentally overwriting encrypted firmware with plaintext data [Encrypted Flash Protection]. When it detects flash encryption enabled and manual download encryption disabled, it blocks standard flashing [Encrypted Flash Protection].
However, looking at the provided eFuse dump:
None of the key blocks (BLOCK4 through BLOCK9) have keys burned or configured (they are all zeroes).
An unprogrammed/factory chip should have SPI_BOOT_CRYPT_CNT = 0 (flash encryption disabled) [Troubleshooting].
Because the ESP32-C61 is a newer chip target [v5 Migration Guide], this behavior likely stems from an eFuse map offset or bitfield definition discrepancy in esptool/espefuse incorrectly interpreting the ESP32-C61's BLOCK0 bits as SPI_BOOT_CRYPT_CNT = 0b111.
Workaround / Flashing in the Meantime
To bypass the safety check and proceed with flashing your firmware, you can use the --force flag or the --ignore-flash-enc-efuse argument (introduced in esptool v5 as the replacement for --ignore-flash-encryption-efuse-setting [v5 Migration Guide]):
I agree the problem is likely to be with the esptool's reporting of the encryption bits being set when they are not set. So I tried --force and got a checksum/MD5 error.
donp@dustnote hello-c61 $ $ esptool write-flash --force 0x10000 esp32-c61-lapnoi/firmware.bin
esptool v5.3.1
Connected to ESP32-C61 on /dev/ttyAMA0:
Chip type: Unknown ESP32-C61 (revision v1.0)
Features: Wi-Fi 6, BT 5 (LE), Single Core, 160MHz
Crystal frequency: 40MHz
MAC: 88:56:a6:cb:25:74
Stub flasher is already running. No upload is necessary.
Configuring flash size...
Flash will be erased from 0x00010000 to 0x00058fff...
Wrote 296448 bytes (160724 compressed) at 0x00010000 in 16.6 seconds (142.7 kbit/s).
Input MD5: 0dae5e86f9d52d9858ba002151f8725e
Flash MD5: afa8cda787cbdd7ffbe0a8fb96243330
Hard resetting via RTS pin...
A fatal error occurred: MD5 of file does not match data in flash!
I just find that hard to believe - I soldered this chip myself from a shipment from Digikey (obviously a reputable dealer). The chip was completely clean/new looking. The espfuse report means it was not only burned before, but enabled twice so the flash encryption cannot be turned off again. I've never done anything efuse related with any of my esp32 chips. Maybe its a problem with the pcboard layout? At any rate I'll build another prototype board with another new esp32-c61 (from the same digikey shipment of 5 pieces) and see if that changes anything.
There are some patches linked to this issue which were found during investigating this issue. However, I couldn't reproduce the issue and I believe the eFuses were previously burned. I would suggest to send back those chip(s) which where delivered to you in this state.
Thanks for the followup. I put together a second prototype board with the 2nd chip from that batch of 5. It worked immediately.
$ esptool --port /dev/ttyAMA0 --baud 115200 write-flash 0x0 esp32-c61-lapnoi/firmware.factory.bin
esptool v5.3.1
Connected to ESP32-C61 on /dev/ttyAMA0:
Chip type: ver 1 ESP32-C61 (revision v1.0)
Features: Wi-Fi 6, BT 5 (LE), Single Core, 160MHz
Crystal frequency: 40MHz
MAC: 88:56:a6:cb:25:60
Stub flasher running.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00058fff...
Wrote 361984 bytes (175086 compressed) at 0x00000000 in 18.3 seconds (158.4 kbit/s).
Hash of data verified.
Hard resetting via RTS pin...
the faulty chip reported
Chip type: Unknown ESP32-C61 (revision v1.0)
I don't think it tells me anything useful but at least I can continue development.
Activity
[-]esptool reports flash encryption enabled on factory-new esp32-c61[/-][+]esptool reports flash encryption enabled on factory-new esp32-c61 (ESPTOOL-1371)[/+]github-actions commentedon Aug 21, 2026
Hi @donpdonp! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.
Here is a response you can post to the GitHub issue:
Hi,
Thank you for reporting this.
Why this happens
esptoolchecks eFuse settings before writing to flash to protect devices from being bricked by accidentally overwriting encrypted firmware with plaintext data [Encrypted Flash Protection]. When it detects flash encryption enabled and manual download encryption disabled, it blocks standard flashing [Encrypted Flash Protection].However, looking at the provided eFuse dump:
BLOCK4throughBLOCK9) have keys burned or configured (they are all zeroes).SPI_BOOT_CRYPT_CNT = 0(flash encryption disabled) [Troubleshooting].Because the ESP32-C61 is a newer chip target [
v5Migration Guide], this behavior likely stems from an eFuse map offset or bitfield definition discrepancy inesptool/espefuseincorrectly interpreting the ESP32-C61'sBLOCK0bits asSPI_BOOT_CRYPT_CNT = 0b111.Workaround / Flashing in the Meantime
To bypass the safety check and proceed with flashing your firmware, you can use the
--forceflag or the--ignore-flash-enc-efuseargument (introduced in esptool v5 as the replacement for--ignore-flash-encryption-efuse-setting[v5Migration Guide]):or
donpdonp commentedon Aug 21, 2026
I agree the problem is likely to be with the esptool's reporting of the encryption bits being set when they are not set. So I tried --force and got a checksum/MD5 error.
dobairoland commentedon Aug 24, 2026
Hi @donpdonp.
espefuse summaryso we can compare it with the output of dump.donpdonp commentedon Aug 24, 2026
here is the summary. the board has been power cycled many times. a new dump is included at the end. I dont think anything has changed.
dobairoland commentedon Aug 24, 2026
Thank you for the additional information. It looks to me that espefuse does everything right. We also tested this on our ESP32-C61 dev board.
I've asked our eFuse expert to take a look at this. But likely the eFuses have really been burned before.
donpdonp commentedon Aug 25, 2026
I just find that hard to believe - I soldered this chip myself from a shipment from Digikey (obviously a reputable dealer). The chip was completely clean/new looking. The espfuse report means it was not only burned before, but enabled twice so the flash encryption cannot be turned off again. I've never done anything efuse related with any of my esp32 chips. Maybe its a problem with the pcboard layout? At any rate I'll build another prototype board with another new esp32-c61 (from the same digikey shipment of 5 pieces) and see if that changes anything.
fix(esp32-c61): Identify in-package flash and PSRAM variants
fix(espefuse): Correct eFuse error and date register offsets
dobairoland commentedon Aug 31, 2026
There are some patches linked to this issue which were found during investigating this issue. However, I couldn't reproduce the issue and I believe the eFuses were previously burned. I would suggest to send back those chip(s) which where delivered to you in this state.
donpdonp commentedon Aug 31, 2026
Thanks for the followup. I put together a second prototype board with the 2nd chip from that batch of 5. It worked immediately.
the faulty chip reported
I don't think it tells me anything useful but at least I can continue development.
fix(esp32-c61): Identify in-package flash and PSRAM variants
fix(espefuse): Correct eFuse error and date register offsets