Verification Academy

Search form

My Account Menu

  • Register
  • Log In
  • Topics
  • Courses
  • Forums
  • Patterns Library
  • Cookbooks
  • Events
  • More
  • All Topics
    The Verification Academy offers users multiple entry points to find the information they need. One of these entry points is through Topic collections. These topics are industry standards that all design and verification engineers should recognize. While we continue to add new topics, users are encourage to further refine collection information to meet their specific interests.
    • Languages & Standards

      • Portable Test and Stimulus
      • Functional Safety
      • Design & Verification Languages
    • Methodologies

      • UVM - Universal Verification Methodology
      • UVM Framework
      • UVM Connect
      • FPGA Verification
      • Coverage
    • Techniques & Tools

      • Verification IQ
      • Verification IP
      • Static-Based Techniques
      • Simulation-Based Techniques
      • Planning, Measurement, and Analysis
      • Formal-Based Techniques
      • Debug
      • Acceleration
  • All Courses
    The Verification Academy is organized into a collection of free online courses, focusing on various key aspects of advanced functional verification. Each course consists of multiple sessions—allowing the participant to pick and choose specific topics of interest, as well as revisit any specific topics for future reference. After completing a specific course, the participant should be armed with enough knowledge to then understand the necessary steps required for maturing their own organization’s skills and infrastructure on the specific topic of interest. The Verification Academy will provide you with a unique opportunity to develop an understanding of how to mature your organization’s processes so that you can then reap the benefits that advanced functional verification offers.
    • Universal Verification Methodology (UVM)

      • Introduction to UVM
      • UVM Basics
      • Advanced UVM
      • UVM Connect
      • UVM Debug
      • UVMF - One Bite at a Time
    • Featured Courses

      • Introduction to ISO 26262
      • Introduction to DO-254
      • Clock-Domain Crossing Verification
      • Portable Stimulus Basics
      • Power Aware CDC Verification
      • Power Aware Verification
      • SystemVerilog OOP for UVM Verification
    • Additional Courses

      • Assertion-Based Verification
      • An Introduction to Unit Testing with SVUnit
      • Evolving FPGA Verification Capabilities
      • Metrics in SoC Verification
      • SystemVerilog Testbench Acceleration
      • Testbench Co-Emulation: SystemC & TLM-2.0
      • Verification Planning and Management
      • VHDL-2008 Why It Matters
    • Formal-Based Techniques

      • Formal Assertion-Based Verification
      • Formal-Based Technology: Automatic Formal Solutions
      • Formal Coverage
      • Getting Started with Formal-Based Technology
      • Handling Inconclusive Assertions in Formal Verification
      • Sequential Logic Equivalence Checking
    • Analog/Mixed Signal

      • AMS Design Configuration Schemes
      • Improve AMS Verification Performance
      • Improve AMS Verification Quality
  • All Forum Topics
    The Verification Community is eager to answer your UVM, SystemVerilog and Coverage related questions. We encourage you to take an active role in the Forums by answering and commenting to any questions that you are able to.
    • UVM Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • UVM Forum
    • SystemVerilog Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • SystemVerilog Forum
    • Coverage Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • Coverage Forum
    • Additional Forums

      • Announcements
      • Downloads
      • OVM Forum
  • Patterns Library
    The Verification Academy Patterns Library contains a collection of solutions to many of today's verification problems. The patterns contained in the library span across the entire domain of verification (i.e., from specification to methodology to implementation—and across multiple verification engines such as formal, simulation, and emulation).
    • Implementation Patterns

      • Environment Patterns
      • Stimulus Patterns
      • Analysis Patterns
      • All Implementation Patterns
    • Specification Patterns

      • Occurrence Property Patterns
      • Order Property Patterns
      • All Specification Patterns
    • Pattern Resources

      • Start Here - Patterns Library Overview
      • Whitepaper - Taking Reuse to the Next Level
      • Verification Horizons - The Verification Academy Patterns Library
      • Contribute a Pattern to the Library
  • All Cookbooks
    Find all the methodology you need in this comprehensive and vast collection. The UVM and Coverage Cookbooks contain dozens of informative, executable articles covering all aspects of UVM and Coverage.
    • UVM Cookbook

      • UVM Basics
      • Testbench Architecture
      • DUT-Testbench Connections
      • Configuring a Test Environment
      • Analysis Components & Techniques
      • End Of Test Mechanisms
      • Sequences
      • The UVM Messaging System
      • Other Stimulus Techniques
      • Register Abstraction Layer
      • Testbench Acceleration through Co-Emulation
      • Debug of SV and UVM
      • UVM Connect - SV-SystemC interoperability
      • UVM Versions and Compatibility
      • UVM Cookbook
    • Coding Guidelines & Deployment

      • Code Examples
      • UVM Verification Component
      • Package/Organization
      • Questa/Compiling UVM
      • SystemVerilog Guidelines
      • SystemVerilog Performance Guidelines
      • UVM Guidelines
      • UVM Performance Guidelines
    • Coverage Cookbook

      • Introduction
      • What is Coverage?
      • Kinds of Coverage
      • Specification to Testplan
      • Testplan to Functional Coverage
      • Bus Protocol Coverage
      • Block Level Coverage
      • Datapath Coverage
      • SoC Coverage Example
      • Requirements Writing Guidelines
      • Coverage Cookbook
  • All Events
    No one argues that the challenges of verification are growing exponentially. What is needed to meet these challenges are tools, methodologies and processes that can help you transform your verification environment. These recorded seminars from Verification Academy trainers and users provide examples for adoption of new technologies and how to evolve your verification process.
    • Featured & On-Demand

      • Continuous Integration - March 28th
      • Questa Verification IQ - April 11th
      • SystemVerilog Assertions
      • SoC Design & Functional Safety Flow
      • 2022 Functional Verification Study
      • Design Solutions as a Sleep Aid
      • CDC and RDC Assist
      • Formal and the Next Normal
      • Protocol and Memory Interface Verification
      • Webinar Calendar
    • On-Demand Library

      • Practical Flows for Continuous Integration
      • Lint vs Formal AutoCheck
      • The Three Pillars of Intent-Focused Insight
      • Formal Verification Made Easy
      • Fix FPGA Failures Faster
      • HPC Protocols & Memories
      • FPGA Design Challenges
      • High Defect Coverage
      • The Dog ate my RTL
      • Questa Lint & CDC
      • Complex Safety Architectures
      • Data Independence and Non-Determinism
      • Hierarchical CDC+RDC
      • All On-Demand Recordings
    • Recording Archive

      • Aerospace & Defense Tech Day
      • Exhaustive Scoreboarding
      • Improving Initial RTL Quality
      • CDC Philosophy
      • Hardware Emulation Productivity
      • Visualizer Debug Environment
      • Preparing for PCIe 6.0: Parts I & II
      • Automotive Functional Safety Forum
      • Siemens EDA Functional Verification
      • Improving Your SystemVerilog & UVM Skills
      • All Webinar Topics
    • Conferences & WRG

      • Industry Data & Surveys
      • DVCon 2023
      • DVCon 2022
      • DVCon 2021
      • Osmosis 2022
      • All Conferences
    • Siemens EDA Learning Center

      • SystemVerilog Fundamentals
      • SystemVerilog UVM
      • EDA Xcelerator Academy(Learning Services) Verification Training, Badging and Certification
      • View all Learning Paths
  • About Verification Academy
    The Verification Academy will provide you with a unique opportunity to develop an understanding of how to mature your organization's processes so that you can then reap the benefits that advanced functional verification offers.
    • Blog & News

      • Verification IQ
      • Verification Horizons Blog
      • Technical Resources
    • Verification Horizons Publication

      • Verification Horizons - March 2023
      • Verification Horizons - December 2022
      • Verification Horizons - July 2022
      • Issue Archive
    • About Us

      • Verification Academy Overview
      • Subject Matter Experts
      • Academy News
      • Contact Us
    • Training

      • Learning @OneGlance (PDF)
      • SystemVerilog & UVM Classes
      • Siemens EDA Classes
