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
  • Driver data not getting propagated to the DUT

Driver data not getting propagated to the DUT

UVM 6661
UVM Driver 14 UVM-DUT connection 2
Coppola
Coppola
Full Access
7 posts
May 04, 2020 at 6:49 pm

I wrote this code for "Introducing Transactions" class under Basic UVM course.

I am sending some sample address, command, and data from the driver. However, DUT is not
receiving the data. I pasted most relevant SV files in my TB at the top. Please help me point to the error.

Here is the output
UVM_INFO @ 0: reporter [RNTST] Running test my_test...
$time = 105, addr = 0, data = 0, cmd = x

UVM_INFO @ 200: reporter [TEST_DONE] 'run' phase is ready to proceed to the 'extract' phase
UVM_INFO @ 200: reporter [UVM/REPORT/CATCHER]

Here is the Code base

DUT Interface ---> dut_if.sv

interface dut_if;
 
logic clock, reset;
logic cmd;
int data, addr;
 
endinterface

DUT Config File

class dut_config extends uvm_object;
 
`uvm_object_utils(dut_config)
 
function new(string name = "dut_config");
 
endfunction
 
virtual dut_if dut_vif;
 
endclass

DUT module ---> dut_module.sv

module dut(dut_if _if);
 
initial begin
    _if.clock = 0;
 
    #5 _if.clock = ~_if.clock;
 
    #100 $display("$time = %d, addr = %d, data = %d, cmd = %d \n", $time, _if.addr, _if.data, _if.cmd); 
end
 
always@(_if.data or _if.cmd or _if.addr) begin
    $display("$time = %d, addr = %d, data = %d, cmd = %d \n", $time, _if.addr, _if.data, _if.cmd);    
 
end
 
endmodule : dut

Driver --> my_driver.svh

class my_driver extends uvm_driver#(my_transaction);
 
`uvm_component_utils(my_driver)
 
  dut_config dut_config_0;
 
//virtual interface dut_if dut_vif;
 
function new(string name, uvm_component parent);
    super.new(name, parent);
endfunction
 
function void build_phase(uvm_phase phase);
    super.build_phase(phase);
endfunction
 
