MCUBOOT build failed with PK

RE: MCUBOOT build failed with PK

Sigurd Hellesvik — Tue, 13 Jun 2023 09:11:57 GMT

Hi,

I will continue to help in this case.

Looks like you are trying to build MCUboot as standalone.
In the nRF Connect SDK, we generally recommend building it as a child image of a project.

To set custom keys using the multi-image approach, see my MCUBoot Custom Key with SMP Server sample.

You can still build it standalone though. If this is what you want, there is a bug.

Here is the fix for said bug:

diff --git a/boot/zephyr/nrf_cleanup.c b/boot/zephyr/nrf_cleanup.c
index f567b97e..6344a985 100644
--- a/boot/zephyr/nrf_cleanup.c
+++ b/boot/zephyr/nrf_cleanup.c
@@ -20,7 +20,7 @@
 
 #include <string.h>
 
-#if defined(USE_PARTITION_MANAGER)
+#if (USE_PARTITION_MANAGER)
 #include <pm_config.h>
 #endif

Regards,
Sigurd Hellesvik

RE: MCUBOOT build failed with PK

KLarocqueEMFluids — Wed, 07 Jun 2023 12:20:50 GMT

Any updates on the matter ?

RE: MCUBOOT build failed with PK

KLarocqueEMFluids — Mon, 05 Jun 2023 13:17:16 GMT

In steps how I did

1. I used OpenSSL to generate a RSA 2048 key in WSL. openssl genrsa -out private.pem 2048

2. I put that private key .pem file under a folder called 'keys' inside my project

3. Within my CmakeLists.txt file I added these lines to find the path relative to my key folder as it should be appended within the child image mcuboot.conf

set(mcuboot_key_file ${CMAKE_CURRENT_LIST_DIR}/keys/private.pem)
set(mcuboot_CONFIG_BOOT_SIGNATURE_KEY_FILE "\"${mcuboot_key_file}\"")
if (EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/mcuboot.conf")
    list(APPEND mcuboot_OVERLAY_CONFIG
      "${CMAKE_CURRENT_SOURCE_DIR}/mcuboot.conf"
      )
endif()

As you can see within my logs the file is found and not skipped to the DEBUG option.

RE: MCUBOOT build failed with PK

Edvin — Mon, 05 Jun 2023 13:09:24 GMT

Hello,

How did you generate and include your private key to your project?

Best regards,

Edvin