Ask a Question
UVM
  • Home
  • Forums
  • UVM
  • Individual tests extending from base test

Individual tests extending from base test

UVM 6659
#uvm 278 #polymorphism# 1
dvuvmsv
dvuvmsv
Forum Access
48 posts
November 16, 2019 at 1:20 am

Hello,

I have a basic question in all other tests ( apb_test_1, apb_test_2, apb_test_3 )
extending from apb_base_test. I have separate sequences for each test
apb_test_1 has apb_sequence_1 which need to be run in sequencer
apb_test_2 has apb_sequence_2 which need to be run in sequencer.

My question is since I am extending these tests from apb_base_test,
can I skip these
// 1. apb_env env; virtual dut_if if;
// 2. function new
// 3. build_phase
and directly write run_phase() method, and start the corresponding sequencer
OR
Do I need to write all 1,2,3 above?

JeffD

class apb_base_test extends uvm_test;
`uvm_component_utils(apb_base_test);
 
  apb_env  env;
  virtual dut_if vif;
 
  function new(string name = "apb_base_test", uvm_component parent = null);
    super.new(name, parent);
  endfunction
 
  function void build_phase(uvm_phase phase);
    env = apb_env::type_id::create("env", this);
    if (!uvm_config_db#(virtual dut_if)::get(this, "", "vif", vif)) begin
      `uvm_fatal("build_phase", "No virtual interface specified for this test instance")
    end 
    uvm_config_db#(virtual dut_if)::set( this, "env", "vif", vif);
  endfunction
 
  //Run phase - Create an abp_sequence and start it on the apb_sequencer
  task run_phase( uvm_phase phase );
    apb_sequence apb_seq;
    apb_seq = apb_sequence::type_id::create("apb_seq");
    phase.raise_objection( this, "Starting apb_base_seqin main phase" );
    $display("%t Starting sequence apb_seq run_phase",$time);
    apb_seq.start(env.agt.sqr);
    #100ns;
    phase.drop_objection( this , "Finished apb_seq in main phase" );
  endtask
 