function void connect_phase(uvm_phase phase);
 
    if(!uvm_config_db#(dut_config)::get(this, "", "dut_config", dut_config_0))
        `uvm_fatal(get_type_name(), "Could not instantiate dut_config in my_driver")
endfunction
 
 
task run_phase(uvm_phase phase);
    my_transaction tx;
    @(posedge dut_config_0.dut_vif.clock);
    seq_item_port.get_next_item(tx);
 
    dut_config_0.dut_vif.addr = tx.addr;
    dut_config_0.dut_vif.cmd= tx.cmd;
    dut_config_0.dut_vif.data = tx.data;
       @(posedge dut_config_0.dut_vif.clock);
 
    seq_item_port.item_done();
 
endtask
endclass

Top Module --> top.sv

module top; 
 
import uvm_pkg::*;
import my_pkg::*;
 
dut_if dut_if1();
 
dut dut_inst(._if(dut_if1));
 
initial 
begin
    uvm_config_db#(virtual dut_if)::set(null, "uvm_test_top", "dut_vif", dut_if1);
    run_test("my_test");
end
 
endmodule : top

Top level Test ---> my_test.svh

class my_test extends uvm_test;
 
`uvm_component_utils(my_test)
 
 my_env my_env_h;
 dut_config dut_config_0;
 
 function new(string name, uvm_component parent);
    super.new(name, parent);
 
    my_env_h = my_env::type_id::create("my_env_h", this);
 
 endfunction
 
 function void build_phase(uvm_phase phase);
    super.build_phase(phase);
 
     dut_config_0  = new();
 
    if(!uvm_config_db#(virtual dut_if)::get(this, "", "dut_vif", dut_config_0.dut_vif))
        `uvm_fatal(get_type_name(), "dut_if has not been instantiated")
 
    uvm_config_db#(dut_config)::set(this, "*", "dut_config", dut_config_0);
 endfunction
 
task run_phase(uvm_phase phase);
    phase.raise_objection(this);
 
    #200;
    phase.drop_objection(this);
 
 
 
endtask
 
endclass : my_test

Env File --> my_env.svh

class my_env extends uvm_env;
 
`uvm_component_utils(my_env)
 
my_agent my_agent_h;
 
function new(string name, uvm_component parent);
    super.new(name, parent);
endfunction
 
function void build_phase(uvm_phase phase);
    super.build_phase(phase);
    my_agent_h = my_agent::type_id::create("my_agent_h", this);
endfunction
 
task run_phase(uvm_phase phase);
 
endtask 
 
endclass : my_env

Agent --> my_agent.svh

class my_agent extends uvm_agent;
 
    `uvm_component_utils(my_agent)
 
 
    my_driver my_driver_h;
    my_sequencer my_sequencer_h;
    my_monitor my_monitor_h;
 
    function new(string name, uvm_component parent);
        super.new(name, parent);
    endfunction
 
    function void build_phase(uvm_phase phase);
        super.build_phase(phase);
 
        if(is_active == UVM_ACTIVE) begin
            my_driver_h = my_driver::type_id::create("my_driver_h", this);
            my_sequencer_h = my_sequencer::type_id::create("my_sequencer_h", this);
        end
 
        my_monitor_h = my_monitor::type_id::create("my_monitor_h", this);
    endfunction
 
   function void connect_phase(uvm_phase phase);
       if(is_active == UVM_ACTIVE)
            my_driver_h.seq_item_port.connect(my_sequencer_h.seq_item_export);
   endfunction
 endclass

Sequence ---> my_sequence.svh

class my_sequence extends uvm_sequence#(my_transaction);
 
`uvm_object_utils(my_sequence)    
 
function new(string name = "");
    super.new(name);    
endfunction
 
task body();
    forever begin
       my_transaction tx = my_transaction::type_id::create("tx");
 
       start_item(tx);
       if(!tx.randomize()) 
           `uvm_fatal(get_type_name(), "Randomization of my_transaction instance failed")
 
       finish_item(tx); 
    end    
endtask
 
endclass

Sequence Item

class my_transaction extends uvm_sequence_item;
 
  `uvm_object_utils(my_transaction)
 
   rand bit cmd;
    rand int addr;
    rand int data;
 
   function new(string name = "");
    super.new(name);    
   endfunction
 
   constraint c_addr {addr >= 0; addr <256;}
 
   constraint c_data {addr >= 0; addr <256;}
endclass

typedef uvm_sequencer #(my_transaction) my_sequencer;

Replies

Log In to Reply
chr_sue
chr_sue
Full Access
3846 posts
May 04, 2020 at 11:06 pm

In reply to Coppola:

Would be great if you could put your example to EDAPlayground (edaplayground.com) to have an executable piece of code.
Only a few remarks:
(1) in your DUT you have your clock generator, but you generating only 1 edge.
(2) In the constructor of your config bals the constructor call to the base class is missimng. It should be

class dut_config extends uvm_object;
`uvm_object_utils(dut_config) 
function new(string name = "dut_config");
  super.new(name);
endfunction 
virtual dut_if dut_vif;
endclass
Coppola
Coppola
Full Access
7 posts
May 04, 2020 at 11:22 pm

In reply to chr_sue:

Thanks. I was indeed missing the clock. However, even after calling base class constructor and giving clock edges, i am not seeing change in my addr, data, and cmd.

I understand my code might be too cumbersome. Will explore using EDAPlayground .

Thx!!!

UVM_INFO @ 0: reporter [RNTST] Running test my_test...
$time = 5, addr = 0, data = 0, cmd = x

$time = 10, addr = 0, data = 0, cmd = x

$time = 15, addr = 0, data = 0, cmd = x

$time = 20, addr = 0, data = 0, cmd = x

$time = 25, addr = 0, data = 0, cmd = x

$time = 30, addr = 0, data = 0, cmd = x

Solution

Solution

dave_59
dave_59
Forum Moderator
10661 posts
May 04, 2020 at 11:31 pm

In reply to Coppola:

Also, you never start your sequence

— Dave Rich, Verification Architect, Siemens EDA

chr_sue
chr_sue
Full Access
3846 posts
May 04, 2020 at 11:35 pm

In reply to Coppola:

Quote:
In reply to chr_sue:

Thanks. I was indeed missing the clock. However, even after calling base class constructor and giving clock edges, i am not seeing change in my addr, data, and cmd.

I understand my code might be too cumbersome. Will explore using EDAPlayground .

Thx!!!

UVM_INFO @ 0: reporter [RNTST] Running test my_test...
$time = 5, addr = 0, data = 0, cmd = x

$time = 10, addr = 0, data = 0, cmd = x

$time = 15, addr = 0, data = 0, cmd = x

$time = 20, addr = 0, data = 0, cmd = x

$time = 25, addr = 0, data = 0, cmd = x

$time = 30, addr = 0, data = 0, cmd = x

The data you see are the initial values of your class memebers. As Dave says you do not start the sequence. You should do this in your test.

Coppola
Coppola
Full Access
7 posts
May 05, 2020 at 10:33 am

In reply to chr_sue:

Thanks for the prompt replies. Once i started sequence in the test, i see the transaction flowing from driver to DUT.

task run_phase(uvm_phase phase);
    my_sequence seq;
    seq = my_sequence::type_id::create("seq");
 
    phase.raise_objection(this);
---
    seq.start(my_env_h.my_agent_h.my_sequencer_h);
 
    #200;
 
    phase.drop_objection(this);
----
----
 
endtask
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