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

      • VA Live - Multiple Dates & Locations
      • Interconnect Formal
      • Formal and the Next Normal
      • Formal Verification Made Easy
      • Data Independence and Non-Determinism
      • Exhaustive Scoreboarding
      • Visualizer Debug Environment
      • Webinar Calendar
    • On-Demand Library

      • SystemVerilog Assertions
      • Practical Flows for Continuous Integration
      • Continuous Integration
      • Questa Verification IQ
      • Avery & Siemens VIP
      • Protocol and Memory Interface Verification
      • HPC Protocols & Memories
      • Preparing for PCIe 6.0: Parts I & II
      • High Defect Coverage
      • SoC Design & Functional Safety Flow
      • Complex Safety Architectures
      • All On-Demand Recordings
    • Recording Archive

      • Lint vs Formal AutoCheck
      • FPGA Design Challenges
      • Design Solutions as a Sleep Aid
      • Fix FPGA Failures Faster
      • CDC and RDC Assist
      • The Dog ate my RTL
      • Questa Lint & CDC
      • Hierarchical CDC+RDC
      • Improving Initial RTL Quality
      • CDC Philosophy
      • Hardware Emulation Productivity
      • The Three Pillars of Intent-Focused Insight
      • All Webinar Topics
    • Conferences & WRG

      • 2022 Functional Verification Study
      • Improving Your SystemVerilog & UVM Skills
      • Automotive Functional Safety Forum
      • Aerospace & Defense Tech Day
      • Siemens EDA Functional Verification
      • Industry Data & Surveys
      • DVCon 2023
      • DVCon 2022
      • DVCon 2021
      • Osmosis 2022
      • All Conferences
    • Siemens EDA Learning Center

      • EDA Xcelerator Academy(Learning Services) Verification Training, Badging and Certification
      • View all Xcelerator Academy classes
  • 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
  • How to use set_type_override_by_type to override multiple extended classes from same base class.

How to use set_type_override_by_type to override multiple extended classes from same base class.

UVM 6748
ANASHKU
ANASHKU
Full Access
4 posts
March 31, 2023 at 10:53 am

I am trying to modularize a part of the TB, where a large file is split into individual feature classes. These extended classes will have tasks which needs to be used in base class.
How can I use set_override method to selectively pick methods from multiple classes?

class base_class extends uvm_scoreboard;
 
 
  virtual function void func_b();
      $display("Inside base class");
  endfunction
 
  virtual function void func_e1();
      $display("Inside base class func_e1");
  endfunction
 
  virtual function void func_e2();
      $display("Inside base class func_e2");
  endfunction
 
  virtual function void func_e3();
      $display("Inside base class func_e3");
  endfunction
 
virtual task run();
  func_b();
  func_e1();
  func_e2();
  func_e3();
endtask
 
endclass
 
//----------- extended class 1
class ext_class_1 extends base_class;
  virtual function void func_e1();
  	$display("Inside extended class 1");
  endfunction
 
endclass
 
//----------- extended class 2
class ext_class_2 extends base_class;
  virtual function void func_e2();
  	$display("Inside extended class 2");
  endfunction
endclass
 
//----------- extended class 3
class ext_class_3 extends base_class;
  virtual function void func_e3();
  	$display("Inside extended class 3");
  endfunction
 
endclass
 
class agent extends uvm_agent ;
  base_class b_c ;
  ext_class_1 e_1 ;
  ext_class_2 e_2 ;
  ext_class_3 e_3 ;
 
  function void build();
    if(feature1) begin
    	set_type_override_by_type(base_class::get_type(), ext_class_1::get_type()) ;
    	set_type_override_by_type(base_class::get_type(), ext_class_2::get_type()) ; // this overwrites the prev override
    end
    else if (feature2) begin
    	set_type_override_by_type(base_class::get_type(), ext_class_1::get_type()) ;
    	set_type_override_by_type(base_class::get_type(), ext_class_3::get_type()) ; // this overwrites the prev override
    end
 
  // build base and extended classed using create() method
 
endfunction
 
endclass
 
 
endmodule

Replies

Log In to Reply
dave_59
dave_59
Forum Moderator
10899 posts
March 31, 2023 at 9:17 pm

In reply to ANASHKU:

