fw-v0.5

Tag firmware for the distributed targets. Each image ships with its build manifest, which records the commit, the ChibiOS commit and branch, the toolchain and nanopb versions, and the SHA-256 of the image itself. CI does not bench-test power behaviour; that is a separate step before flight, and the table below says which targets have had it.

Power qualification

Measured on hardware, from this release's images, per the release procedure. Supply voltage is stated because it is not the same for every tag: BitTag is unregulated and runs directly from its cell, so its currents have no meaning at any other voltage.

Target	Qualified	Supply	Idle	Running	Finished
BitTag	2026-10-03	2.496 V	0.122 µA	0.508 µA	0.121 µA
CompassTagAT25	2026-10-04	2.496 V	0.23 µA	1.95 µA	0.22 µA
IMUTagNandBmp581	not qualified
PresTag	not qualified
UIUCTag	not qualified

BitTag — PASS. Board BitTag V6, UUID 2035374D303150190059002F, config bittag-bitpersec.json (one activity bit per second). Four resting states agree within 1.1%, 40× below the 5 µA gate; running reproduced to 0.04% across two 1200 s windows with the state confirmed RUNNING. A 1440-row activity table downloaded with monotonic timestamps. tag-test ALL_PASSED. Per mAh of cell: 342 days resting, 82 days recording. Evidence attached as qualification-BitTag-20261003.tar.gz.

CompassTagAT25 — PASS. Board CompassTagv1, UUID 203633324B4250060022005E, shipped default config, 30 s compass sample period. Four resting states agree within 10 nA, including one taken after a different attach pattern; idle and finished match to 0.01 µA, as they must, sharing one terminal-sleep path. Running measured over three 900 s windows across two harnesses — 1.96, 1.95 and 1.9482 µA, a 0.60% spread. Each run downloaded 30 activity rows with every sample interval exactly 30 s. tag-test ALL_PASSED. Per mAh of cell: 187 days resting, 21.3 days recording. Evidence attached as qualification-CompassTagAT25-20261004.tar.gz.

Two caveats worth carrying. FINISHED had never been measured on a CompassTag before this session. And the figures agree with the 2026-09-24 production unit (…004A005D: idle 0.2346/0.2317 µA, running 1.9538 µA) on a different board and from a release image rather than a local build — the first board-to-board agreement CompassTag has had. Read that older running figure as carrying 17% of its own alignment error, though: it came from a 180 s window, six ticks of a 30 s period.

IMUTagNandBmp581 is marked not qualified deliberately. It has a full set of measurements at this commit, but from a locally built image rather than from this release, so it does not meet the procedure's requirement that the image measured is the image that ships. It will be re-run against the release.

A target that is not flying this round does not need qualifying. A target that is needs it again after any change to its image — which, the build being reproducible, means after any change to the commit it is built from.