Signing file with a relative key path

RE: Signing file with a relative key path

Menon — Tue, 29 Oct 2024 12:16:27 GMT

Hello,

Sorry I couldn’t test this myself, as I was tied up with other work. But I found a similar issue reported earlier where the customer was able to get it working. Please have a look and let me know if this helps. If it doesn’t, I can try it on my end.

Kind regards,

Abhijith

RE: Signing file with a relative key path

QuentinD — Tue, 29 Oct 2024 09:33:09 GMT

Could you answer me?

Thank you

RE: Signing file with a relative key path

QuentinD — Thu, 24 Oct 2024 14:05:38 GMT

Have you been able to try?

RE: Signing file with a relative key path

QuentinD — Wed, 23 Oct 2024 12:51:46 GMT

Hello,

No it doesn't work.

For m'y key to be taken into account during compilation, I need to define SB_CONFIG_BOOT_SIGNATURE_KEY_FILE in the sysbuild.conf file. Doing it instead in the applications CMakeLists.txt or in the sysbuild.cmake does not fix my problem.

Could you try on your side qnd tell me what do you do exactly to do it?

Thank you

RE: Signing file with a relative key path

Menon — Tue, 22 Oct 2024 16:28:57 GMT

Hello,

I think this needs to be done as one of the first things in your CMakeLists.txt, or before any find_package, include, or SDK-related commands. Set and convert paths early in CMakeLists.txt

Kind Regards,

Abhijith

RE: Signing file with a relative key path

QuentinD — Tue, 22 Oct 2024 14:40:23 GMT

My board is the PCA10056 (nRF52840 DK)

If I replace the command "set(keyfile "${SB_CONFIG_BOOT_SIGNATURE_KEY_FILE}" in b0_mcuboot_signing.cmake file by yours, it works but it works also if I write "set(keyfile "${APP_DIR}/keys/mcuboot_private.pem".

So where can I put this command to not modify the SDK files ?

Thank you

RE: Signing file with a relative key path

Menon — Mon, 21 Oct 2024 18:22:01 GMT

Hello,

In nRF Connect SDK v2.7.0, the introduction of Sysbuild might have changed how the build system manages paths and configurations, but I'm not completely sure as I haven't tested it myself. Which Nordic chip/DK are you using?

Could you try using get_filename_component inside CMake? This command will convert a relative path to an absolute path. For example: get_filename_component(keyfile "${SB_CONFIG_BOOT_SIGNATURE_KEY_FILE}" ABSOLUTE ${CMAKE_CURRENT_SOURCE_DIR}). See this.

#  Define the relative APP_DIR

# Define the relative path to the key file

# Convert the relative path to an absolute path for signing purposes (using the get_filename_component())

Kind Regards,

Abhijith