Signing script not working as expected

[shreyas.g]

I want to use the signing script as mentioned Technical Documentation (nordicsemi.com), however, with NCS, this script is not automatically being picked up during the build process, unless I do a cmake include myself. 

My current setup is as follows:

- B0 + mcuboot bootloader + application 

- NRF52840 DevKit

- NCS 2.5

Additionally, i want my signed binaries to be picked up by the rest of the build process (for merged.hex, dfu, etc, will this be done automatically?

[Amanda Hsieh]

Hi, 

Could you try the latest version v2.7.0?

Regards,
Amanda H.

[shreyas.g]

Hi Amanda, 

Thanks, I tried it on 2.7 version and it seems to pick up the `-DSIGNING_SCRIPT` arg / target property now. However, the files that generated are not used by the rest of the build process. 

The build still signs with the default imgtool, unless I set

CONFIG_SIGN_IMAGES=n

This is the build log, 

[385/395] Signing files                                                        # This comes from my custom cmake script
[389/395] Generating ../../zephyr/app_update.bin              
image.py: sign the payload                                                 # This is from the ncs' sign.cmake ?
[391/395] Generating ../../zephyr/app_signed.hex
image.py: sign the payload
[392/395] Generating ../../zephyr/app_test_update.hex
image.py: sign the payload
[394/395] Generating zephyr/merged.hex                          # I am not sure which image is picked up here

Do I need to set any cmake var or generate specifically named .hex /.bin files after I have finished signing in my script?