Hi @askash kadam,

I think you should use the element for the config to attach the cert bundle instead of . The element expects a certificate string whereas expects a callback function pointer.

Thank you!

Hi @fschuetz, A similar issue has been reported in the mbedtls issues as well, could you please take a look into this thread https://github.com/libssh2/libssh2/commit/2e4c5ec4627b3ecf4b6da16f365c011dec9a31b4#commitcomment-141379351 . I think the crux of the above discussion is that the mbedtls_pk_lo...

Hello @vkp2808, I tried using the v5.2.2 tag of ESP-IDF but I was unable to recreate the issue. Using which ESP-IDF release are you facing the issue? You could also try out secure boot using QEMU (emulator) to "conserve" your testing devkits: 1. Build your firmware 2. Merge the binaries using: (cd b...

Hi @bramalka, I would suggest you to use the Flash Encryption development mode for generating a production-ready device. Reference docs: https://docs.espressif.com/projects/esp-idf/en/stable/esp32/security/flash-encryption.html#flash-enc-release-mode . While using development mode, you can disable f...

Hello @mikecarlos,

The steps that you have followed are correct and even I tried them out at my end and the device boots correctly.
But I am not sure why the bootloader does not boot up in your case. Could you share your sdkconfig file to help me to reproduce the issue?

Hi @yaghmr,

Addressing this issue at: https://github.com/espressif/esp-insigh ... 1976104736.

Thanks!

Skimmed through the sdkconfig and it looks just normal.

I'll try to build a smaller repro.

Thanks that would be really helpful!

Hi @kasperl,

Let's continue the discussion here: https://esp32.com/viewtopic.php?f=13&t= ... 25#p128625

Thanks!

Hello @kasperl,

1. Could you share the sdkconfig file of your use case?
2. Also, it would be great if you could create and share a minimal example that would help me to reproduce this issue.

Thanks!

Hello @minhbka, Secure boot should work even after an ESP-IDF version update. Taking a look at the error log, it looks like bootloader verification has failed. And by the steps that you have mentioned, seems like you flashed the new reflashable bootloader digest, app, and partition table, but missed...