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

AboutContactPrivacyTerms
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
    • Monitor & Driver Coding
    • Sequences Coding
    • TLM & Analysis
    • RAL & Adapters
    • Factory & config_db
    • Phases & Objections
      • Objection Count & Drain Time
      • Phase Jump & Domain Sync
      • Run-Time Sub-Phases
      • Phases Tricky Q&A
    • 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

‹Phases & Objections
  1. Topics
  2. UVM Verification
  3. Coding Practice
  4. Phases & Objections
  5. Run-Time Sub-Phases

UVM Coding Practice · Senior

Run-Time Sub-Phases

reset, configure, main, shutdown.

On this page

    Interview prompt

    List UVM run-time sub-phases and what runs in each.

    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
    1. reset_phase — apply reset, wait reset release, flush FIFOs

    2. configure_phase — program registers, load cfg

    3. main_phase — primary stimulus (sequences)

    4. shutdown_phase — wait idle, drain, summary report

    Mechanism to narrate

    • UVM 1.2 splits run_phase into sub-phases automatically

    • Override task reset_phase/main_phase etc. instead of one giant run

    • Objections can be per sub-phase or owned by test

    Smoke test (5 minutes)

    • Narrate which sub-phase runs your APB seq.

    • Show reset_phase task that waits PREADY idle before main.

    Common pitfalls

    • All stimulus in run_phase task ignoring sub-phases.

    • Reset tasks in main_phase after traffic started.

    Previous

    223 / 280

    Next: Phases Tricky Q&A

    Up next

    Up nextPhases Tricky Q&A

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Objection Count & Drain Time