Over-the-air updates and release engineering
How a fix gets from your repository to every device in the field, safely, and what it costs each time you do it.
An update path is the one feature a device cannot gain after it leaves the factory. This section of Field Update covers how to build one and how to use it well: the bootloader and flash layout, image signing and who holds the keys, the test-then-confirm step that lets a device fall back to a working version, and the rollout plan that decides which devices get a release first.
Much of it is practical arithmetic. How long does an image take to cross a Bluetooth LE link? What does one rollout cost on a cellular plan, with full images or with deltas? How many devices are at risk in the first wave, and how many days does a staged rollout take? The articles show the working, and the free tools let you run your own numbers:
- Over-the-air data cost calculator for the cost of each rollout.
- Staged rollout planner for wave sizes and soak times.
- Bluetooth LE update time calculator for transfer times.
- Release notes builder, update policy worksheet and firmware release checklist for the release habits around them.
Release engineering matters for longer than it used to. For products sold in the EU, the Cyber Resilience Act expects security updates to be provided free of charge over a support period of at least five years, unless the product is expected to be in use for less. That makes the update pipeline something you will run for years, not something you set up once.
If you want the path built and tested with you, see over-the-air updates. If you want someone to keep shipping releases and reporting on them, see sustaining releases. The articles in this section are listed below with their issue dates.
| Issue | Article and the question it answers |
|---|---|
| What it takes to ship firmware you can safely updateWhat has to be in place, from bootloader and signing keys to factory programming and rollout, before a startup can safely update devices in the field? | |
| Rollback vs anti-rollback: recovering without downgrade riskHow do we let devices recover from a bad update while still blocking attackers from installing older, vulnerable firmware? | |
| Staged firmware rollouts: what to watch and when to stopWhen we release firmware to a fleet in waves, which health signals should decide whether the next wave goes out or the rollout stops? | |
| Delta firmware updates: when smaller images pay offWhen are delta (differential) firmware updates worth their added complexity on a microcontroller fleet, and what do they demand from the bootloader and release process? | |
| A/B or single-slot updates: choosing an MCUboot layoutShould our microcontroller firmware use swap, overwrite or A/B (direct-XIP) updates, and what does each cost in flash, downtime and recovery after a failed or interrupted update? |
Send us your board and your plan.
A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.
Or email sales@fumbar.com, or call (720) 675-4202.