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

      • Exploring Formal Coverage
      • Processor Customization
      • 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 - July 2023
      • Verification Horizons - March 2023
      • Verification Horizons - December 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 driver sequencer interaction with parameterized sequence item

UVM driver sequencer interaction with parameterized sequence item

UVM 6935
uvm driver sequencer... 1
Brass
Brass
Full Access
12 posts
May 17, 2023 at 12:40 am

I have a sequence item of the type :

class seq_item#(int PARAM_NAME) extends uvm_sequence_item;
`uvm_object_param_utils(seq_item#(PARAM_NAME))

The sequence item is created in the sequence as:

m_seq_item = seq_item#(PARAM_NAME):: type_id::create("name")

In the agent, the sequencer is declared and created as:

uvm_sequencer#(seq_item#(PARAM_NAME)))   m_sqr;
...
m_sqr = uvm_sequencer#(seq_item#(PARAM_NAME))::type_id::create("name", this);

The driver class definition is
class driver#(int PARAM_NAME) extends uvm_driver #(seq_item#(PARAM_NAME))

The driving loop is : 

forever begin
  seq_item_port.get_next_item(req);
 
  do_transaction(); 
  // please note that the transaction is visible on the bus
 
  seq_item_port.item_done();
  $cast(rsp,req);
  rsp.set_id_info(req);
  seq_item_port.put_response(rsp)
end

LE:

typedef parameterized_sequence_with_very_long_name#(PARAM_NAME) my_sequence_type;
class my_test extends uvm_test;
  my_sequence_type m_seq;
...
  function void build_phase(uvm_phase phase);
    super.build_phase(phase)
    m_seq = my_sequence_type::type_id::create("name")
  endfunction
...
endclass

class parameterized_sequence_with_very_long_name#(PARAM_NAME) extends uvm_sequence;

I get a runtime fatal from the sequencer :
UVM_FATAL : <..> [PUTRSP] Failure to cast response in put_response.

Please support to find what I'm doing wrong.

Thank you

Replies

Log In to Reply
cgales
cgales
Forum Moderator
2094 posts
May 17, 2023 at 4:54 am

In reply to Brass:

Without an actual testcase, it's difficult to provide accurate feedback.

However, you shouldn't cast the req to rsp. You should clone() req and cast that to rsp to ensure that the original req won't be reused. I would also call item_done() after the response is created just to ensure that req hasn't been changed at some point outside of this task.

forever begin
  seq_item_port.get_next_item(req);
 
  do_transaction(); 
  // please note that the transaction is visible on the bus
 
  $cast(rsp,req.clone());
  rsp.set_id_info(req);
  seq_item_port.put_response(rsp)
  seq_item_port.item_done();
end
chr_sue
chr_sue
Full Access
3991 posts
May 17, 2023 at 5:54 am

In reply to Brass:

How did you construct the rsp?

Brass
Brass
Full Access
12 posts
May 17, 2023 at 8:20 pm

In reply to chr_sue:
Hi chr_sue

good question: I also used the PARAM_NAME

rsp = seq_item#(PARAM_NAME)::type_id::create("rsp",this);

Brass
Brass
Full Access
12 posts
May 17, 2023 at 8:23 pm

In reply to cgales:

Hi cgales

and thank you for your answer.

I keyed in your suggestion but the result is the same.

chr_sue
chr_sue
Full Access
3991 posts
May 17, 2023 at 9:54 pm

In reply to Brass:

You can pass the rsp also using item_done like this

  $cast(rsp,req.clone());
  rsp.set_id_info(req);
  seq_item_port.item_done(rsp);

Because we do not see the whole story it is not easy to give you the right advice.
It is more guessing what we can do.

Brass
Brass
Full Access
12 posts
May 18, 2023 at 2:01 am

In reply to chr_sue:

Thank you for your suggestion . Unfortunately it doesn't work either in my case.

The example is based on production code, so I was hoping for more of a theoretical approach, since I haven't seen any documentation/online resource for this particular case.

chrisspear
chrisspear
Full Access
119 posts
May 19, 2023 at 7:47 am

In reply to Brass:

You left out the declaration of the sequence.

The code in uvm_sequence::put_response() is trying to $cast() between a uvm_sequence_item handle and the RSP type from your sequence declaration. Did you give a different RSP type than then REQ type?

Brass
Brass
Full Access
12 posts
May 21, 2023 at 9:48 pm

In reply to chrisspear:

Hi chrisspear

and thank you for your reply.
My driver is defined as :

class driver#(int PARAM_NAME) extends uvm_driver #(seq_item#(PARAM_NAME))

As per uvm_driver class definition, the rsp type is implicitly the same as the req type:
class uvm_driver #(type REQ=uvm_sequence_item,type RSP=REQ) extends uvm_component;

I have,however, tried to create the rsp type explicitly inside the driver, as per your suggestion and also to declare the driver class as :
class driver#(int PARAM_NAME) extends uvm_driver #(seq_item#(PARAM_NAME), seq_item#(PARAM_NAME))

with no change in the outcome.

ABD_91
ABD_91
Forum Access
198 posts
May 22, 2023 at 3:20 am

In reply to Brass:

Quote:

The sequence item is created in the sequence as:
m_seq_item = seq_item#(PARAM_NAME):: type_id::create("name")

Could you share code for the sequence class specialization in the test i.e handle declaration of the sequence in the test using which you call task start

Solution

Solution

chrisspear
chrisspear
Full Access
119 posts
May 22, 2023 at 6:36 am

In reply to ABD_91:

Here is a working example with a parameterized sequence item. You can try to work forward from this to your situation.

Brass
Brass
Full Access
12 posts
May 22, 2023 at 8:10 pm

In reply to ABD_91:
Hi ABD_91 and thank you

typedef parameterized_sequence_with_very_long_name#(PARAM_NAME) my_sequence_type;
class my_test extends uvm_test;
  my_sequence_type m_seq;
...
  function void build_phase(uvm_phase phase);
    super.build_phase(phase)
    m_seq = my_sequence_type::type_id::create("name")
  endfunction
...
endclass

class parameterized_sequence_with_very_long_name#(PARAM_NAME) extends uvm_sequence;

Also added to the initial post. thanks

Brass
Brass
Full Access
12 posts
May 22, 2023 at 8:38 pm

In reply to chrisspear:

Hi chrispear

and thank you

it seems my sequece paramter list was void :

class parameterized_sequence_with_very_long_name#(PARAM_NAME) extends uvm_sequence#();

instead of

class parameterized_sequence_with_very_long_name#(PARAM_NAME) extends uvm_sequence#(PARAM_NAME);

Thank you all for contributing to solve this

chr_sue
chr_sue
Full Access
3991 posts
May 23, 2023 at 2:15 am

In reply to Brass:

I cannot agree. I modified the code example from chrisspear wrt to the sequence definition to
class tx_sequence extends uvm_sequence;
It works also, but it should fail because this sequence has to produce seq_items.

chrisspear
chrisspear
Full Access
119 posts
May 23, 2023 at 4:36 am

In reply to chr_sue:

If you don't specialize the uvm_sequence on line 22, then req is just uvm_sequence_item and you will get an elaboration error on line 33 for the req.data reference. You must have:class tx_sequence extends uvm_sequence #(tx_item(P));

chr_sue
chr_sue
Full Access
3991 posts
May 23, 2023 at 5:59 am

In reply to chrisspear:

This is exactly what I was expecting. But Questa-2022.4 is tolerting this.
It's strange I know, but it is as it is.

chrisspear
chrisspear
Full Access
119 posts
May 24, 2023 at 7:59 am

In reply to chr_sue:

You must seeing be a disturbance in the matrix. I just tried Questa 2022.4_2 and it correctly gave an elaboration error for req.data and rsp.data, when uvm_sequence uses the default specialization uvm_sequence_item.

chr_sue
chr_sue
Full Access
3991 posts
May 24, 2023 at 8:16 am

In reply to chrisspear:

The `uvm_info are only needed for displaying some information. If you are removing them it works in my environment.

chrisspear
chrisspear
Full Access
119 posts
May 24, 2023 at 8:28 am

In reply to chr_sue:

Of course. You removed the two references to tx_item members, data. Everything else is uvm_sequence_item members.

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