SB_CONFIG_BOOT_SIGNATURE_KEY_FILE and SB_CONFIG_BOOT_ENCRYPTION_KEY_FILE path issue

[taspon98]

According to developer.nordicsemi.com/.../migration_sysbuild.html , the config variable SB_CONFIG_BOOT_SIGNATURE_KEY_FILE and SB_CONFIG_BOOT_ENCRYPTION_KEY_FILE should be absolute. However, entering an absolute path triggers the following error during build. Changing this to be 

ninja: error: '.........../bootloader/mcuboot/bootloader/mcuboot/enc-ec256-pub.pem', needed by 'zephyr/autogen-enckey.c', missing and no known rule to make it

Changing this to be the relative path gives this error instead

CMake Error at ........../nrf/cmake/sysbuild/image_signing.cmake:43 (message):
  west sign can't find file

[dejans]

Hi,

Could you provide more information on what you try to achieve?

Which NCS version do you use?

There is a guide how to add bootloader chain using sysbuild. Please note that currently NCS v2.7.0 has experimental support in VS Code.

Best regards,
Dejan

[taspon98]

I am using NCS 2.7.0. I am trying to make my application build correctly with mcuboot by supplying a custom signature and encryption key. However, when assigning the absolute path to these config variables zephyr/autogen-enckey.c complains since it looks at the relative path, but changing it back to the relative path triggers an error in nrf/cmake/sysbuild/image_signing. Therefore, I am confused on how to correct path the custom key path using sysbuild.