Modify and log MCUBOOT version

RE: Modify and log MCUBOOT version

Amanda Hsieh — Fri, 05 May 2023 15:07:05 GMT

Set CONFIG_FW_INFO_FIRMWARE_VERSION in application/child_image/mcuboot.conf. See my colleague's example in this post.

-Amanda H.

RE: Modify and log MCUBOOT version

Anthony Ambuehl — Thu, 04 May 2023 23:49:37 GMT

I think I have misunderstood CONFIG_MCUBOOT_IMAGE_VERSION.

I am now understanding it like this:

CONFIG_MCUBOOT_IMAGE_VERSION -- S0/S1 application version passed during application dfu package generation. mcuboot will receive this version in the metadata of a dfu image.

CONFIG_REST_FOTA_SAMPLE_VERSION -- version string specific to the sample but not part of DFU

CONFIG_FW_INFO_FIRMWARE_VERSION -- version of mcuboot which secureboot/b0 will receive via metadata.

It seems if I want to have a consistent version logged by mcuboot that matches the mcuboot dfu package metadata then I need to set CONFIG_FW_INFO_FIRMWARE_VERSION.

Should I

* set CONFIG_FW_INFO_FIRMWARE_VERSION in application prj.conf

* set CONFIG_FW_INFO_FIRMWARE_VERSION in application/child_image/mcuboot.conf

* both ?

RE: Modify and log MCUBOOT version

Anthony Ambuehl — Thu, 04 May 2023 23:28:39 GMT

Perfect!

Could you give me an idea of which CMake file I need to edit and some example of what it would look like? Is it possible to set this up from the application folder or would it require editing SDK files?

RE: Modify and log MCUBOOT version

Amanda Hsieh — Wed, 03 May 2023 12:45:41 GMT

Hi,

This has to be solved in CMake, as there is no mechanism in Kconfig that could solve this.

In CMake you have access to all kconfig options for all images, and it is possible to set options for specific child images (see multi_image.cmake for details on how to pass options to specific child images).

Regards,
Amanda H.

RE: Modify and log MCUBOOT version

Anthony Ambuehl — Tue, 02 May 2023 15:20:21 GMT

That is not correct.

Having the application report the version of mcuboot it was built with completely missing the point. The mcuboot is updated independently from the application by secureboot.

During the build a dfu_mcuboot.zip file is generated. This file contains update images for mcuboot by itself. The secure boot handles the mcuboot update. I have proven this is true by manually editing the log lines in v2.3.0/bootloader/mcuboot/zephyr/main.c and then performing the update and confirming the updated logs were generated after entering the mcuboot.

Now I would like to pass a CONFIG variable that is set to a version string to mcuboot. How do I pass the value of CONFIG_MCUBOOT_IMAGE_VERSION into the mcuboot childimage build?

I have been able to add my own CONFIG_ANTHONY_VERSION to mcuboot and log that value, but I don't know how to make CONFIG_ANTHONY_VERSION = CONFIG_MCUBOOT_IMAGE_VERSION and to pass it from the application folder to the mcuboot childimage build.

RE: Modify and log MCUBOOT version

Amanda Hsieh — Tue, 02 May 2023 13:53:19 GMT

Hi,

The mcuboot cannot be updated singly. It has to be built with an application to update, so you can use the application to report the mcuboot version.

-Amanda H.

RE: Modify and log MCUBOOT version

Anthony Ambuehl — Mon, 01 May 2023 19:28:33 GMT

I'm specifically wanting mcuboot to log the version since I am testing mcboot updates. The application is not aware of the mcuboot update and would log the version it was built with, not the version that is actually running with.

RE: Modify and log MCUBOOT version

Anthony Ambuehl — Mon, 01 May 2023 19:26:33 GMT

Your log shows the application reporting the value of CONFIG_MCUBOOT_IMAGE_VERSION, however the mcuboot is actually not logging the version it was built with. The mcuboot logs are ending at "Bootloader chainload address offset: 0xc000" The subsequent logs are the application code.

The main.c for mcuboot is bootloader\mcuboot\boot\zephyr\main.c

RE: Modify and log MCUBOOT version

Amanda Hsieh — Mon, 01 May 2023 15:57:58 GMT

Hi,

In prj.conf, you can set

CONFIG_MCUBOOT_IMAGE_VERSION="1.0.0+0"

In the main, you can have this code:

void main(void)
{
    printk("Board config %s\n", CONFIG_BOARD);
	printk("IMAGE_VERSION %s\n", CONFIG_MCUBOOT_IMAGE_VERSION);
	printk("build time: " __DATE__ " " __TIME__ "\n");
}

Here is my test project devzone.nordicsemi.com/.../hello_5F00_world_5F00_mcuboot.7z and
the output
.

Beware that this code/configuration is not fully tested or qualified and should be considered provided “as-is”. Please test it with your application and let me know if you find any issues.

Regards,
Amanda H.