Skip to content

target/ast10x0: List the gaps around the self-update record - #42

Draft
chrysh wants to merge 1 commit into
self-update-recordfrom
self-update-gaps
Draft

chrysh wants to merge 1 commit into
self-update-recordfrom
self-update-gaps

Conversation

@chrysh

@chrysh chrysh commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

The self-update record in #41 depends on a boot stage that the tree does not hold. GAPS.md does not list what the boot stage starts after a lost record or a flash fault on the newest record copy.

This PR adds a GAPS.md section on the self-update record, on top of #41.

A question for reviewers. Take an update that raised the SVN. A flash fault hits the record copy that holds the Committed session, between the SVN floor advance and complete(). The boot stage then reads the older copy, which holds the TrialPending session. The SVN floor check rejects the confirmed image, select reads the trial as tried and excludes the trial slot from the walk, and on a layout of 2 slots the boot stage starts the golden image in recovery mode. Is recovery mode the accepted outcome for this fault?

GAPS.md now has a section on the boot stage contract that the
self-update record depends on, and on the boot stage walking the slots
after the confirm, which makes RecordSession::open() drop the session
without a revert. The trial watchdog, the lock on the tried-mark region
and the handover mechanism belong to the boot stage, which the tree does
not hold, so the tree has no code for them.

The bullet on joining the QEMU self-update scenarios into one run now
also lists a board that wires RecordSession on flash and a boot stage
that reads the record.

Signed-off-by: Christina Quast <christina.quast@9elements.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

1 participant