Document MMS NAND logging semantics: LENGTH's three moods, async GC, consuming readouts#12
Open
lkasso wants to merge 1 commit into
Open
Document MMS NAND logging semantics: LENGTH's three moods, async GC, consuming readouts#12lkasso wants to merge 1 commit into
lkasso wants to merge 1 commit into
Conversation
…consuming readouts Field-verified on MMS firmware 1.7.x during multi-device host development: byte-identical command sequences succeed or fail purely on timing and prior flash state, because the NAND write page and background garbage collector are invisible to the wire protocol. Human-paced hosts never noticed — navigation delays provided the settling time by accident; machine-paced hosts hit every mechanic. Documents the three LENGTH states, the asynchronous Drop Entries + unreliable 0x0D completion, the records-nothing-during-GC trap, entry consumption by readout confirms, and the verified host pattern (poll LENGTH rising while enabled) that sidesteps all of it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Writes down what eight hardware debugging sessions proved about MMS (logging revision 3) NAND behavior — knowledge that previously existed nowhere in the spec and bit even the canonical apps (which were merely human-paced enough to hide it):
LENGTH's three moods: flash+RAM while logging is enabled · flash-only after stop (the final-page commit takes seconds, silently) · sentinel/stale for up to ~60 s after a clear — including the trap that a stable zero can mean "empty but dirty."0x0Dcompletion notification is not reliably delivered on 1.7.x.LENGTHrising while logging is enabled after arming (healthy boards confirm in one or two 2 s polls; ~90 s bound for GC-bound boards), and flush + settle before download reads.Placed at the end of the Logging module section, before the Timer module. Merging auto-deploys to docs.mbientlab.com.
🤖 Generated with Claude Code