Update My Board!
summary
Compares four concrete update paths and what actually needs to be changed to get them running on a custom Yocto board: Mender produces a .mender artifact, requires U-Boot with bootcount, two root partitions and meta-mender (automatic U-Boot patching works sometimes, otherwise apply one board patch); libostree/aktualizr requires everything under /usr, hardlinks and an initramfs/ROM disk from meta-updater; SWUpdate uses .sw-description scripts and Lua hooks to partition or swap; resin.io uses container delta for apps and A/B for OS with meta-resin. A/B installs are the most robust.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:21Session Overview
- 1:22Background
- 5:07Mender (Requirements)
- 7:25Mender (Yocto/OE-core)
- 11:28Mender (U-boot)
- 13:33libostree (Requirements)
- 17:01libostree (meta-updater)
- 26:28resin.io (u-boot)
- 28:33Honorary Mentions
- 29:50Summary
- 30:50Questions?
related talks
43mPractical Experience with Linux A/B Upgrades
44mUpdating an Embedded System with SWUpdate Framework
34mComparing Linux OS Image Update Models
56mComparison of Linux Software Update Technologies
51mUsing SWUpdate to Upgrade Your System
45mSoftware Updates for Connected Devices: Key Considerations
47mOrchestrated Android-Style System Upgrades for Embedded Linux
20mUsing Yocto as a Method to Upstream, Maintain, and Track Patches