Is It Possible To Encrypt Firmware For Esp8285; What Is The Difference Between Secure Boot V1 And V2; After Enabling Secure Boot, There Is A Build Error Indicating Missing Files. What Could Be The Reasons; After Enabling Secure Boot, Is It Possible For Modules To Be Flashed Again - Espressif Systems ESP Faq

Chapter 4. Software framework

4.7.2 Is it possible to encrypt firmware for ESP8285?

• No, the ESP8285 chip does not support firmware encryption function.
• Both ESP32 and ESP32-S2 support firmware encryption, thus can be your substitution.
• If you insist on using ESP8285, you can achieve data encryption by adding an encrypted chip externally.

4.7.3 What is the difference between secure boot v1 and v2?

Compared with secure boot v1, secure boot v2 has the following improvements: - The bootloader and
app use the same signature format. - The bootloader and app use the same signing key.
Currently, secure boot v1
and later versions, ESP32-C3, ESP32-S2, and ESP32-S3, it is recommended to use
4.7.4 After enabling secure boot, there is a build error indicating missing files. What
could be the reasons？
Error log: /Makefile.projbuild:7/f/ESP32Root/secure_boot_signing_key.pem
Reason: security boot is a function for firmware signature verification, which requires generating key
pairs. - For the method of generating a key pair when secure boot v1 is enabled, please refer to
boot v1 key generation. - For the method of generating a key pair when secure boot v2 is enabled, please
refer to secure boot v2 key

4.7.5 After enabling secure boot, is it possible for modules to be flashed again?

• If the secure boot v1 is configured as one-time, then it can only be flashed once and the bootloader firmware
cannot be reflashed.
• If the secure boot v1 is configured as reflashable, then the bootloader firmware can be flashed again.
• The secure boot v2 allows reflashing the bootloader and app firmware.
4.7.6 With flash encryption enabled, a module reports an error as flash read error
after reflashed. How to resolve such issue?
With flash encryption enabled, the module will not support plaintext firmware flash. For common fail-
ures, please refer to Possible
reflash the plaintext firmware, or directly flash the encrypted firmware to devices referring to the
encryption example.
Note: Please note there is a time limit for the flash encrypted function.
Espressif Systems
is only reommended for earlier versions than ESP32 v3.0. For ESP32 v3.0
generation.
Failures. You can use the
105
Submit Document Feedback
espefuse script to disable the encryption and then
secure boot v2.
secure
flash
Release master