MCUboot test and confirm with DFU Target library

RE: MCUboot test and confirm with DFU Target library

BrianW — Tue, 11 Mar 2025 17:05:36 GMT

just for info, because it took me a long time to find, make sure your primary and secondary partitions are aligned on your flash erase sector size boundary (0x1000 for me) for BOTH their start AND their size... (otherwise the mcuboot trailers are not updated during swap, and the confirmation doesn't work)

RE: MCUboot test and confirm with DFU Target library

simonhwm — Mon, 27 Jan 2025 12:51:51 GMT

In case it helps anyone else with the same question, I searched the ncs 2.8.0 folder structure and found the following:

dfu_target_schedule_update(img_num), when used with MCUboot, internally calls boot_request_upgrade_multi(img_num, BOOT_UPGRADE_TEST)

So scheduling an update and rebooting will boot the new application code as test. It needs to be confirmed in my application code after reboot and once I've established BLE connection again to to prove that the new code is working.

In the LWM2M code I found this, which seems to be what I need for that task:

__weak bool lwm2m_os_dfu_application_update_validate(void)
{
#if defined(CONFIG_MCUBOOT_IMG_MANAGER)
int err;
bool img_confirmed;

img_confirmed = boot_is_img_confirmed();
if (!img_confirmed) {
err = boot_write_img_confirmed();
if (err == 0) {
LOG_INF("Marked running image as confirmed");
return true;
}

LOG_WRN("Failed to mark running image as confirmed");
}
#endif /* CONFIG_MCUBOOT_IMG_MANAGER */

return false;
}

Simon

RE: MCUboot test and confirm with DFU Target library

AHaug — Fri, 24 Jan 2025 09:57:36 GMT

I see now I was a bit too quick in my reply yesterday as I mixed up two libraries, sorry for that. It is as you say, an overlap.

MCUmgr and DFU target Lib are two separate methods to perform DFU. The _confirmed() function I referred to belongs to MCUmgr, while the dfu_target_schedule_update() belongs to DFU target lib and does the same thing as _confirmed(). AFAIK dfu_target_schedule_update()'s main job is to mark the images as test or confirm.

As for showing how to perform a test reboot and confirm, I recommend you to have a look at these two samples:

The Cellular HTTP full modem update sample . https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/cellular/http_update/modem_full_update/README.html#dependencies
The LwM2M client sample https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/cellular/lwm2m_client/sample_description.html

Let me know if these samples are enough to show you how to use the DFU target library for test and/or confirm

Kind regards,
Andreas

RE: MCUboot test and confirm with DFU Target library

simonhwm — Thu, 23 Jan 2025 16:32:57 GMT

Thanks. In that case what does dfu_target_schedule_update() do? It seems like an overlap.

RE: MCUboot test and confirm with DFU Target library

AHaug — Thu, 23 Jan 2025 15:02:54 GMT

Hi,

If you're referring to "confirm" as in "marking an image as confirm for DFU", then you can use boot_write_img_confirmed() as described here https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/applications/nrf_desktop/doc/dfu_mcumgr.html. There is also the equivalent to mark it as test.

However if you believe I've misunderstood your question, please feel free to fill in the gaps that you believe I've missed,

Kind regards,
Andreas