Facts verified against RouteWave 2.4.0 and rr 5.1.1 on 2026-10-30.

Source Link connects three things: a signal in the wave, the line of RTL that declares it, and the test assert that checks it. rr sim run writes the map from signal to declaration. RouteWave reads it for whereis and sourcepeek. triage reads a second map, from assert to signal and time, and shows all three in one step.

Source Link: wave signal to source map to RTL declaration; triage adds the failing-test map
Source Link files and commands

The source map

rr sim run with nvc and waves on writes <top>.srcmap.json beside the wave. It runs a separate pass over the elaborated design, so the map does not depend on signal values, and a repeated run of an unchanged design reuses it. RR_NO_SRCMAP=1 turns it off; a coverage run skips it.

One entry, from the pulse counter used in RouteWave from rr:

"pulse_counter.cnt": {
  "decl": "cnt",
  "file": "src/pulse_counter.vhd",
  "kind": "sig",
  "line": 17
}
FieldMeaning
KeyInstance path, spelled as in the wave hierarchy
fileProject-relative source file
lineDeclaration line; null when it could not be resolved
kindsig or port
declDeclared name

whereis and sourcepeek

CommandOutput
srcmap statusNumber of mapped signals, top level, source of the line numbers, map file
srcmap load <file>Loads a map file
whereis <signal>file:line (kind decl)
whereis --open <signal>The same, then opens the file at the line in the editor named by VISUAL, EDITOR or the configured editor template
sourcepeek <signal>A read-only Source Peek window around the declaration

A signal name resolves loosely: whereis count and whereis pulse_counter.count give the same line.

$ routewave_cli -c "open pulse_counter.fst; whereis pulse_counter.cnt; whereis count"
Loaded 8 channel(s) from 'pulse_counter.fst'.
Source map: 8 signal(s) from 'pulse_counter.srcmap.json' (whereis <signal>).
src/pulse_counter.vhd:17  (sig cnt)
src/pulse_counter.vhd:10  (port count)

open in the console loads <wave>.srcmap.json from beside the wave. A window started with the wave on the command line, as rr sim waves starts it, does not load the map in RouteWave 2.4.0: whereis replies No source map for this wave. srcmap load loads it in that window:

srcmap load sim/waves/test_pulse_counter/pulse_counter.srcmap.json
whereis pulse_counter.cnt
sourcepeek pulse_counter.cnt
RouteWave 2.4.0 with the Source Peek window open on the declaration of cnt, line 17 of pulse_counter.vhd
RouteWave 2.4.0 started by rr sim waves, after srcmap load, whereis and sourcepeek. Line 17 is highlighted.

sourcepeek resolves a relative file against the directory of the map, then against the working directory of RouteWave. rr starts RouteWave in the directory rr runs in, here the project directory, so src/pulse_counter.vhd resolves.

Failing-test triage

rr vboard save-test <record> turns a recorded virtual-board session into a cocotb test and writes <test>.testmap.json beside it. Each entry of the test map is one assert of that test: signal instance path, simulation time in ns, width and expected value.

CommandEffect
triage load <test>.testmap.jsonLoads the test map
triage listOne line per assert: index, time, signal, expected value
triage assert <n>Moves the cursor to the assert time, adds the marker assert#<n>:<signal>, and prints the three lines below
triage assert <n> --openThe same, then opens the RTL line in the editor

The three lines of triage assert <n>:

LineContent
WAVE @ <t> nsCursor time and the marker name
TEST assert #<n> <signal> expected=0x<value> (width <w>)What the test expected
RTL <file>:<line> (<kind> <decl>)The declaration, from the source map

Items to confirm

ItemObservation
triageNot run for this article: no recorded virtual-board session was made. The command forms and output lines are taken from the RouteWave 2.4.0 source.
Simulatorsrr 5.1.1 writes the source map from the nvc run. Other simulators were not checked.
rr sim run --viewStarts RouteWave through the same launcher as rr sim waves, so the same srcmap load step is expected. Not run for this article.
Line numbersWith nvc, rr finds declaration lines by parsing the source; srcmap status reports this as line_source=shim.