nrf5340: How to set image version (SDK is ncs V2.5.2)

[Yanpengwu]

Hi Support Team,

I tried several ways to set the image version but failed. My SDK is ncs V2.5.2.
1. set(CONFIG_MCUBOOT_IMAGE_VERSION "1.0.0") in CMakeLists.txt: did not work.
2. try to set CONFIG_MCUBOOT_IMAGE_VERSION="1.0.0" in prj.conf or child_image\mcuboot.conf: both results are undefined symbol MCUBOOT_IMAGE_VERSION
3. try to set CONFIG_FW_INFO_FIRMWARE_VERSION=1 in child_image and \mcuboot.conf: , did not work.

When I use the below command to check the image version, it always is version: 0.0.0+0:

python C:\ncs\v2.5.2\bootloader\mcuboot\scripts\imgtool.py dumpinfo app_update.bin
Printing content of signed image: app_update.bin

#### Image header (offset: 0x0) ############################
magic:              0x96f3b83d
load_addr:          0x0
hdr_size:           0x200
protected_tlv_size: 0x0
img_size:           0x4afe0
flags:              0x0
version:            0.0.0+0
############################################################

Could you help clarify the config in prj.conf and child_image\mcuboot.conf for the image version setting? When I upload the new image to the slot 1, MCUboot not swap and run it, I guess the reason is both new and old image have the same version 0.0.0+0.
Thank you very much.

Best regards,
Yanpeng Wu

[Turbo J]

See zephyr documentation "Application version management". You are supposed to use a magic VERSION file where those numbers will be pulled from.

[AHaug]

Hi,

As Turbo J mentioned, you can do this by following https://docs.nordicsemi.com/bundle/ncs-2.5.2/page/zephyr/build/version/index.html 

Kind regards,
Andreas

[Yanpengwu]

 Hi Andreas and Turbo,

Thanks so much for your precise guidance. It works:).

Best regards,
Yanpeng Wu