Enable support for wfx backend based software updates
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hi All,
Please ignore this v2 series. Just found an issue with patch 2 (recipes-core/swupdate-config: Add suricatta section in swupdate.cfg). Will share v3 in sometime.
Regards,
Adithya Balakumar
________________________________
From: [email protected] <[email protected]> on behalf of Adithya Balakumar <[email protected]>
Sent: Tuesday, October 28, 2025 11:04 AM
To: [email protected] <[email protected]>; [email protected] <[email protected]>
Cc: balakumar adithya(TSIP DITC_DIT-OST) <[email protected]>; kunijadar shivanand(TSIP DITC_DIT-OST) <[email protected]>; dinesh kumar(TSIP DITC_DIT-OST) <[email protected]>; hayashi kazuhiro(林 和宏 □DITC○CPT) <[email protected]>; sahithi akunuri(TSIP TEUR) <[email protected]>
Subject: [cip-dev] [isar-cip-core][RFC v2 0/5] Enable support for wfx backend based software updates
From: Adithya Balakumar <[email protected]>
SWUpdate has supported software updates with wfx[1] backend for a while now. But using this requires a few configurations in the image (swupdate.cfg). These series of patches enables/sets the necessary configurations required to use wfx for software updates.
For now, I'm sending this as an RFC to understand the opinions of a broader audience.
A couple notes about the implementation:
- Provides using wfx as the update backend as an option (not forced).
- Adds a new section for suricatta in the swupdate.cfg file.
- Starts SWUpdate in suricatta daemon mode at service startup (if wfx support is enabled at build).
- wfx requires a clientId per device in order to target devices (create jobs for devices). This is currently achieved with wfx-customizations package which deploys a script in the image that sets the ID in the swupdate.cfg at run time.
- The above point could be made more practical with something like an onboarding function (See [2], This is still not officially part of the CIP project yet).
- Introduces wfx.yml to set wfx specific variables.
[1] https://sbabic.github.io/swupdate/suricatta.html#support-for-wfx
[2] https://gitlab.com/cip-playground/cip-wfx-onboarding-client-plugin
Changes since v1:
- Rebase to current next
- Drop carrying the patch to fix swupdate issue as its backported to debian
- Fix appending suricatta section in swupdate.cfg only if wfx is requested at build time
- Use /etc/machine-id as is for client-id in suricatta
Adithya Balakumar (5):
SWUpdate: Use self-built SWUpdate 2025.05+dfsg-3 for trixie recipes-core/swupdate-config: Add suricatta section in swupdate.cfg
wfx-customizations: Recipe to add wfx helper specific scripts into
target
kas/opt/wfx.yml: Set wfx specific variables doc/README.swupdate.md: Add section for software update with wfx
conf/distro/cip-core-trixie.conf | 1 +
doc/README.swupdate.md | 124 ++++++++++++++++++
kas/opt/wfx.yml | 20 +++
recipes-core/images/swupdate.inc | 3 +-
recipes-core/swupdate-config/files/suricatta | 1 +
.../files/{swupdate.cfg => swupdate.cfg.tmpl} | 2 +
.../swupdate-config/swupdate-config_0.2.bb | 27 +++-
.../swupdate/swupdate_2025.05+dfsg-3.bb | 36 +++++
.../wfx-customizations/files/override.conf | 6 +
.../files/wfx-generate-client-id.sh | 9 ++
.../wfx-customizations_0.1.bb | 28 ++++
11 files changed, 254 insertions(+), 3 deletions(-)
create mode 100644 kas/opt/wfx.yml
create mode 100644 recipes-core/swupdate-config/files/suricatta
rename recipes-core/swupdate-config/files/{swupdate.cfg => swupdate.cfg.tmpl} (83%)
create mode 100644 recipes-core/swupdate/swupdate_2025.05+dfsg-3.bb
create mode 100644 recipes-core/wfx-customizations/files/override.conf
create mode 100644 recipes-core/wfx-customizations/files/wfx-generate-client-id.sh
create mode 100644 recipes-core/wfx-customizations/wfx-customizations_0.1.bb--
2.39.5