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

      • Questa Verification IQ - April 11th
      • Continuous Integration
      • 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
  • Illegal virtual interface dereference error

Illegal virtual interface dereference error

UVM 6670
#uvm 278 #virtual_interface 2 #error 5 #makefile #questasim ... 1 #systemverilog 100
Appledore22
Appledore22
Forum Access
3 posts
July 11, 2019 at 7:28 am

Driver Code -
class d_driver extends uvm_driver #(seq_item);
`uvm_component_utils(d_driver)
virtual d_interface intf1;

function new (string name,uvm_component parent);
super.new(name,parent);
endfunction

function void build_phase(uvm_phase phase);
super.build_phase(phase);
if(!uvm_config_db#(virtual d_interface)::get(this,"","d_interface",intf1))
`uvm_error("", "uvm_config_db::get - Failed")

endfunction

task run_phase(uvm_phase phase);
phase.raise_objection(this);
seq_item_port.get_next_item(req);
$display("--------------------------------- Received Item------------------------------");
req.print();
seq_item_port.item_done();
#20;
put_data();
phase.drop_objection(this);

endtask


task put_data();
intf1.addr <= req.addr;
intf1.data <= req.data;
intf1.rd_en <= req.rd_en;
intf1.wr_en <= req.wr_en;
endtask

endclass

top code -
`include "uvm_macros.svh"
import uvm_pkg::*;
`include "d_interface.sv"
`include "d_dut.v"
`include "seq_item.sv"
`include "s_sequencer.sv"
`include "s_sequence.sv"
`include "d_driver.sv"
`include "d_env.sv"
`include "d_test.sv"

module tb_top;


d_interface d1();
d_dut dut1(.intf(d1));

initial begin
uvm_config_db#(virtual d_interface)::set(null,"*","d_interface",d1);
uvm_top.finish_on_completion = 1;
run_test("d_test");
end

endmodule

Error -
** Fatal: Illegal virtual interface dereference.

I don't think there is any error in interface file. But in case you need other file as well let me know.

Replies

Log In to Reply

Solution

Solution

chr_sue
chr_sue
Full Access
3850 posts
July 12, 2019 at 7:17 am

In reply to Appledore22:

The error message is typical when a testbench component does not get the virtual interface from the config_db.

And you should put the following lines of code to the connect_phase:

if(!uvm_config_db#(virtual d_interface)::get(this,"","d_interface",intf1))
`uvm_error("", "uvm_config_db::get - Failed")
Appledore22
Appledore22
Forum Access
3 posts
July 14, 2019 at 10:24 pm

In reply to chr_sue:

Thankyou so much it worked perfectly

gennaro
gennaro
Full Access
10 posts
February 06, 2020 at 11:30 am

In reply to chr_sue:

Hi,

I got into the same issue. The fix worked also in my case. I'm surprised that the handle of the virtual interface needs to be taken twice from the config db. The first time in the build phase, the second time in the connect_phase. Why?

Thank you for the help.

Fabio

chr_sue
chr_sue
Full Access
3850 posts
February 06, 2020 at 1:56 pm

In reply to gennaro:

I did not say you have to do this twice. he UVM is a phased approacg. Ther are special phases for doing certain things. The build_phase is used to construct all components in your testbench. It works top-down. The connect_phase is used to perform all connections, virtual connectiosn as well as the TLM connections. This works bottom-up.

gennaro
gennaro
Full Access
10 posts
February 07, 2020 at 9:12 am

In reply to chr_sue:

Thank you. It make sense.

Hope you have patience to help me/us to understand further. There're some students ramping up on UVM/system verilog, thus the topic is quite interesting from academycal perspective.

Apparently, the usage of connect phase seems to be strictly required, also when there's no specific top-down bottom-up requirement.

There's a simple design. There's one physical interface which is passed, through the config db at two components:
- test class
- virtual seqeuncer instantiated by the test class

initial 
     begin
        uvm_config_db#(virtual tb_sv2uvm_if)::set(uvm_root::get(),
                "*uvm_test_err_inj","tb_sv2uvm_if_vi",tb_sv2uvm_if);
        uvm_config_db#(virtual tb_sv2uvm_if)::set(uvm_root::get() , 
                "*m_uvm_tb_vseqr","m_tb_sv2uvm_if", tb_sv2uvm_if);	 
        run_test("uvm_test_err_inj");
     end

The test gets the handle in the build phase (currently, which is wrong but works).
The vsqr has to get the handle in the connect phase (otherwise there's the error message of this thread).

One analomaly: the error message is fired by vsim when the first signal of the interface is accessed. Such line belongs to the first sequence executed by the vsqr.

I would have expected the error to be fired in the build phase where we were doing

 if(!uvm_config_db#(virtual tb_sv2uvm_if)::get(this,"","m_tb_sv2uvm_if",m_tb_sv2uvm_if))
    `uvm_error("", "uvm_config_db::get - Failed")

In other words, why the get method works? Maybe the physical/virtual connection is done by vsim in the connect phase?

chr_sue
chr_sue
Full Access
3850 posts
February 07, 2020 at 10:40 am

In reply to gennaro:

A few remarks.
(1) All tarnsaction level components like sequencers, scoreboardsa, coverage collectors do NOT need any virtual interface. These components do never knwo anything about tieming and clock cycles, reset etc.
(2) When you are doing the connections at the end of the build_phase this will work, but it is a bad coding style because we have the connect_phase to implement the connections.

With respect to the usage of the uvm_config_db commands:
(1) for the set in the toplevel module use as the first argument 'null'. This is indicating the 2nd argument has to be considered as an absolute path
(2) for the get command commonly use as the first argument 'this'. This indicates the 2nd argument has to be considered as an absolute path.
Following these rules covers 95% of the uvm_config_db usage.
A different 1st argument you need whan you want to pass data to sequences, because they do not belong to the testbench topology.

Hope this helps to fix your issues.

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