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
SystemVerilog
  • Home
  • Forums
  • SystemVerilog
  • Config_db specialization for virtual interface using modport

Config_db specialization for virtual interface using modport

SystemVerilog 6318
Config_db... 1
MICRO_91
MICRO_91
Full Access
156 posts
January 30, 2023 at 11:16 pm 

LRM  Syntax 25-5  quotes :
data_type ::= 
 virtual [ interface ] interface_identifier [ parameter_value_assignment ] [ . modport_identifier ]

So essentially keyword "interface" and .modport_name are optional.

This would mean within a driver component these 3 would be equivalent 

     virtual  interface  intf.master_cb  vif ;  //  (a)
     virtual  intf.master_cb             vif ;  //  (b)
     virtual  interface  intf            vif   //  (c)
 

For any one of the above 3 handle declaration I wanted to know the legal ways to set and get the interface .

(1) What would be the correct way to set the virtual interface for above driver component ?

       //  Within  top_tb ::
 
        intf  intf_instance ( clk , rst ) ;
 
      initial  //  Keyword  "interface"  used  as  specialization  along  with  interface_type.modport 
        uvm_config_db #( virtual interface intf.master_cb ) :: set ( null , "uvm_test_top.env_h.agent_h.drvr_h" , "vif_intf" , intf_instance ) ;
 
      initial  //  Specialization  is  interface_type.modport 
        uvm_config_db #( virtual intf.master_cb ) :: set ( null , "uvm_test_top.env_h.agent_h.drvr_h" , "vif_intf" , intf_instance ) ;
 
      initial  //  Specialization  is  only  interface_type
        uvm_config_db #( virtual intf ) :: set ( null , "uvm_test_top.env_h.agent_h.drvr_h" , "vif_intf" , intf_instance ) ;
 

Are all 3 cases for uvm_config_db set equivalent ?
Can anyone of these 3 set be used for all 3 cases of handle declaration [ (a) , (b) and (c) ] interchangeably ?

(2) What would be the correct way to get the virtual interface for the driver component ?

       //  Within  driver  component's  build_phase() ::
 
 
       //  (i)   Keyword  "interface"  used  as  specialization  along  with  interface_type.modport 
        uvm_config_db #( virtual interface intf.master_cb ) :: get ( this , "" , "vif_intf" ,  vif ) ;
 
       //  (ii)  Specialization  is  interface_type.modport 
        uvm_config_db #( virtual intf.master_cb ) :: get ( this , "" , "vif_intf" , vif ) ;
 
       //  (iii)  Specialization  is  only  interface_type
        uvm_config_db #( virtual intf ) :: get (  this , "" , "vif_intf" , vif ) ;
 

Are all 3 cases for uvm_config_db get equivalent ?
Can anyone of these 3 get be used for all 3 cases (a) , (b) and (c) interchangeably ?

Replies

Log In to Reply

Solution

Solution

dave_59
dave_59
Forum Moderator
10663 posts
February 01, 2023 at 9:54 pm

In reply to MICRO_91:

First of all, I recommend avoiding modports in testbench code; simulation tools ignore the directions that they are supposed to enforce.

Just because the BNF syntax shows something is optional does not necessarily mean it has no effect on the meaning.

The [interface] keyword is optional just there for visual clarity.

However, the LRM says this about modports in a virtual interface declaration.

Quote:
A virtual interface declaration may select a modport of an interface in which case the modport is also part of its type. An interface instance or virtual interface with no modport selected may be assigned to a virtual interface with a modport selected.

That implies you cannot make assignments from something with a modport to without a modport, or from one modport selected to another modport selected.

— Dave Rich, Verification Architect, Siemens EDA

MICRO_91
MICRO_91
Full Access
156 posts
February 03, 2023 at 11:01 am

Hi Dave ,

I have a clocking block as part of the modport to enforce the direction is followed by respective components.

If I were to declare virtual interface handle as :

virtual  interface  intf.Driver  vif ; //  Clocking  block  driver_cb  is  part of  the  modport  Driver
 
      //  Fetching  virtual  interface  :
if( ! uvm_config_db #( virtual interface  intf ) :: get( this , "" , "vif_intf"  ,  vif ) )
      `uvm_fatal( .. )
 

I observe elaboration error :

Quote:
formal and actual do not have assignment compatible data types (expecting datatype compatible with 'virtual interface intf.Driver' but found 'virtual interface intf' instead)

As ' vif ' has modport in the declaration i.e intf.Driver whereas I am trying to assign non-modport type intf , this results in elaboration error .

The solution would to be use virtual interface intf.Driver as the specialization.
 i.e  uvm_config_db #( virtual interface  intf.Driver )

This also means the modport needs to be part of specialization when setting the virtual interface in top_tb else fatal message .

NOTE : uvm_config_db #( virtual interface  intf ) is a different specialization than uvm_config_db #( virtual interface  intf.Driver )



Quote:
An interface instance or virtual interface with no modport selected may be assigned to a virtual interface with a modport selected.

Using the above quote an alternate solution would be :


 //  top_tb  would  simply  need  to  do  a  single  set  with  no  modport  specialization :
 
 uvm_config_db #( virtual interface intf ) :: set ( null , "uvm_test_top.env_h.agent_h*" , "vintf" , intf_instance );
 
 //  Then  within  Driver  and  Monitor  Components  with  virtual  interface  handles  using  a  modport :
 
    function  void  build_phase( uvm_phase  phase);
     virtual interface  intf  vintf ;
 
   if( ! uvm_cofig_db #( ( virtual interface intf ) :: get ( this , "" , "vintf" , vintf ) )
       `uvm_fatal( .. ) 
 
     //  LHS  is  declared  as  :  virtual  interface  intf.Driver  vintf_driver ;
      vintf_driver =  vintf ;  //  Assigning  virutal  interface with no modport to virtual interface with a modport 
      ....................
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