← Back to the chapter · Next detail →
Technical detail · Fleet Device Management
Firmware Supports Managed State
32.4 Firmware Supports Managed State
A management platform cannot rescue firmware that lacks a safe update and recovery path. A/B slots keep two firmware images so a bootloader can return to a known-good image if the new one fails. A delta update carries only changes from a known base image. Update metadata describes the package, its target, and how to verify it. MCUboot is a bootloader; RAUC and SWUpdate manage update installation, while Uptane and TUF define security metadata and verification practices. Check which pieces the target actually supports.
- Identity boundary: separate manufacturing id, user-visible asset id, certificate subject, MQTT topic namespace, device-shadow record, and support ticket reference.
- Update boundary: define A/B slot layout, bootloader rollback flag, MCUboot, RAUC, SWUpdate, Uptane or TUF metadata, delta-update rules, battery threshold, and network resume behavior.
- Access boundary: decide who can enroll, group, configure, command, suspend, delete credentials, export logs, approve rollout, and release a quarantined device.
- Lifecycle boundary: preserve replacement mapping, credential revocation, data-retention action, final configuration state, and proof that the retired unit can no longer reconnect.