endclass
 
 
class apb_test_1 extends apb_base_test;
  //  Since I am extending from apb_base_test above,   do I need to 
  //  1. apb_env env;  virtual dut_if if;
  //  2. function new 
  //  3. build_phase
  //  4. 
endclass

Replies

Log In to Reply
dave_59
dave_59
Forum Moderator
10658 posts
November 16, 2019 at 8:15 am

In reply to dvuvmsv:

When extending any class, you must define a new() if there are constructor arguments that need to be passed down.

You should definitely not re-declare env or vif. The whole point of inheritance is using the variable declared in the base class.

Whether or not you override build_phase or run_phase depends on how different each test is. If the only different is which sequence to start, than you can use the build_phase to set a factory override, and then you don't need a different run_phase for each test.

class apb_test_1 extends apb_base_test;
 function new(string name = "apb_test_1", uvm_component parent = null);
    super.new(name, parent);
  endfunction
  function void build_phase(uvm_phase phase);
    set_type_override_by_type(apb_sequence::get_type(), apb_sequence_1::get_type());
    super.build_phase(phase);
  endfunction
endclass

— Dave Rich, Verification Architect, Siemens EDA

dvuvmsv
dvuvmsv
Forum Access
48 posts
November 16, 2019 at 9:30 pm

Thank you Dave for your response. You gave an example for factory override
and that way we don't need to have a run_phase. Just override the apb_sequence with apb_sequence_1

Otherwise we need to have the following with run_phase.

class apb_test_1 extends apb_base_test;

