Closed listout closed 1 year ago
Any help or ideas?
@listout
Probably esp_efuse_get_pkg_ver
refers to the virtual EFuse block and reads an incorrect version as highlighted below:
As highlighted in the help for CONFIG_EFUSE_VIRTUAL
, this features is primarily for the testing purpose and it is difficult to ensure functionality of all features with this config.
I would recommend that you try our qemu port for verifying security features on ESP32.
Hope this helps!
Thank you @mahavirj. I've been using qemu for testing secure boot, unfortunately for flash encryption, it's not possible and the wiki says info added later.
Thanks for the feedback! I will update the wiki for the flash enc instructions and notify you.
Answers checklist.
IDF version.
v4.4.3
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-PICO-DevKitM-2
Power Supply used.
USB
What is the expected behavior?
I was testing Secure boot (version 2) and flash encryption, to reduce the chances of bricking my device I decided to use virtual efuses (stored in flash). With all these three options enabled I can't run any application (in this case hello_world example from v4.4.3); the device would boot showing device informations and in the psram section it would show This chip is ESP32-D0WD whereas my chip is ESP32 Pico Mini V3 02, and after some time the device would reboot.
When I turn off SPIRAM support, the code/application runs as expected.
What is the actual behavior?
Application run and correct chip is detected with secure boot, flash encryption and virtual efuses enabled.
Steps to reproduce.
Debug Logs.
More Information.
Minimal sdkconfig
Partition table
Code I used