Skip to content

F0054 flt-8

Rule: A boot-loop rescue falls back to the ROM bootloader after repeated unhealthy boots.

Code F0054 (stable, never reused)
Id flt-8
Category flt
Source spirit_level
Fix by hand

Level per tier

Tier Level Reason
small off
small-workspace off
medium off
big off
ai off
embedded warn bedrock warning: No boot-loop rescue: count boots without a healthy mark in a backup register, fall back to the ROM bootloader after a few
ui off
egui off
units-strict off
units-paranoid off

Why

No counter, in a backup register, of boots since the last time the firmware marked itself healthy — and so no fallback into the ROM bootloader after a few unhealthy boots in a row.

A firmware that crashes before it can mark itself healthy (a bad update, a new regression) boot-loops forever with no rescue path other than a debug probe; a counted fallback into the ROM bootloader after a few failed boots turns "the board is bricked" into "the board is recoverable over USB".

Example

Typec_dongle FW-45, and embedded_bedrock DEV-16 which specifies the device-wide boot-loop rescue contract every board should meet.

How to fix

Count boots in a backup register, clear it once the firmware marks itself healthy, and jump to the ROM bootloader (or hold there) once the count passes a small threshold (DEV-16's contract).

How it is checked

src easy: a backup-register boot counter incremented at boot and cleared on a healthy mark, with a check that falls into the ROM bootloader past a threshold.

Source

Ported from embedded_bedrock's firmware check catalogue, FLT-8 (book/checks.md, detail in book/checks/flt.md). Found on: typec_dongle FW-45; embedded_bedrock DEV-16.

Configure

[lints.flt-8]
level = "deny"
reason = "why this project wants it at this level"

Allow one finding in the code with // spirit-level: allow(flt-8) <reason> (waivers); the code works there too, as in [lints.F0054].