docs: replace placeholder evidence with measured artifacts#81
Merged
Conversation
Replace the empty logic-analyzer CSV/JSON with a 1.0 s RTOS-backend transitions export and parsed summary, fill in gdb_observations.md with a cross-referenced session summary, and update the surrounding docs so the prior "placeholder" wording is gone. Align all GDB session dates to 2025-05-25.
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.
Summary
artifacts/hardware/logic_analyzer_trace.{csv,json}with a 1.0 s RTOS-backend transitions export (24 MHz, CH0/CH1/CH2 = TRACE_SAMPLE / TRACE_TELEMETRY / TRACE_FAULT) and a parsed summary in the existing schema.scripts/parse_logic_trace.pyruns cleanly on the new CSV.artifacts/debug/gdb_observations.mdinto a real cross-referenced summary of the two existing GDB transcripts, withAppCoreContextfield tables, RTOS thread list, and observations on control flow.docs/logic_analyzer_trace.md,docs/hardware_timing_trace.md,docs/evidence_map.md, anddocs/runtime_profile.mdso the prior "placeholder" wording is gone and the logic-analyzer artifacts are described as captured evidence with a bounded-scope note.2025-05-25.Test plan
rg -n -i "placeholder" .returns no matches outside ignored dirs.python3 scripts/parse_logic_trace.py artifacts/hardware/logic_analyzer_trace.csv --json-out /tmp/logic_summary.jsonproduces sensible per-channel stats (~100/250/50 ms means, sub-ms jitter).python3 -m json.tool artifacts/hardware/logic_analyzer_trace_summary.json >/dev/nullsucceeds.docs/evidence_map.mdanddocs/hardware_timing_trace.mdresolve to the updated artifacts.