Reference Model Scoreboard
Create a scoreboard that compares observed DUT output against a reference model.
Task
Consume transactions through an analysis implementation and report mismatches clearly.
Examples
- expected=0x12, actual=0x12 → PASS
- expected=0x12, actual=0x13 → ERROR
Constraints
- Use uvm_analysis_imp or an equivalent analysis connection.
- Include useful mismatch information.
What this problem is testing
UVM interview problems test transaction flow, ownership, phasing, TLM connections, checking strategy, and whether components remain reusable and debuggable.
Interview habit: before coding, state reset behavior, the state that must be stored, and the conditions that update each output.
Verification plan
- Trace one item from sequence creation through driver activity, monitor observation, and scoreboard checking.
- Inject a mismatch or protocol error to confirm the environment can fail for the correct reason.
- Check that handshakes and analysis connections cannot silently drop transactions.
- Run multiple transactions to exercise queues, ordering, and end-of-test behavior.
Common mistakes
- Putting checking logic in the driver.
- Dropping or duplicating items around sequencer-driver or analysis-port handshakes.
- Ending the test before outstanding transactions are checked.
- Reporting mismatches without enough diagnostic context.
Interview follow-up questions
- Which component should own the reference-model comparison?
- How would you debug a transaction that was driven but never reached the scoreboard?
Concepts to review
scoreboard, analysis, verification
Open Reference Model Scoreboard in the HDLForge interactive editor.
Related problems
- Build a UVM Driver — Medium
- Queue-Based Expected-Value Checker — Medium
- UVM Sequence Item — Medium
- UVM Sequence Body — Medium
- UVM Monitor Analysis Port — Medium
Explore the UVM Practice & Interview Preparation hub.