mcuboot CONFIG_MCUBOOT_ACTION_HOOKS

[Krzysztof Szewczyk]

Hello!

I'm working on some project using Fanstel BM832 module. I'm using the configuration based on board nrf52dk_nrf52832, with some minor modifications (led's and button pinouts are changed using nrf52dk_nrf52832.overlay). I'm trying to use the bluetooth bootloader. I enabled the bootloader by adding the:
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y
into my prj.conf file.
I also created the child_image/mcuboot.conf file with those entries:
CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y
CONFIG_BOOT_SIGNATURE_KEY_FILE=.....

For now everything works fine, except that I would like to indicate that "bootloading" (copying from 2nd slot in flash to the 1st slot) is in progress, by blinking one of my LEDs.
I know that I can enable the bootloader action hooks by enabling the option:
CONFIG_MCUBOOT_ACTION_HOOKS=y
in my child_image/mcuboot.conf file.
I need to add a c file containing the mcuboot_status_change to the mcuboot child image build. How can I do this without modifying the nrf connect sdk (just by adding my own files in my project folder).

I have also another question: How can I detect the bootloading process (when the firmware is uploading by the bluetooth to the flash 2nd slot) in my application. Are there any hooks also on the application side?

Best regards,
Krzysztof Szewczyk

[Sigurd Hellesvik]

Hi,

Lets start with the last question:

I have also another question: How can I detect the bootloading process (when the firmware is uploading by the bluetooth to the flash 2nd slot) in my application. Are there any hooks also on the application side?

See MCUmgr Callbacks.
You can see an example of this in our matter samples.

I need to add a c file containing the mcuboot_status_change to the mcuboot child image build. How can I do this without modifying the nrf connect sdk (just by adding my own files in my project folder).

You can see an example of this at https://github.com/nrfconnect/sdk-zephyr/tree/main/tests/boot/mcuboot_recovery_retention.

However, this test uses Sysbuild, which is not even in "Experimental" status yet, so no promises on how that will interact with other stuff.

Regards,
Sigurd Hellesvik

[Nicolas Goualard]

Hi, Sigurd Hellesvik , I am also interested in using a mcuboot_status_change function without having to modify the SDK.
I have found this related question : MCUBoot DFU OTA Best way to obtain actions ( Hooks ) also Android vs iOS discrepancies.

in which someone puts a c file in the custom board "boards" folder.
Is this the preferred way to do this, or is there a better way now ?

[Sigurd Hellesvik]

Hi Nicolas,

Did you try to use MCUmgr Callbacks?

I think you should be able to catch these callbacks from your app. (Not the boards folder, just from the application you have)

Regards,
Sigurd Hellesvik

[Nicolas Goualard]

Yes, I am successfully using MCUMgr callbacks to get the events of a new image being uploaded to slot 1. However, when the device gets restarted, my understanding is that MCUBoot swaps the new image from slot 1 to slot 0. At this point the application has not started yet, so I cannot get callbacks, but I still would like to inform the user that something is happening.

The method described in the post I mentioned is working for me, I was just wondering if this is the preferred way of doing this kind of things ?

[Sigurd Hellesvik]

MCUboot has some logs on serial when it initializes a swap operation.
However, no LED blinking functionality is available.

You could always fork MCUboot and add some such functionality yourself if you want.

Does this answer your question?

[Nicolas Goualard]

Yes, I think so, thanks.