Software Updates for Connected Devices: Key Considerations
summary
Survey of ~30 teams finds most build homegrown updaters, taking 3–6 months to create and then maintained for years; average deployment cadence is about six updates per device per year. Key concrete choices: use full-image or atomic A/B updates for reliability (double storage, single reboot), or package/runtime installs for lower bandwidth but higher risk. Essential pieces are signed artifacts, pre/post-install sanity checks, rollback capability, delta transfers to cut bytes, and a managed server (example: Mender.io integrates with Yocto and is open source).
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:42Software Updates for Connected Devices
- 2:14Connected devices must be remotely updatable
- 3:53Reuse open source tools for remote updater
- 6:08Session overview
- 6:59Do you deploy updates today? How?
- 8:13Image-based or package-based deployment?
- 9:52Development time and frequency of use
- 11:41The embedded environment
- 14:11Network requirements are different than for smartphone
- 17:50Key criteria for embedded updates
- 20:38Robust and secure
- 22:57Integrates with existing environments
- 25:20Easy to get started
- 26:165. Bandwidth & downtime during update
- 27:27Generic embedded updater workflow
- 33:06run-time installation
- 34:29boot to maintenance mode
- 37:18proxy
- 38:24Comparison of installer strategies
- 38:48Remote deployment management
- 40:26Ensure your devices can be updated remotely
- 41:36Installer strategy 3: dual A/Brootfs layout
related talks
22mUpdate Strategies for the Edge
31mUpdating the Edge
30mDevOps Patterns and Antipatterns for Continuous Software Updates
44mUpdating an Embedded System with SWUpdate Framework
47mOrchestrated Android-Style System Upgrades for Embedded Linux
31mUpdating the Edge
34mComparing Linux OS Image Update Models
30mSoftware Patching Needn't Be a Can of Worms