I do not understand your question. Most of the time factory override calls happen in a different method or even a different class from where the create() happens. And you only create the base class objectb_c = base_class::type_id::create(...) and let the overrides decide if an extended class needs to be constructed instead.

The set_type_override_by_type() method replaces any previous type overrides by default. The set_inst_override_by_type() method does the opposite, first inst override takes precedence.

— Dave Rich, Verification Architect, Siemens EDA

ANASHKU
ANASHKU
Full Access
4 posts
April 03, 2023 at 4:51 pm

In reply to dave_59:

My apologies for the unclear question, let me add more details with an example.

What I want to do is, have multiple classes extended from the base class (component_B and component_C extended from component_A in the below e.g.,) which contain unique virtual methods (display() in component_B and display1() in component_C).
In one simulation I would like to override the base class (component_A) with both the extended class such that when I call the method display() it must recognize that the method is in extended class component_B and first execute it (similar to if I would have just overridden component_B) similarly for display1() is only present in component_C

`include "uvm_macros.svh"
import uvm_pkg::*;
 
class component_A extends uvm_component;
  `uvm_component_utils(component_A)
 
  function new(string name = "component_A", uvm_component parent = null);
    super.new(name, parent);
  endfunction
 
  virtual function display();
    `uvm_info(get_type_name(), $sformatf("inside Base display component_A"), UVM_LOW);
 
  endfunction
 
  virtual function display1();
    `uvm_info(get_type_name(), "inside Base display1 component_A", UVM_LOW);
  endfunction  
 
  virtual task run();
 
    `uvm_info("", "Inside base RUN", UVM_LOW)
    display();
    display1();
  endtask
endclass
 
class component_B extends component_A;
  `uvm_component_utils(component_B)
 
  function new(string name = "component_B", uvm_component parent = null);
    super.new(name, parent);
  endfunction
 
  virtual function display();
    `uvm_info(get_type_name(), "inside display component_B", UVM_LOW);
    super.display();
  endfunction
 
 
  virtual task run();
 
  endtask
 
 
endclass
 
class component_C extends component_A;
  `uvm_component_utils(component_C)
 
  function new(string name = "component_B", uvm_component parent = null);
    super.new(name, parent);
  endfunction
 
  virtual function display1();
    `uvm_info(get_type_name(), "inside display1 component_C", UVM_LOW);
    super.display1();
  endfunction
 
  virtual task run();
 
    `uvm_info("", "Inside ext RUN comp_C", UVM_LOW)
    super.run();
  endtask
 
endclass
 