`uvm_component_utils(apb_test_1);

function new(string name = "apb_test_1", uvm_component parent = null);
super.new(name, parent);
endfunction

function void build_phase(uvm_phase phase);
super.build_phase(phase);
endfunction

task run_phase( uvm_phase phase );
apb_sequence_1 apb_seq_1;
apb_seq_1 = apb_sequence_1::type_id::create("apb_seq_1");
phase.raise_objection( this, "Starting apb_sequence_1 in main phase" );
$display("%t Starting sequence apb_seq_1 run_phase",$time);
apb_seq_1.start(env.agt.sqr);
#100ns;
phase.drop_objection( this , "Finished apb_seq_1 in main phase" );
endtask

endclass

dvuvmsv
dvuvmsv
Forum Access
48 posts
November 16, 2019 at 10:15 pm

Hi,

I need to specify a addr=32'100 and data=32'd200 using `uvm_do_with in a sequence.
Here I am not randomizing. When I run the test , I am not getting addr 32'd100 and data 32'd200. Is there anything wrong with this ?

class apb_transaction extends uvm_sequence_item;

`uvm_object_utils(apb_transaction)

//typedef for READ/Write transaction type
typedef enum {READ, WRITE} kind_e;
rand bit [31:0] addr; //Address
rand bit [31:0] data; //Data - For write or read response
rand kind_e pwrite; //command type

constraint c1{addr[31:0]>=32'd0; addr[31:0] <32'd256;};
constraint c2{data[31:0]>=32'd0; data[31:0] <32'd256;};

function new (string name = "apb_transaction");
super.new(name);
endfunction

function string convert2string();
return $psprintf("pwrite=%s paddr=%0h data=%0h",pwrite,addr,data);
endfunction

endclass

class apb_sequence_2 extends uvm_sequence#(apb_transaction);
`uvm_object_utils(apb_sequence_2)

function new (string name = "");
super.new(name);
endfunction

task body();
apb_transaction rw_trans_2;
repeat(1)
begin
rw_trans_2=new();
`uvm_do_with(rw_trans_2, {rw_trans_2.addr == 32'd100;
rw_trans_2.data == 32'd200;
rw_trans_2.pwrite == WRITE;
});

end
endtask

endclass

class apb_test_2 extends apb_base_test;

`uvm_component_utils(apb_test_2);

function new(string name = "apb_test_2", uvm_component parent = null);
super.new(name, parent);
endfunction

function void build_phase(uvm_phase phase);
super.build_phase(phase);
endfunction

task run_phase( uvm_phase phase );
apb_sequence_2 apb_seq_2;
apb_seq_2 = apb_sequence_2::type_id::create("apb_seq_2");
phase.raise_objection( this, "Starting apb_sequence_2 in main phase" );
$display("%t Starting sequence apb_seq_2 run_phase",$time);
apb_seq_2.start(env.agt.sqr);
#100ns;
phase.drop_objection( this , "Finished apb_seq_2 in main phase" );
endtask

endclass

JeffD

chr_sue
chr_sue
Full Access
3846 posts
November 17, 2019 at 12:01 am

In reply to dvuvmsv:

I see 2 weaknesses in your code:
(1) constructing your seq_item
rw_trans_2=new();
It should be like this (using the create of the factory):
rw_trans_2 = apb_transaction::type_id::create("rw_trans_2");
(2) never use $display in your UVM code use instead `uvm_info

Both do not influence the seq_item generation.
But you do not show which test you are executing.

dvuvmsv
dvuvmsv
Forum Access
48 posts
November 17, 2019 at 8:26 am

Thanks chr_sue for the suggestions.
I was able to get the specific address.
It was a %h vs %d issue where the data was correct,
but in a different format and I could'nt recognize

JeffD

Siemens Digital Industries Software

Siemens Digital Industries Software

#TodayMeetsTomorrow

Portfolio

  • Cloud
  • Mendix
  • Electronic Design Automation
  • MindSphere
  • Design, Manufacturing and PLM Software
  • View all Portfolio

Explore

  • Community
  • Blog
  • Online Store

Siemens

  • About Us
  • Careers
  • Events
  • News and Press
  • Customer Stories
  • Partners
  • Trust Center

Contact

  • VA - Contact Us
  • PLM - Contact Us
  • EDA - Contact Us
  • Worldwide Offices
  • Support Center
  • Give us Feedback
© Siemens 2023
Terms of Use Privacy Statement Cookie Statement DMCA