Fifty-two libavr commits and twenty-seven of pureboot behind, which is far enough that "it still builds" is not the interesting part. It builds, both modes, byte-identical across them, five checks green - and the image is **byte-for-byte the 8004 B the board is running**, so the catch-up costs this deployment nothing and a redeploy was ruled out by comparison rather than skipped by assumption. The loader is the gap that mattered. pureboot rode as a submodule for its geometry alone, so the commit that pinned this firmware did not build the one image this board cannot be recovered without - the same hole tempmon had. `pureboot_add_loader(pureboot)` closes it on nothing but pureboot's own defaults for the chip, and the 386 B it produces is byte-for-byte what the board's slot reads back. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.5 KiB
2.5 KiB