diff options
Diffstat (limited to 'debug/risc-v-gsp-rm-vm/docs/19-CONTROL-DISCOVERY.md')
| -rw-r--r-- | debug/risc-v-gsp-rm-vm/docs/19-CONTROL-DISCOVERY.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/debug/risc-v-gsp-rm-vm/docs/19-CONTROL-DISCOVERY.md b/debug/risc-v-gsp-rm-vm/docs/19-CONTROL-DISCOVERY.md index 0f9afbe..67ef556 100644 --- a/debug/risc-v-gsp-rm-vm/docs/19-CONTROL-DISCOVERY.md +++ b/debug/risc-v-gsp-rm-vm/docs/19-CONTROL-DISCOVERY.md @@ -1,7 +1,7 @@ # 19 — Control discovery and hot-path reachability > **# TOOL IN DEVELOPMENT - NOT READY YET!** See 00 for status and -> [`GREEN-EYE-ROADMAP.md`](../GREEN-EYE-ROADMAP.md) H4 for the program. +> [`RISC-V-GSP-RM-DEBUGGER-ROADMAP.md`](../RISC-V-GSP-RM-DEBUGGER-ROADMAP.md) H4 for the program. Two harness tools close the loop between "a new firmware image does something we do not model" and "here is the code path, its trigger and its effects": @@ -14,7 +14,7 @@ we do not model" and "here is the code path, its trigger and its effects": Both are simulator-only, bounded, evidence-producing, and depend only on the public `Session`/hook/watch primitives (stdlib-only Python). They are the practical start of the "Sandsifter for RM" idea in -[`GREEN-EYE-ROADMAP.md`](../GREEN-EYE-ROADMAP.md) H4 and reuse the contracts +[`RISC-V-GSP-RM-DEBUGGER-ROADMAP.md`](../RISC-V-GSP-RM-DEBUGGER-ROADMAP.md) H4 and reuse the contracts in [06-ACCURACY](06-ACCURACY.md) and [14-ADVERSARIAL-INTEROP-GUIDE](14-ADVERSARIAL-INTEROP-GUIDE.md). --- @@ -235,7 +235,7 @@ Flags: `--method auto|stimulus|trigger|run|call`, `--all-methods`, `--args`, `auto` tries methods in this order and stops at the first hit (use `--all-methods` to compare routes): -1. `stimulus` — run a green-eye script (or a probe spec's stimulus) with the +1. `stimulus` — run a risc-v-gsp-rm-debugger script (or a probe spec's stimulus) with the target hook and watchpoints armed. The script drives `session.run` itself. 2. `trigger` — read the surface's handler table, find the command ID(s) that resolve to the target, settle the firmware, apply that command and run |