Repository navigation
bench: count the frames the trim test really sends - #309
Merged
Merged
Conversation
aq1018
force-pushed
the
bench-trim-reanchor-stable
branch
from
October 7, 2026 06:18
7184a7e to
721ea38
Compare
aq1018
force-pushed
the
bench-trim-reanchor-stable
branch
from
October 7, 2026 06:21
721ea38 to
04b97f8
Compare
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.
HOSTCOUNT computed the trim test frames from a formula whose +2 had no identified send, and at 3 Mbps it missed the baud-switch write. The bench wire now counts the frames it actually sends. The test prints the baud switch as setup_frames, the run as frames, and total_frames since connect, which is what a probe dump taken around the whole binary sees (the shared bench setup reads are the old +2). At the 1M default, switch_baud sends nothing. Stacked on the re-anchor PR.
Bench gate: setup_frames 0 at 1M and 1 at 3M (PASS, 10/10 runs each); total_frames == the TrimProbe frames delta after one detune run on the probe image at 1M and at 3M (the first gate showed frames + 2 == probe at both bauds, the two setup reads).
https://claude.ai/code/session_016NV5eybqhfjQPnesWHUCRs