Re: [meta-arago][scarthgap][PATCH RFC 0/4] Add support for SWUpdate

Hello Anshul, All,

Le 02/12/2025 à 12:15, Anshul Dalal a écrit :
> Hi all,
> 
> This RFC adds support for SWUpdate[1] to meta-arago, this provides us with OTA
> updates with A/B redundancy for the rootfs.

Do you have some recommendation when an upgrade should include a TI firmwares
updates (TI SCI, DM)? On the rootfs we can have some remoteproc firmwares built
with a specific TI SDK version that imply a specific TI SCI/DM firmware version
being used.

What if we want to update the system with OTA? It seems we have to update u-boot
too.

Example:
The system is running with a Yocto kirkstone based image and we want to deploy a
new Scarthgap based image. The kirkstone image will provide a DSP firmware build
with the TI SDK 09.02.00.05 while the Scarthgap image will provide a DSP
firmware build with the TI SDK 11.02.00.06.

On meta-ti kirkstone I had a regression with a DSP firmware at runtime due to a
ti-linux-fw version bump: https://lists.yoctoproject.org/g/meta-ti/message/19322
(It was probably due to an IPC/mailbox change between TI SDK 9 and 10).

The K3 bootflow that is already complex doesn't seems to expect using A/B
redundancy for the bootloader. One of the "safer" solution would to flash the
eMMC with a new image after booting with an SD card.

Best regards,
Romain

> 
> For now the support is enabled for eMMC boot only based on the 'ti-swupdate'
> override. The below steps can be used to test this RFC on an AM62x EVM:
> 
>  1. Add 'meta-swupdate' layer[2] to the SDK sources directory.
> 
>  2. Since the bootloader side changes have not been merged to ti-u-boot yet,
>     make use of the 'swupdate' branch from my own U-Boot fork[3].
> 
>  3. Enable 'swupdate' support by setting the 'ti-swupdate' override in
>     local.conf as follows:
> 
>       DISTROOVERRIDES:append = ":ti-swupdate"
> 
>  4. Flash the U-Boot binaries to the correct offsets on boot0 partition as
>     per the docs[4] and run 'env save' on first boot to save the environment to
>     eMMC's hw partition.
> 
> Regards,
> Anshul
> 
> [1]: https://swupdate.org/
> [2]: https://github.com/sbabic/meta-swupdate
> [3]: https://github.com/ArchUsr64/u-boot/tree/swupdate
> [4]: https://software-dl.ti.com/processor-sdk-linux-rt/esd/AM62X/latest/exports/docs/linux/How_to_Guides/Target/How_to_emmc_boot.html#how-to-emmc-boot
> 
> Anshul Dalal (4):
>   swupdate: add systemd service to rootfs
>   swupdate: add creation of update image
>   swupdate: add bootloader support
>   swupdate: enable authentication for update image
> 
>  meta-arago-distro/conf/distro/arago.conf      |  3 ++
>  .../images/files/sw-description               | 46 +++++++++++++++++++
>  .../recipes-swupdate/images/update-image.bb   | 27 +++++++++++
>  .../libubootenv/files/fw_env.config           |  5 ++
>  .../libubootenv/libubootenv_%.bbappend        | 10 ++++
>  .../recipes-swupdate/swupdate/files/defconfig | 12 +++++
>  .../swupdate/files/swupdate.cfg               | 13 ++++++
>  .../swupdate/files/swupdate.sh                | 15 ++++++
>  .../swupdate/swupdate_%.bbappend              | 35 ++++++++++++++
>  .../wic/sdimage-2part-swupdate.wks            |  6 +++
>  10 files changed, 172 insertions(+)
>  create mode 100644 meta-arago-distro/recipes-swupdate/images/files/sw-description
>  create mode 100644 meta-arago-distro/recipes-swupdate/images/update-image.bb
>  create mode 100644 meta-arago-distro/recipes-swupdate/libubootenv/files/fw_env.config
>  create mode 100644 meta-arago-distro/recipes-swupdate/libubootenv/libubootenv_%.bbappend
>  create mode 100644 meta-arago-distro/recipes-swupdate/swupdate/files/defconfig
>  create mode 100644 meta-arago-distro/recipes-swupdate/swupdate/files/swupdate.cfg
>  create mode 100644 meta-arago-distro/recipes-swupdate/swupdate/files/swupdate.sh
>  create mode 100644 meta-arago-distro/recipes-swupdate/swupdate/swupdate_%.bbappend
>  create mode 100644 meta-arago-distro/wic/sdimage-2part-swupdate.wks