class my_test extends uvm_test;
  `uvm_component_utils(my_test)
  component_A comp_B, comp_C;
 
  function new(string name = "my_test", uvm_component parent = null);
    super.new(name, parent);
  endfunction
 
  function void build_phase(uvm_phase phase);
    uvm_factory factory = uvm_factory::get();
    super.build_phase(phase);
 
    factory.set_inst_override_by_type(component_A::get_type(), component_B::get_type(), "uvm_test_top.comp_B");    
    factory.set_inst_override_by_type(component_A::get_type(), component_C::get_type(), "uvm_test_top.comp_C");
 
    comp_C = component_A::type_id::create("comp_C", this);
    comp_B = component_A::type_id::create("comp_B", this);
 
    factory.print();
  endfunction
 
  function void end_of_elaboration_phase(uvm_phase phase);
    super.end_of_elaboration_phase(phase);
    uvm_top.print_topology();
  endfunction
 
  task run_phase(uvm_phase phase);
     super.run_phase(phase);
 
    //comp_A.display();
  endtask
endclass
 
module tb_top;
  initial begin
    run_test("my_test");
  end
endmodule

--------------------------------------------------------------------------------------------
Output I am seeing right now -

UVM_INFO testbench.sv(65) @ 0: uvm_test_top.comp_C [] Inside ext RUN comp_C
UVM_INFO testbench.sv(22) @ 0: uvm_test_top.comp_C [] Inside base RUN
UVM_INFO testbench.sv(12) @ 0: uvm_test_top.comp_C [component_C] inside Base display component_A
UVM_INFO testbench.sv(59) @ 0: uvm_test_top.comp_C [component_C] inside display1 component_C
UVM_INFO testbench.sv(17) @ 0: uvm_test_top.comp_C [component_C] inside Base display1 component_A

--------------------------------------------------------------------------------------------
What I am expecting (It is missing the line in bold, display() inside component_B was not overridden) -

UVM_INFO testbench.sv(65) @ 0: uvm_test_top.comp_C [] Inside ext RUN comp_C
UVM_INFO testbench.sv(22) @ 0: uvm_test_top.comp_C [] Inside base RUN
UVM_INFO testbench.sv(36) @ 0: uvm_test_top.comp_B [component_B] inside display component_B
UVM_INFO testbench.sv(12) @ 0: uvm_test_top.comp_C [component_C] inside Base display component_A
UVM_INFO testbench.sv(59) @ 0: uvm_test_top.comp_C [component_C] inside display1 component_C
UVM_INFO testbench.sv(17) @ 0: uvm_test_top.comp_C [component_C] inside Base display1 component_A

dave_59
dave_59
Forum Moderator
10899 posts
April 03, 2023 at 8:18 pm

In reply to ANASHKU:

Your problem is component_A has a task run() that is empty. You either need to have it call super.run, or not define it at all.

Also note the task run is from the OVM and is deprecated. Use run_phase instead.

— Dave Rich, Verification Architect, Siemens EDA

ANASHKU
ANASHKU
Full Access
4 posts
April 03, 2023 at 10:17 pm

In reply to dave_59:

Thanks for the feedback Dave.
I changed the code like you suggested and I still see only one of the override takes affect.
Can I override both extended classes together?
What I mean is, when run_phase in component_A is called, it in turn calls display() and display1().
But since, display() is in component_B it must first print "inside display component_B" and then since we call the super.display() it must print "inside Base display component_A"

Similarly, display1() is in component_C it must first print "inside display1 component_C" and then from super.display1() "inside Base display1 component_A"

But in reality only one override takes affect. So, is there a way where I can have both overrides?

I have the expected output after the code.

`include "uvm_macros.svh"
import uvm_pkg::*;
 
class component_A extends uvm_component;
  `uvm_component_utils(component_A)
 
  function new(string name = "component_A", uvm_component parent = null);
    super.new(name, parent);
  endfunction
 
  virtual function display();
    `uvm_info(get_type_name(), $sformatf("inside Base display component_A"), UVM_LOW);   
  endfunction
 
  virtual function display1();
    `uvm_info(get_type_name(), "inside Base display1 component_A", UVM_LOW);
  endfunction  
 
  task run_phase(uvm_phase phase);
    super.run_phase(phase);
    `uvm_info("", "Inside base RUN", UVM_LOW)
    display();
    display1();
  endtask
 
endclass
 
class component_B extends component_A;
  `uvm_component_utils(component_B)
 
  function new(string name = "component_B", uvm_component parent = null);
    super.new(name, parent);
  endfunction
 
  virtual function display();
    `uvm_info(get_type_name(), "inside display component_B", UVM_LOW);
    super.display();
  endfunction
 
 
  virtual task run_phase(uvm_phase phase);
    `uvm_info("KMK", "Inside ext RUN comp_B", UVM_LOW)
    super.run_phase(phase);
 
  endtask
 
 
endclass
 
class component_C extends component_A;
  `uvm_component_utils(component_C)
 
  function new(string name = "component_B", uvm_component parent = null);
    super.new(name, parent);
  endfunction
 
  virtual function display1();
    `uvm_info(get_type_name(), "inside display1 component_C", UVM_LOW);
    super.display1();
 
  endfunction
 
  task run_phase(uvm_phase phase);  
    `uvm_info("", "Inside ext RUN comp_C", UVM_LOW)
    super.run_phase(phase);
  endtask
 
endclass
 
