Hi Suresh,

The firmware update service APIs are for updating the firmware. The functionalities of these APIs includes loading the image into its target device(flash), verifying the image and installing it and so on.

The user can call the these APIs to achieve update images. For example, in the integration of TF-M and the FreeRTOS OTA, the OTA agent calls the firmware update service APIs to achieve an image update remotely.

I guess that the “MCUboot update services” you mentioned refers to the functionality of MCUboot which acts as a bootloader. As a bootloader, it can verify the image which already exists on the device and chose the right image to start up. But it cannot, for example, load the image into device or control the image update process.

The firmware update partition calls some user APIs provided by MCUboot to cooperate with it. You can refer to https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/docs/technical_references/tfm_fwu_service.rst#n75.

Regards,

Sherry Zhang

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Suresh Marisetty via TF-M
Sent: Thursday, May 13, 2021 11:09 AM
To: tf-m@lists.trustedfirmware.org
Subject: [TF-M] Firmware update API - MCUboot update

Hi,

I would like to see if there is any guidance/documentation on how to coordinate between the firmware update services API with that of MCUboot.

Does the use of this API make the MCUboot update services redundant?

thanks

Suresh Marisetty

Infineon Semiconductor Corporation

Lead Member of Technical Staff

CYSC CSS ICW SW SSE

Mobile: +5103863997
Suresh.Marisetty@infineon.com