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

["Raghavendra, Vignesh" <vigneshr@ti.com>]

Hi Denys,

On 12/3/2025 2:29 AM, Denys Dmytriyenko wrote:
> On Tue, Dec 02, 2025 at 04:45:57PM +0530, Anshul Dalal via lists.yoctoproject.org wrote:
>> 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.
>>
>> 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.
> Why not use a more established A/B solution, such as RAUC (or even Mender)?
> 

SWUpdate is still the most widely requested option from users of TI K3
SoC. Its a more versatile than RAUC as it provides flexibility wrt image
level vs file vs block level updates.

AFAIK, Both RAUC and SWUpdate are equally powerfully and well
established. Could you help me understand why RAUC is more established
than SWUpdate?

AGL seems to be on OSTree. OpenWRT, CIP is SWUPdate. Buildroot supports
both (default is SWUpdate), so there isnt a common theme. Though
SWUpdate seems more common in industrial focused distro space as far as
my knowledge goes.

Mender is a different story though, its open source but has commercial
element to it. And at least K3 based beagle devices are already
supported via mender.io [1].

[1] https://hub.mender.io/t/board-support-index/5742

Regards
Vignesh