RTL Studio Open IDE

4.2 · UVM CLASS

raise_objection / drop_objection time control

Use phase objections to keep run_phase alive until stimulus completes.

Watch on YouTube

What you practice

raise_objection / drop_objection time control (4.2). Use phase objections to keep run_phase alive until stimulus completes. It is in Objections — Part 4 · Advanced UVM of the UVM Masterclass. Factory, config objects, virtual sequences, and pipelined drivers for large SoC verification.

The UVM bench compiles in that same browser SystemVerilog simulator. You edit the test in the IDE, run Verilator, and read the log beside the waveform.

What you will learn

You will learn how to keep the UVM run phase alive until stimulus completes by wrapping sequence execution with raise_objection and drop_objection calls in the test's run phase.

Learning objectives

  • Understand why phase objections are needed in UVM to prevent premature phase termination.
  • Learn how to correctly pair phase.raise_objection(this) and phase.drop_objection(this) in the run phase.
  • Practice wrapping sequence execution in the testbench run phase with objection control.
  • Verify simulation completes only after objection is dropped.

Theory

In UVM, the run phase is a *concurrent* phase: all components run in parallel, and the phase ends when the last component finishes. Without objections, the run phase may end before the test sequence completes, causing early simulation termination. Phase objections let a component signal it is still active. Each raise_objection increments a counter; each drop_objection decrements it. The phase ends only when the counter reaches zero.

ActionEffect
phase.raise_objection(this)Increments objection count; phase stays active
phase.drop_objection(this)Decrements objection count; phase may end if count reaches zero

Practice

Open this chapter in RtlStudio. Files appear in Explore under student/. Edit only student/ files.

  1. Open student/tb/tb_top.sv in the editor.
  2. Locate the fifo_base_test run phase (inside class fifo_base_test extends uvm_test).
  3. Wrap the seq.start(...) call with phase.raise_objection(this) before and phase.drop_objection(this) after.
  4. Run Simulation and check the Log panel for INFO: messages.

Summary

You practiced using phase objections to keep the run phase alive during sequence execution in the run_phase of your UVM test. By wrapping the sequence start with raise_objection and drop_objection, you ensured the simulation does not end prematurely before stimulus completes. The key takeaway is that objections provide a reliable mechanism to control phase duration based on active stimulus, preventing premature phase termination.

Run it in the Verilog IDE

  1. Open the UVM workspace in the IDE. The DUT and the testbench compile together in the browser.
  2. Run the SystemVerilog simulation with Verilator and read the phase and scoreboard lines in the log.
  3. When the check is on pins rather than a print, open the VCD next to that log.
  4. Edit the sequence, driver, or scoreboard in the IDE and rerun. You stay in the same simulator.

The lesson is done when the simulation matches raise_objection / drop_objection time control. Change the source, run the Verilog simulator again, and read the waveform without leaving the IDE. Simulation guide · Yosys guide.