specify multi-image build app version

[rerickson]

When building an app with mcuboot as part of a multi-image build, how can I pass the app version to imgtool so the app_update.bin header gets created with the correct app version?

[Øyvind]

Hi, 

Can you please elaborate? Is there something that should be more clear in the mcuboot documentation?

Kind regards,
Øyvind

[rerickson]

When building your app with mcuboot it triggers a multi-image build to build the mcuboot child image along with your app.  During this process the application hex gets signed by default.  As part of the signing process you can specify the apps version so that version gets included in the image header.  How can I specify that app version when running the west build command?

[Øyvind]

Hi Ryan, 

Thanks for clarifying. I will talk to our NCS developers to get a final answer.

-Øyvind

[rerickson]

Any update?

[Øyvind]

My sincere apologies for the late reply, Ryan. Most of our developers are back this week. I will ask again. I did find an answer, however, I don't think that's what you are looking for:

Running ninja clean && ninja -v, it will output:

[236/238] cmd.exe /C "cd /D C:\SDK\ncs\nrf\applications\asset_tracker\build\modules\mcuboot && C:\Python37\python.exe C:/SDK/ncs/nrf/scripts/bootloader/generate_zip.py --bin-files C:/SDK/ncs/nrf/applications/asset_tracker/build/zephyr/app_update.bin --output C:/SDK/ncs/nrf/applications/asset_tracker/build/zephyr/dfu_application.zip load_address=0x1c200 version_MCUBOOT=0.0.0+0 type=application board=nrf9160dk_nrf9160 soc=nRF9160_SICA"

[rerickson]

To manually sign an image you would do:

west sign -t imgtool -d /build/my_app -- --version 1.0.0

How can I pass that version argument to a multi-image build when using NCS.

[Øyvind]

rerickson said:

How can I pass that version argument to a multi-image build when using NCS.

You should be able to this using:

west build -- '-DCONFIG_MCUBOOT_IMAGE_VERSION="1.0.0+0"'

Let me know how that works for you. 

Kind regards,
Øyvind