WARNING: Using generated NSIB public/private key-pair.

[snowuyl]

D:\ncs\v2.4.0\bootloader\mcuboot\samples\zephyr\hello-world>west build -b nrf5340dk_nrf5340_cpuapp
-- west build: generating a build system

...

-- Configuring done
-- Generating done
-- Build files have been written to: D:/ncs/v2.4.0/bootloader/mcuboot/samples/zephyr/hello-world/build/b0
=== child image b0 - end ===

CMake Warning at D:/ncs/v2.4.0/nrf/subsys/bootloader/cmake/debug_keys.cmake:36 (message):

--------------------------------------------------------------
--- WARNING: Using generated NSIB public/private key-pair. ---
--- It should not be used for production. ---
--- See CONFIG_SB_SIGNING_KEY_FILE ---
--------------------------------------------------------------

Procedures to reproduce this issue is as follows.

1. Unzipping hello-world.zip to D:\ncs\v2.4.0\bootloader\mcuboot\samples\zephyr folder.

2. cd D:\ncs\v2.4.0\bootloader\mcuboot\samples\zephyr\hello-world

3. west build -b nrf5340dk_nrf5340_cpuapp

[Sigurd]

Hi,

You need to set CONFIG_SB_SIGNING_KEY_FILE when using your own key.

See the documentation here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/config_and_build/bootloaders_and_dfu/bootloader_adding.html#adding-a-custom-signature-key-file

Based on your sample, try setting this in prj.conf:

CONFIG_SB_SIGNING_KEY_FILE="custom_key_dir/custom_priv.pem"

[Daniel K]

I found that I was hitting the error because I didn't have the key file defined for hci_rpmsg; so I fixed my overlays so that the absolute path is supplied via generated files into the child images via <img>_OVERLAY_CONFIG

• mcuboot (CONFIG_BOOT_SIGNATURE_KEY_FILE)
• b0 and hci_rpmsg (CONFIG_SB_SIGNING_KEY_FILE)

I still think the scripts should be fixed to allow override via environment variable, CMake argument, or by path relative to <img>_CONF_DIR.