Model the volatile reprogram ladder as a hardware plan - #131
Merged
Conversation
SramProgramPlan encodes the bench-proven SRAM safe order as ordered ToolSteps: device-scoped PM hold (tolerant), deadman arm, sysfs remove, volatile program, secondary-bus reset on the endpoint's upstream bridge (a new explicit host_access fact, reset_bridge_bdf), global rescan + settle, endpoint verify, an optional injected device verify, deadman disarm. The disarm step is deliberately not named *release: the plan executor stops on the first failure and runs only *release cleanup after, so a wedge leaves the deadman armed and the box self-recovers to the SPI-resident design — pinned by test. Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
This was referenced Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Increment 1 of dau-docs-private/ROADMAP_DAU_BUILD_FIXES.md:
SramProgramPlanencodes the bench-proven volatile (SRAM) reprogram safe order as orderedToolSteps — device-scoped PM hold (tolerant), deadman arm, sysfs remove, volatile program, secondary-bus reset on the endpoint's upstream bridge (new explicitHostAccess.reset_bridge_bdffact, threaded throughfor_platform/the task/yaml), global rescan + settle, endpoint verify, optional injected device verify, deadman disarm.The disarm step is deliberately not named
*release: the executor stops on the first failure and runs only*releasecleanup after, so a wedge leaves the deadman armed and the box self-recovers to the SPI-resident design — pinned by test. Codex round 1 caught swallowedsetpci/rescan failures behind trailing sleeps (now&&-chained so they fail the step) and the unquoted bridge BDF (nowshlex.quoted).