The bind construct instantiates a verification module inside an RTL module without editing the RTL source. The bound instance sees the target's ports and internal signals, which makes bind the standard delivery mechanism for checkers on design code that DV does not own.
BIND — WHO OWNS WHAT
RTL repo DV repo
────────────── ─────────────────────────
fifo.sv <-- no edits --- fifo_checker.sv
arbiter.sv arb_checker.sv
subsystem_binds.sv:
bind fifo fifo_checker ...
bind arbiter arb_checker ...
|
v elaboration
+------------------------------+
| fifo (every instance) |
| |- ... RTL contents ... |
| └- fifo_checker chk (DV) | <- lives inside the
+------------------------------+ target's scopeLesson | What it covers | Path |
|---|---|---|
Targets, port maps, and what elaboration produces. | Required | |
Input-only conventions and a valid-ready checker. | Required | |
One bind file per subsystem, ordering, and guards. | Optional | |
Parameterized checkers, the checker construct, and releases. | Recommended | |
Elaboration triage, waves, and bind against inline. | Recommended |
Required is the core first pass for this part's goal, Recommended is for most learners, and Optional is reference, specialist or revision material. Bind File Organization matters once an environment has many binds.
The target's internal signals: FSM state, counters, and grants resolve by name in the target's scope, with no RTL edits and no fragile hierarchical paths from the testbench.