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
When I run "espefuse.py summary," it displays what appears to be the basic fabric configuration settings.
Nothing is changed before trying to burn the flash key.
Other Steps to Reproduce
I Have Read the Troubleshooting Guide
I confirm I have read the troubleshooting guide.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
burn_key operation gives Burn BLOCK_KEY0 (['BLOCK4']) was not successful
burn_key operation gives Burn BLOCK_KEY0 (['BLOCK4']) was not successful (ESPTOOL-986)
Jan 9, 2025
Hi @Daphne-HU!
The command is correct. If nothing is changed then the problem is likely hardware-related. You can try programming it into a different BLOCK_KEY.
Possible hardware-related issues:
ESD (Electrostatic Discharge): Ensure proper handling and grounding to prevent damage.
Weak Power Supply: Verify the power supply's stability and ensure it meets the ESP32-C3's voltage and current requirements.
Operating System
Xubuntu 20.04 (under WSL)
Esptool Version
4.7.0
Python Version
3.8.10
Chip Description
esp32-C3-mini-1
Device Description
Chip is on a custom PCB
Hardware Configuration
When relevant i can provide pin configurations
How is Esptool Run
Visual studio code
Full Esptool Command Line that Was Run
espefuse.py --debug burn_key BLOCK_KEY0 flash_encryption_key.bin XTS_AES_128_KEY
Esptool Output
More Information
I followed the documentation as noted here, under Using Host Generated Key:
https://docs.espressif.com/projects/esp-idf/en/release-v5.1/esp32c3/security/flash-encryption.html
When I run "espefuse.py summary," it displays what appears to be the basic fabric configuration settings.
Nothing is changed before trying to burn the flash key.
Other Steps to Reproduce
I Have Read the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: