How to Leverage an Open Update Protocol to Drive Your Embedded Devices from Any Cloud OTA Provider
summary
A lightweight update stack uses containers and a minimal container orchestrator (under 2 MB) to represent device state as a state.json that points to squashfs container artifacts, enabling reproducible rollouts and rollbacks. A tiny HTTP server over a Unix socket exposes four actions (install JSON, transfer artifacts, run command, metadata) so any REST-based cloud (Azure device update, Pantacor Hub client) or local host tool can drive OTA. Implements integrity checks via hashes/signatures, configurable garbage collection, works on 16 MB-class routers and scales to fleet UIs.
AI-written summary · about
chapters (6)
- 0:00Start
- 8:37Control Socket
- 9:16Update Flow
- 9:54Control Protocol
- 15:12Making Device States Reproducible
- 22:43A couple of Containerized Cloud Client examples
related talks
42mEvolution of (OTA) Update in the IoT World
43mOTA Updates in the Wild: Lessons from the Field
50mThe ultimate guide to software updates on embedded Linux devices
45mOSS Remote Firmware Updates for IoT-like Projects
39mImplementing Power-Safe Atomic Over the Air Updates
39mAktualizr-lite: Be Secure and Never use /bin/dd Again
55mBoF: Embedded Update Tools
39mHow to Choose a Software Update Mechanism for Embedded Linux Devices