From 271bb3251267fec68f5c9cec63314b22cfaefe75 Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Fri, 2 Oct 2026 12:41:52 -0400 Subject: debug: risc-v-gsp-rm-debugger final pass - remove in-development notices, complete rename, adversarial-review fixes Remove the '# TOOL IN DEVELOPMENT - NOT READY YET!' notices from the tool docs/README/scripts and the project docs; record the removal (2026-10-02) against the tool audit (debug/risc-v-gsp-rm-vm/docs/27-TOOL-AUDIT.md), the 194-test suite and the value-validation demos (docs/25-VALUE-VALIDATION.md). Complete the cosmetic rename to risc-v-gsp-rm-debugger in user-facing prose and commands (launcher, roadmap, docs); internal greeneye package and code identifiers unchanged. Adversarial-review fixes: deterministic control-discovery sweep (flaky test root-caused), UUID session dirs + atomic JSON writes for concurrent runs, Ghidra bridge loopback enforcement and clean shutdown, fp register restore in Session.call, version_diff --dry-run, 30 s interrupt budget, dry-run non-destructiveness verified. Docs: flag-removal records, link fixes, command/flag corrections (fdematch arity, port_new_device --out, trace filename), F2 orchestration note in future-eng-ops; STATE-CURRENT status refreshed. --- debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md') diff --git a/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md b/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md index 47854d1..e55162d 100644 --- a/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md +++ b/debug/risc-v-gsp-rm-vm/docs/06-ACCURACY.md @@ -1,6 +1,6 @@ # 06 — Accuracy: what the risc-v-gsp-rm-debugger test bed does and does not prove -> **# TOOL IN DEVELOPMENT - NOT READY YET!** See 00 for status. +> Status: implemented, documented and tested (audit: docs/27-TOOL-AUDIT.md; value demos: docs/25-VALUE-VALIDATION.md). > This document is deliberately conservative. Treat every claim without a > recorded A/B as unverified. @@ -43,7 +43,7 @@ windows, a TCM/MPU layout and a PMU-provided environment that `qemu virt` does not have. **Therefore:** loading the raw `.fwimage` into `qemu virt` cannot boot it. -The `greeneye probe` command is designed for exactly this: it loads the +The `./risc-v-gsp-rm-debugger.sh probe` command is designed for exactly this: it loads the segments, runs bounded, and reports the first divergence (`guest_errors,unimp,int` log + stopped PC + symbol). That report is a *memory and control-flow map* of what the firmware tries to touch first — useful data, @@ -92,7 +92,7 @@ Reference capture: `gsp-phys-log-dump`, status-queue drains) and the static-config oracle; * risc-v-gsp-rm-debugger: `events.jsonl` + snapshots, symbol-annotated. -Comparison: `greeneye compare dumps/real- dumps/greeneye- +Comparison: `./risc-v-gsp-rm-debugger.sh compare dumps/real- dumps/greeneye- --symbols`, then a short table of M1–M6 with counts. Never publish a single "accuracy %" number without the metric breakdown. @@ -114,7 +114,7 @@ failure path. The rules: Before trusting a risc-v-gsp-rm-debugger session: -* the demo firmware self-test must pass (`greeneye demo`, `make test`); +* the demo firmware self-test must pass (`./risc-v-gsp-rm-debugger.sh demo`, `make test`); * the session must contain the expected `hook`/`watch` registrations and a coherent `bp_hit` sequence (the analyzer highlights empty sessions); * the UART banner and control-block magic are cheap liveness checks; -- cgit v1.2.3