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
  • uvm_config_db / uvm_resource_db for registering virtual interfaces

uvm_config_db / uvm_resource_db for registering virtual interfaces

UVM 6661
uvm_config_db 38 virtual interface 8
Vperrin
Vperrin
Forum Access
9 posts
June 06, 2017 at 6:53 am

Hi UVM experts,

I read from the Advanced UVM book (Second Edition) that resource_db must be used when information is not associated with any part of the uvm component hierarchy, otherwise we must use config_db.
Therefore according to the author, it is recommended to use resource_db for handling virtual interface registration.
However i came with cases where component hierarchy matters for registering virtual interfaces such as follows :

Tx_env contains one apb agent
Rx_env contains one apb agent
Top_env contains one tx_env and one rx_env.
In testbench I have two differents apb interfaces, one for rx and one for tx.

In this case, how can i use resource_db for registering the two apb interfaces as I use the same apb class for tx and rx ?

Best regards,

Victor Perrin
Verification Engineer

Replies

Log In to Reply
chr_sue
chr_sue
Full Access
3846 posts
June 06, 2017 at 7:49 am

In reply to Vperrin:

Hi Victor,

first, never use resource_db. Instead use config_db. config_db is a layer put around the resource_db adding more flexibility.
second, passing virtual interfaces to the config_db has nothing to do with classes.
third, you can pass the handles of the virtual Interfaces to the config_db like this in the toplevel module of your UVM testbench:

apb_if   apb_ifrx();
apb_if   apb_iftx();
 
initial
begin
 uvm_config_db #(virtual apb_if)::set(null, "uvm_test_top", "apb_if_tx", apb_iftx);
 uvm_config_db #(virtual apb_if)::set(null, "uvm_test_top", "apb_if_rx", apb_ifrx)
....
end
Vperrin
Vperrin
Forum Access
9 posts
June 06, 2017 at 8:04 am

In reply to chr_sue:

Thanks for the feedback.
My concern was more about how to register virtual interfaces with resource_db when you have multiple instances of the same agent, but i can see that config_db is more appropriate.
That s why it was confusing me that the book recommended to use resource_db for registering virtual interfaces.

chr_sue
chr_sue
Full Access
3846 posts
June 06, 2017 at 8:13 am

In reply to Vperrin:
Using resource_db does not look so different.
But you have seen how to deal with 2 instances of the same interface type.
You do not pass the Interface type to the config_db but there instances.

Vperrin
Vperrin
Forum Access
9 posts
June 06, 2017 at 8:21 am

In reply to chr_sue:

The problem i see for resource_db is the following :
Here is the code for driver. It s getting virtual interface with name and scope but it does not have information about hierarchy. If we have apb_tx and apb_rx agent how can you get correctly the corresponding interfaces to each agent instances.

class apb_driver extends uvm_driver #(apb_trans);
     virtual interface apb_interface vif;
 
    `uvm_component_utils(apb_driver)
 
    virtual function void build_phase(uvm_phase phase);
        super.build_phase(phase);
        if(!uvm_resource_db#(virtual interface apb_interface)::get("apb_pkg", "vif", vif))
         `uvm_fatal(get_type_name(), "Unable to get virtual interface");
 
    endfunction: build_phase
chr_sue
chr_sue
Full Access
3846 posts
June 06, 2017 at 8:33 am

In reply to Vperrin:

It depends how you are Setting the context. You could use a wildcard(*). Then it should work.

Vperrin
Vperrin
Forum Access
9 posts
June 06, 2017 at 9:18 am

In reply to chr_sue:

So the testbench would look like this

module top
interface apb_interface apb_tx_if();
interface apb_interface apb_rx_if();
 
initial begin
  uvm_resource_db#(...)
end
 
endmodule

How would you set the resource_db with the apb interfaces ?

chr_sue
chr_sue
Full Access
3846 posts
June 06, 2017 at 9:38 am

In reply to Vperrin:

First I have to correct ny Syntax:

module top
  apb_interface apb_tx_if(); // the keyword interface was wrong in this place
  apb_interface apb_rx_if();
 
initial begin
  uvm_resource_db #(virtual apb_interface) ("*", "apb_tx", apb_tx_if );
  uvm_resource_db #(virtual apb_interface) ("*", "apb_rx", apb_rx_if );
 
end
 
endmodule
Vperrin
Vperrin
Forum Access
9 posts
June 06, 2017 at 10:05 am

In reply to chr_sue:

You're right about the syntax.

What you described won't work in the case described because of the following code in the agent implemented for getting virtual interface

virtual function void build_phase(uvm_phase phase);
        super.build_phase(phase);
        if(!uvm_resource_db#(virtual interface apb_interface)::get("apb_pkg", "vif", vif))
         `uvm_fatal(get_type_name(), "Unable to get virtual interface");
 
endfunction: build_phase
chr_sue
chr_sue
Full Access
3846 posts
June 06, 2017 at 11:15 am

In reply to Vperrin:

virtual function void build_phase(uvm_phase phase);
        super.build_phase(phase);
        if(!uvm_resource_db#(virtual interface apb_interface)::get("", "apb_tx", vif))
         `uvm_fatal(get_type_name(), "Unable to get virtual interface");
 
endfunction: build_phase
Vperrin
Vperrin
Forum Access
9 posts
June 06, 2017 at 12:47 pm

In reply to chr_sue:

If you do that, that means you have different code for apb_tx and apb_rx. I want the two agents to use the same class.

chr_sue
chr_sue
Full Access
3846 posts
June 06, 2017 at 1:49 pm

In reply to Vperrin:

What do you mean with the 'same class'. An interface is not a class. It is a SV Interface. And a virtual interface uses the SV Interface as a type.
I understood you have 2 Interfaces of the same type. One is stored in the config_db/resource_db under the Name "apb_tx" and the other one under the name "apb_rx".

Vperrin
Vperrin
Forum Access
9 posts
June 07, 2017 at 5:13 am

In reply to chr_sue:

I meant same class for the agents as described in the following example :

apb_agent_c apb_tx;
apb_agent_c apb_rx;
 
virtual task build_phase(uvm_phase phase);
        apb_tx = apb_agent_c::type_id::create("apb_tx", this);
        apb_rx = apb_agent_c::type_id::create("apb_rx", this);
endtask: build_phase
chr_sue
chr_sue
Full Access
3846 posts
June 07, 2017 at 5:27 am

In reply to Vperrin:

This is the build_phase function of your env. Right?
There is also no Problem. The resource_db/config_db is storing the Interfaces under seperate names.
I'd make the names of the agents and the config_db names different.

Vperrin
Vperrin
Forum Access
9 posts
June 07, 2017 at 5:46 am

In reply to chr_sue:

Yes this is the build_phase of the env. I don't see any problem for the config_db but I still have the issue with resource_db.

Ok you can put different names in the resource_db in your top module ("apb_tx", "apb_rx") but in the agent build_phase when you call resource_db you don't know which string to provide for the name

chr_sue
chr_sue
Full Access
3846 posts
June 07, 2017 at 6:02 am

In reply to Vperrin:

In the env you have to retrieve the data usingg the same name:
if the set in the toplevel module uses as name "apb_tx" you have to perform the get for the same Name.

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