ledger: confirm TB LEDs and record LPPS reflash - #95
Merged
Conversation
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.
Record the owner-confirmed TB LED coexistence, USB indication and layer-number blink. Keep LPPS/IQS LED and CDC gates pending. Update evidence to the successful main build and regenerated standard firmware folder. Record the user-authorized latest LPPS flash with Git blob/SHA256 identity checks, CDC reopen and matching Studio core response, without claiming LPPS input/LED acceptance or LPPS-origin CDC recovery. Local ledger validation, 36 Python tests and 45 Node tests pass.