Prove the Trial Slot before Expanding the Cohort

Prove the Trial Slot before Expanding the Cohort

Prove the Trial Slot before Expanding the Cohort

Assume an illustrative dual-slot layout with two 512 KiB image slots. Together they reserve 1,024 KiB, or 1 MiB, before bootloader, metadata and working space. A 480 KiB candidate leaves 32 KiB within its slot for any slot-resident overhead. The update must check the actual signed image layout rather than comparing only the uncompressed application binary with nominal flash capacity.

Follow Figure 1 in the chapter from signed artifact and manifest to readiness, local verification, inactive-slot installation and boot confirmation. Each transition creates a different update state. Download complete means the bytes arrived; verification checks their integrity and authorization; confirmation establishes that the new running image met the defined health conditions.

Cut power before the boot selection changes, then in a separate test cut it during the first trial boot. The architecture should recover according to its documented state machine without selecting partially written code. Keep the retained image and boot metadata consistent under these fault points. The boot architecture needs power-loss evidence to establish its flash-write and metadata guarantees.

For a staged update example, choose 10 devices from a fleet of 10,000. The exposed fraction is 10 divided by 10,000 = 0.001, or 0.1%. If two fail the healthy-boot check, that is 20% of the trial cohort. Do not dilute the failed update result by dividing those failures by the untouched fleet. The update stays within the first cohort until the stated gate permits expansion.

Predict whether returning to the old code is sufficient after the candidate changed stored data into an incompatible format. The update architecture needs a compatible state plan or a tested roll-forward recovery. Next, let a device stop checking in. The update policy treats silence as unknown or failed health, not confirmation by default.

This module treats remote updates as controlled state changes because the device may be beyond physical reach. The exact slot sizes and cohort figures are illustrative, while the retained-image, health and recovery evidence must come from the hardware and bootloader that will perform the change.

Back to the chapter