Orchestrated Android-Style System Upgrades for Embedded Linux
summary
An Android-style, two‑phase updater is implemented for embedded Linux using SWUpdate, Eclipse hawkBit and Yocto changes; a tiny recovery RAM disk plus a bootloader “update” flag lets the regular OS download a .sw file to a recovery partition and reboot to a writable recovery that flashes partitions atomically. Demo shows orchestrated rollout (staged groups for Germany/Italy), cloud feedback on success, and custom artifact storage; signature verification is planned and the system works end‑to‑end on a Nitrogen6 reference board.
AI-written summary · about
chapters (24)
- 0:00Start
- 2:47Preamble
- 4:29Android update: approach to OTA updates
- 5:08Android update Workflow
- 6:58Android update: execution
- 8:44Android Update: advantages
- 9:50Part One: Device Update Approaches
- 13:20Double Copy: Pros and cons
- 15:09Single Copy: Pros and cons
- 16:38Embedded Linux 11ke Android ?
- 18:28SWUpdate: Architecture
- 21:40Security notes: encryption
- 21:53Case Study: Warp board
- 24:54hawkBit Architecture
- 26:49Update Factory Architecture
- 27:32Android "like" behaviour on Embedded Linux
- 28:11Update Factory: Linux Update Anatomy
- 29:41Update Factory: device to cloud
- 30:31Update Factory: bootloader coordination
- 31:48Update Factory: recovery partition
- 32:46Update Factory: bootscript & randisk
- 33:11Update Factory: Installation feedback
- 33:29Update Factory: future developments
- 42:52Android update: preparation
related talks
51mUsing SWUpdate to Upgrade Your System
56mComparison of Linux Software Update Technologies
45mOSS Remote Firmware Updates for IoT-like Projects
45mSoftware Updates for Connected Devices: Key Considerations
45mSoftware Update for IoT: The Current State of Play
43mUpdate My Board!
39mImplementing Power-Safe Atomic Over the Air Updates
01h 00mOpen Software Updates for IoT