Posted reproducible issue to IDF repo. Including here in case somebody finds this post later. https://github.com/espressif/esp-idf/issues/10925 Also posted this issue as well which is related. https://github.com/espressif/esp-idf/issues/10929 Seems that you cannot have flash encryption enabled (real...

Did some more testing with this today on a dev kit with a fresh project. Starting from scratch the virtual efuses loaded correctly based on what the espefuse.py dump command showed. However, the device still wouldn't boot fully. This is with a simple hello world project. I then enabled flash encrypt...

I have an existing project that runs as desired. I am looking to enable Secure Boot and so I would like to use virtual efuses to test. Before enabling Secure Boot I decided to just enable virtual efuses to make sure everything still ran the same but it does not. In fact it doesn't run at all now. Bu...

If you just want to build you should be able to use the command as described in the image documentation: docker run --rm -v $PWD:/project -w /project espressif/idf:latest idf.py build When you do exec you are not running in the same context where the entrypoint script executed on your docker "run" w...

:roll: Wow, don't I feel foolish. As part of enabling flash encryption I left bootloader logging on and, therefore, had to move the app partition after making more room for the bootloader. This is exactly what was going on. I did an idf.py erase_flash followed by an idf.py encrypted-flash. Everythin...

I am trying to learn more about flash encryption and have read the docs multiple times but am still confused as to why I can dump encrypted flash in development mode with esptool.py and see plain strings. I followed the instructions in the documentation by enabling flash encryption and allowing the ...

@ESP_Sprite Thanks for pointing that out. You made me dig deeper into this and I have a question. The boot log shows "Starting app cpu, entry point is 0x40081610". Is there any way to correlate that address to a physical location or is it a dynamic virtual address? I know the app cpu is starting but...

After applying an OTA update my ESP32 WROOM-32D no longer boots. When I look at the serial output I see that it makes it to the "App cpu up" line but never beyond that which makes me think this is in the bootloader. The WDT then kicks in and resets it. It is stuck in this loop forever. I have device...

Before submitting a bug on the actual repo I wanted to see if this is a known issue or if I'm doing something wrong. It appears to me that the MbedTLS error codes are not being properly stored in the esp_tls_error_handle_t struct. I am doing some testing with expired X509 certs. When I try to connec...