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
  • filter uvm_info statements in the monitor by interface

filter uvm_info statements in the monitor by interface

UVM 6659
uvm_info 13 virtual interface 8
Phill_Ferg
Phill_Ferg
Full Access
69 posts
June 08, 2014 at 4:29 am

I am in the situation were i have a significant amount of interfaces (+60) of the same type.

I would like to see the output of specific monitors. Now i have plenty of UVM debug statements in my monitors, but with lots of monitors this is very difficult to filter.
At the moment i have added the virtual interface handle to the uvm_info calls (see below) and then i will grep my log files

	`uvm_info("MONITOR", $sformatf("[%p]WR Data %0d of %0d ", vif,capture_count,collected_transfer.burstLen), UVM_HIGH)

Can anyone advise a better way of doing this? I wish i could shorten the vif because the hierarchy looks awful in the log files.

Thanks

Replies

Log In to Reply
Vinay Jain
Vinay Jain
Full Access
83 posts
June 08, 2014 at 7:04 am

In reply to Phill_Ferg:

Hi Phill,

Best Way is to filter UVM Message is to have unique Message ID.

you could try such implementation
`uvm_info("MONITOR:Filtername", $sformatf("[%p]WR Data %0d of %0d ", vif,capture_count,collected_transfer.burstLen), UVM_HIGH)

you will get "[MONITOR:Filtername]" this pattern in log and then its easy to grep for this id. I hope this is what you are looking for.

Regards,
Vinay Jain

Phill_Ferg
Phill_Ferg
Full Access
69 posts
June 08, 2014 at 11:41 pm

In reply to Vinay Jain:

Vinay,

thanks for the response, i understand what you mean. However when i write the code i won't know what i want to filter.
All i know is that i would like to look at the uvm_info statements from a particular monitor instance, when i see things going wrong in the scoreboard.

How do i trace this instance and put it in my uvm_info statements? I am needing something unique per instance , a number or an interface.

I remember noticing an agent id field in template code - but never paid any attention to this - perhaps i should be look for fields inherited from uvm_monitor.

kavin
kavin
Full Access
7 posts
June 08, 2014 at 11:57 pm

In reply to Phill_Ferg:

Hi Phil,
How about assigning a unique string for each monitor from environment and add that string variable in info .

Phill_Ferg
Phill_Ferg
Full Access
69 posts
June 09, 2014 at 3:47 am

In reply to kavin:

Thanks kavin, i've kind of done this, but using the vif instead of a unique id. It is a lot more useful, but is a bit verbose on the transcript window.
I was hoping that there was an in-built uvm_compoment field that might help here.

Sadly my agents only have scope of their configuration, so i guess i could put in a associative array along with the vifs, but this just seems overkill

tfitz
tfitz
Forum Moderator
467 posts
June 09, 2014 at 7:40 am

You could make the ID field of the monitor based on the name or full_name of the monitor and filter on that. That's kind of what the ID field was intended for.

Phill_Ferg
Phill_Ferg
Full Access
69 posts
June 09, 2014 at 7:57 am

In reply to tfitz:

Am i right in saying the ID field is a user defined field, so i would have to populate it from the the agent?

At present i have a testbench level config that pulls the virtual interface from the config_db. This then creates uvc based configs and passes the vif handles down. At some stage i will specific how many agents of a particular type i have and align them to a vif. At this stage i have an "id" that i can pass to the monitor.
I am happy with this approach, but i just wanted to make sure i wasn't missing anything embedded in uvm_component that may help me in the same way.

I like neat transcript windows and greping on "MONITOR.*[/top/interface_name]" is not pleasant, "MONITOR.*[vif0] would be lovely.

tfitz
tfitz
Forum Moderator
467 posts
June 09, 2014 at 8:21 am

In reply to Phill_Ferg:

The ID field is user-defined. It doesn't need to be populated from the agent. It's just a string, so you could define it inside the agent. You'd probably want to define it once up-front (like in build_phase() or end_of_elaboration_phase()), and you can base it off either the monitor's name/full_name, or any other information you may get from the config_db. You could easily write a function that returns the "vif0" part of the interface name and use that.

kavin
kavin
Full Access
7 posts
June 09, 2014 at 8:41 am

In reply to Phill_Ferg:

Hello Phill ,
why would a string variable in monitor would affect anything(i meant your configs). In environment either build phase or connect phase make monitor IDs(string value for each monitor instance), since you are naming it , greping also will be easy .

This is what tfitz idea too .

Phill_Ferg
Phill_Ferg
Full Access
69 posts
June 09, 2014 at 8:54 am

In reply to kavin:

Kavin

I agree - my initial point was to check i wasn't missing anything obvious.

My configs at the UVC level contain the number of agents, their configs which include the vif to assign to a particular agent.
There are a few options:

1) write an ID fields in the monitor from the agent based on the virtual interface name of array location.
2) write a function in the monitor to parse extract the virtual interface name.

I'll probably go with point one to keep the code simple.

Thanks

Phill_Ferg
Phill_Ferg
Full Access
69 posts
June 09, 2014 at 8:56 am

In reply to tfitz:

Thanks Tom,

as mentioned above:

My configs at the UVC level contain the number of agents, an array of their configs which include the vif to assign to a particular agent.

I am most likely to write the ID field in the monitor from the agent based on the array index which holds the config for that particular agent.

Thanks :)

tfitz
tfitz
Forum Moderator
467 posts
June 09, 2014 at 10:27 am

In reply to Phill_Ferg:

However you are getting the information into the monitor is fine. We recommend using a configuration object to hold all information for a particular component so you only have to do one config_db::set/get per component. As you pass in the specific vif instance in the config object, you can also include a separate field that holds the ID key. Then, you can make your monitor's ID something like {"MONITOR", config_obj.key} where 'key' could either be a string set by the agent or an int which you convert to a string via $sformat.

Phill_Ferg
Phill_Ferg
Full Access
69 posts
June 10, 2014 at 12:59 am

In reply to tfitz:

Thanks Tom, i have configs for each agent so its an easy change to set id's now in configs.
I am really enjoying this aspect of SystemVerilog/UVM - as the complexity increases there is always something new to discover in the methodology and capability in the language

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