I'm attempting to check out the bootloader under the nRF Connect SDK 2.0.0. This is critical for us to be able to move off of nRF5.
I am starting with the smp_srv sample, and making no changes.
I need to set the signing key to clear up the error message:
=== child image mcuboot - end ===
CMake Warning at C:\ncs\v2.0.0\nrf\modules\mcuboot\CMakeLists.txt:281 (message):
---------------------------------------------------------
--- WARNING: Using default MCUBoot key, it should not ---
--- be used for production. ---
---------------------------------------------------------
So, I've generated a key with:
C:\TestApps\smp_svr>imgtool keygen -k my-key.pem -t rsa-2048
Then inside Visual Studio Code, I select "KConfig", and I go down to "Boot Options", and I select "MCUboot Bootloader Support", and I select "Path to the signing key file".
I put in "my-key.pem".
The same error comes up.
I've seen some people suggesting to put the following in my prj.conf:
CONFIG_MCUBOOT_SIGNATURE_KEY_FILE="my-key.pem"
But that just gets me this error:
CMake Warning at C:\ncs\v2.0.0\nrf\modules\mcuboot\CMakeLists.txt:629 (message): CONFIG_MCUBOOT_SIGNATURE_KEY_FILE is set to "my-key.pem". You are using the NCS Mcuboot signing, which means this option will be ignored. Image signing in NCS is done via the MCUboot image's CONFIG_BOOT_SIGNATURE_KEY_FILE option. Consider setting CONFIG_MCUBOOT_SIGNATURE_KEY_FILE in your application image back to its default value, the empty string.
Sounds like I'm setting it in the wrong place, but I'm using the only "KConfig" option in VSCode, and I'm using the only "prj.conf" in my project!