class my_test extends uvm_test;
  `uvm_component_utils(my_test)
  component_A comp_B, comp_C;
 
  function new(string name = "my_test", uvm_component parent = null);
    super.new(name, parent);
  endfunction
 
  function void build_phase(uvm_phase phase);
    uvm_factory factory = uvm_factory::get();
    super.build_phase(phase);
 
    factory.set_inst_override_by_type(component_A::get_type(), component_B::get_type(), "uvm_test_top.comp_B");    
    factory.set_inst_override_by_type(component_A::get_type(), component_C::get_type(), "uvm_test_top.comp_C");
 
    comp_C = component_A::type_id::create("comp_C", this);
    comp_B = component_A::type_id::create("comp_B", this);
 
    factory.print();
  endfunction
 
  function void end_of_elaboration_phase(uvm_phase phase);
    super.end_of_elaboration_phase(phase);
    uvm_top.print_topology();
  endfunction
 
  task run_phase(uvm_phase phase);
     super.run_phase(phase);
  endtask
 
endclass
 
module tb_top;
  initial begin
    run_test("my_test");
  end
endmodule

---------------------------------------------------

Actual output
UVM_INFO testbench.sv(64) @ 0: uvm_test_top.comp_C [] Inside ext RUN comp_C
UVM_INFO testbench.sv(21) @ 0: uvm_test_top.comp_C [] Inside base RUN
UVM_INFO testbench.sv(12) @ 0: uvm_test_top.comp_C [component_C] inside Base display component_A
UVM_INFO testbench.sv(58) @ 0: uvm_test_top.comp_C [component_C] inside display1 component_C
UVM_INFO testbench.sv(16) @ 0: uvm_test_top.comp_C [component_C] inside Base display1 component_A
UVM_INFO testbench.sv(42) @ 0: uvm_test_top.comp_B [KMK] Inside ext RUN comp_B
UVM_INFO testbench.sv(21) @ 0: uvm_test_top.comp_B [] Inside base RUN
UVM_INFO testbench.sv(36) @ 0: uvm_test_top.comp_B [component_B] inside display component_B
UVM_INFO testbench.sv(12) @ 0: uvm_test_top.comp_B [component_B] inside Base display component_A
UVM_INFO testbench.sv(16) @ 0: uvm_test_top.comp_B [component_B] inside Base display1 component_A

---------------------------------------------------
What I expected (highlighted what's missing)

UVM_INFO testbench.sv(64) @ 0: uvm_test_top.comp_C [] Inside ext RUN comp_C
UVM_INFO testbench.sv(21) @ 0: uvm_test_top.comp_C [] Inside base RUN
UVM_INFO testbench.sv(36) @ 0: uvm_test_top.comp_C [component_C] inside display component_B
UVM_INFO testbench.sv(12) @ 0: uvm_test_top.comp_C [component_C] inside Base display component_A
UVM_INFO testbench.sv(58) @ 0: uvm_test_top.comp_C [component_C] inside display1 component_C
UVM_INFO testbench.sv(16) @ 0: uvm_test_top.comp_C [component_C] inside Base display1 component_A
UVM_INFO testbench.sv(42) @ 0: uvm_test_top.comp_B [KMK] Inside ext RUN comp_B
UVM_INFO testbench.sv(21) @ 0: uvm_test_top.comp_B [] Inside base RUN
UVM_INFO testbench.sv(36) @ 0: uvm_test_top.comp_B [component_B] inside display component_B
UVM_INFO testbench.sv(12) @ 0: uvm_test_top.comp_B [component_B] inside Base display component_A
UVM_INFO testbench.sv(58) @ 0: uvm_test_top.comp_B [component_B] inside display1 component_C
UVM_INFO testbench.sv(16) @ 0: uvm_test_top.comp_B [component_B] inside Base display1 component_A

dave_59
dave_59
Forum Moderator
10899 posts
April 04, 2023 at 12:26 pm

In reply to ANASHKU:

I think you are confusing UVM factory class overrides with how SystemVerilog class inheritance works with method overrides. Both factory overrides are happening to the 2 separate components you created. But each class override only overrides one of the methods.

If you would have extended component_C from component_B, then you would have gotten the "inside display component_B" from component_C.

What you seem to be looking for might be what is known as a policy class. This is where you can associate each method with a seperate class, and override them individually, See https://dvcon-proceedings.org/document/design-patterns-by-example-for-systemverilog-verification-environments-enabled-by-systemverilog-1800-2012-presentation/

— Dave Rich, Verification Architect, Siemens EDA

ANASHKU
ANASHKU
Full Access
4 posts
April 05, 2023 at 6:19 pm

In reply to dave_59:

Thanks for the clarification Dave. Ill go through the document in the link.

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