Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • Start Here4
  • UVM Foundations14
  • UVM Phases & Simulation Lifecycle26
  • Factory & Configuration15
  • Transaction-Level Modeling (TLM)13
  • UVM Sequences & Stimulus21
  • UVM Agents & Protocol VIP21
  • Environment & Test Classes11
  • Checking & Coverage in UVM21
  • UVM Register Abstraction Layer (RAL)22
  • Advanced UVM in Practice13
  • Debug & Regression10
  • Coding Practice47
    • How to Use This Course
    • Whiteboard Delivery Framework
    • Scoreboard Coding
      • Ordered FIFO Compare
      • Out-of-Order Reorder Buffer
      • Multi-Stream Merge
      • Predictor & Reference Model
      • Scoreboard Tricky Q&A
    • Monitor & Driver Coding
    • Sequences Coding
    • TLM & Analysis
    • RAL & Adapters
    • Factory & config_db
    • Phases & Objections
    • Env & Test Architecture
    • Debug Broken Testbench
    • Mock Interview Sets
    • Senior UVM Coding Cheat Sheet
  • Verification in Industry Practice10
  • Senior Prep: Architecture, Leadership and Interviews32
Loading lesson

←Scoreboard Coding
  1. Topics
  2. UVM Verification
  3. Coding Practice
  4. Scoreboard Coding
  5. Multi-Stream Merge
On this page

    UVM Coding PracticeSenior

    Multi-Stream Merge

    Two analysis imports, keyed compare, cross-stream ordering.

    Interview prompt

    DUT has read and write channels. Sketch one scoreboard with two compare paths.

    Diagram
    WHITEBOARD CHAIN
    
    1. DECLARE    interfaces / types / ports you need
    2. SKELETON   class extends + utils macro + key methods
    3. MECHANISM  fill one critical method while narrating
    4. PITFALL    name one bug juniors make on this pattern
    5. TEST       how you would smoke-test the component

    Reference sketch (≤40 lines)

    design.sv
    1
    2
    3
    4
    uvm_analysis_imp_rd #(txn, sb) rd_imp;
    uvm_analysis_imp_wr #(txn, sb) wr_imp;
    txn exp_rd[$], act_rd[$], exp_wr[$], act_wr[$];
    // separate compare_head per stream

    Common pitfalls

    • Mixing read/write in one FIFO without opcode tag.

    • Cross-stream ordering assumed when independent.

    Smoke test (5 minutes)

    • Directed read then write; verify separate queues drain.

    Previous

    188 / 280

    Next: Scoreboard Mismatch Playbook

    Up next

    Up nextScoreboard Mismatch Playbook

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Ordered FIFO Compare
    • Predictor & Reference Model
    • Scoreboard Tricky Q&A