Hi,
i'm a litte bit confused about the Secure Boot functionality. I'm using a custom example and the SDK 17.0.2 Secure bootloader. When generating a DFU package I have to specify my private.key to encrypt the signature and sign the DFU image using ECDSA_P256_SHA256.
So this key/validation is only used for the DFU-update process?
When I also want to implement a secure boot validation for every boot AFTER the DFU I also have to add the VALIDATE_ECDSA_P256_SHA256 Option (for APP and or SD)?
When I want to implement a secure boot validation for every boot already BEFORE a DFU I have to add the VALIDATE_ECDSA_P256_SHA256 Option already when generating the Bootloader-settings file and flashing the chip for the first time?
Do I need to enable NRF_BL_APP_SIGNATURE_CHECK_REQUIRED in the bootloaders skd_config.h to get the boot validation finally enabled/work, or what does this option do in this case?
Kind regards