Building only the app in a multi-image project

RE: Building only the app in a multi-image project

Maria Gilje — Fri, 01 Mar 2024 14:45:57 GMT

Hello,

[quote user="jsantosrico"]Hi Maria, sorry but I totally missed your comment, and noticed only now that Burt has replied to it.[/quote]

No worries about missing my reply.

[quote user="Burt"]There are a couple of additional steps required; Hakon Alseth from Nordic showed me in ticket Case ID 319394, (+) Asset_tracker_v2->Application description->Configuration in nRF Connect SDK document - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com).[/quote]

Thank you, Burt for sharing the ticket with additional steps! Does the ticket help you, jsantosrico, to solve your current build error?

Best regards,

Maria

RE: Building only the app in a multi-image project

Burt — Thu, 29 Feb 2024 14:45:47 GMT

There are a couple of additional steps required; Hakon Alseth from Nordic showed me in ticket Case ID 319394, (+) Asset_tracker_v2->Application description->Configuration in nRF Connect SDK document - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com).

Burt

RE: Building only the app in a multi-image project

jsantosrico — Thu, 29 Feb 2024 14:30:53 GMT

Hi Maria, sorry but I totally missed your comment, and noticed only now that Burt has replied to it.

I followed your steps, built pristine, renamed my own "pm_static.yml" to "pm_static.old", and moved "pm.config" from build to root and renamed to "pm_static.yml", added "CONFIG_MCUBOOT_BUILD_STRATEGY_SKIP_BUILD=y" to my "proj.conf"

Built pristine again.

1. First phase, "build of child image b0", takes the same amount of time (~8s), same log output.

2. Next step, after "=== child image b0 - end ===" in "my build", is the building of the bootloader (~8s) too, but with your changes, I get "Skipping building of mcuboot". So that seems to work as expected

3. Next Step "Child image s1_image - begin" fails with

=== child image s1_image - begin ===

CMake Error at C:/Users/joel.santos/Workspace/NordicWorkspace/nrf/cmake/multi_image.cmake:248 (get_property):

get_property could not find TARGET mcuboot_subimage. Perhaps it has not

yet been created.

RE: Building only the app in a multi-image project

Burt — Tue, 27 Feb 2024 04:25:31 GMT

Actually, neither build strategy will bulid.

Burt

RE: Building only the app in a multi-image project

Burt — Tue, 27 Feb 2024 04:20:58 GMT

Hello Maria, Burt Silverman here. I have tried this procedure with CONFIG_MCUBOOT_BUILD_STRATEGY_SKIP_BUILD=y in v2.5.0, nrf9160dk_nrf9160_ns, asset_tracker_v2. It does not build. I have tried multiple methods: copying/not copying pm.config, and pristine/not pristine builds. No go. Please help. Thanks.

Burt

RE: Building only the app in a multi-image project

Maria Gilje — Tue, 19 Dec 2023 12:33:49 GMT

Hello,

You can specify the *_BUILD_STRATEGY for MCUboot to be *_SKIP_BUILD or *_USE_HEX_FILE. SKIP_BUILD is useful for DFU cases where the application is the only firmware to be updated. USE_HEX_FILE is useful when you will flash the device. In your case it looks like CONFIG_MCUBOOT_BUILD_STRATEGY_USE_HEX_FILE is the suitable option.

The full steps needed are as follows:

Configure and build the application as before (as multi image).
Copy the generated pm.config from the build directory to the project directory and rename it to pm_static.yml.
In prj.conf: set the build strategy to the option most suitable for you.
Make the changes you want in the application and rebuild with the new build strategy set.

Best regards,

Maria