docs: eMMC boot/recovery architecture + install/update system plan

BRINGUP: the measured eMMC map (factory MBR, U-Boot in boot0 at 1KiB,
saved env at user-area 0x80000/0x82000, default-env recovery boot, the
boot0/boot1 recovery images, factory .fw/fwup internals) and the traced
SD kernel-load path.

UPDATE-SYSTEM: phased plan for the factory A/B slot scheme end-to-end -
fwup-packaged signed releases, single-stage installer, GUI update
manager, offline factory restore, legacy-p4 migration, recovery
refresh; invariants and decision gates.
This commit is contained in:
ScottW514
2026-08-08 11:34:08 -04:00
parent 75e0eb24da
commit 888e51d84e
2 changed files with 247 additions and 0 deletions
+7
View File
@@ -833,3 +833,10 @@ max. Images from 20260807204056 carry forgectrl at the bumped SRCREV
meta-forgefirm, boot autostart, reboot-verified). Remaining: Phase 7
doc sweep (CLAUDE.md charter refresh, README roadmap), kas flip +
first GitHub release per kas/README.md once ready to publish.
7. **Install/update system overhaul** (planned 2026-08-08): adopt the
factory A/B slot scheme end-to-end — fwup-packaged signed `.fw`
releases, single-stage installer, GUI update manager + boot
selector in forgectrl, offline factory restore from a `/data`
archive, legacy-p4 migration, and later a refreshed recovery image
in boot0. Full phased plan with invariants and decision gates:
`docs/UPDATE-SYSTEM.md` (builds on the facts-bank eMMC map).