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

      • Functional Safety
      • Portable Test and Stimulus
      • Design & Verification Languages

    • Methodologies

      • Coverage
      • UVM - Universal Verification Methodology
      • FPGA Verification

    • Techniques & Tools

      • Acceleration
      • Formal-Based Techniques
      • Simulation-Based Techniques
      • Planning, Measurement, and Analysis
      • Verification IP
  • 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)

      • UVMF - One Bite at a Time
      • Introduction to UVM
      • Basic UVM
      • UVM Debug
      • Advanced UVM
      • UVM Connect

    • Featured Courses

      • Introduction to DO-254
      • Portable Stimulus Basics
      • SystemVerilog OOP for UVM Verification
      • Power Aware Verification
      • Power Aware CDC Verification
      • Assertion-Based Verification
      • Metrics in SoC Verification

    • Additional Courses

      • Clock-Domain Crossing Verification
      • An Introduction to Unit Testing with SVUnit
      • Evolving FPGA Verification Capabilities
      • 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 Coverage
      • Formal-Based Technology: Automatic Formal Solutions
      • 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
      • AMS Forum
      • 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 Horizon - 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.

    • Upcoming & Featured Events

      • Functional Verification Study - Oct. 10th
      • Getting Started with the SystemVerilog DPI - Oct. 12th
      • Optimizing Questa Performance - Oct. 25th
      • Practical "must have" Applications for SLEC - Fremont, Oct. 25th
      • Events Calendar

    • On Demand Seminars

      • Portable Simulus
      • Debug
      • Coverage
      • FPGA Verification
      • Stimulus Generation
      • UVM Forum
      • All On-Demand Seminars

    • Recording Archive

      • Portable Stimulus from IP to SoC
      • UVM 1800.2 & Updated UVM Cookbook
      • What Is Formal, And How It Works Under-the-Hood
      • DAC & DVCon
      • Silicon Valley Design & Verification IP Forum
      • Wilson Research Group
      • All Recordings

    • Mentor Training Center

      • SystemVerilog Assertions
      • SystemVerilog for Verification
      • SystemVerilog UVM
      • SystemVerilog UVM Advanced
      • Instructor-led Training

    • Mentor Learning Center

      • SystemVerilog Vectors and Arrays
      • SystemVerilog Advanced OOP
      • SystemVerilog Functional Coverage
      • UVM Transactions and Sequences
      • UVM Monitors and Agents
      • UVM Tests and Complex Sequences
      • Basic CDC Verification
      • Finite State Machine Viewer
      • Functional Verification Library
  • 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 Horizons Blog
      • Academy News
      • Technical Resources

    • Verification Horizons Publication

      • Verification Horizons - June 2018
      • Verification Horizons - March 2018
      • Verification Horizons - December 2017
      • Verification Horizons - June 2017
      • Verification Horizons - March 2017
      • Issue Archive

    • About Us

      • Verification Academy Overview
      • Subject Matter Experts
      • Contact Us

    • Training

      • Questa® & ModelSim®
      • SystemVerilog
      • Functional Verification Library
Ask a Question
UVM
  • Home /
  • Forums /
  • UVM /
  • Why are you recommending phase_ready_to_end(), when it has a limit of 20 calls?

Why are you recommending phase_ready_to_end(), when it has a limit of 20 calls?

UVM 4084
Cookbook: EndOfTest 1
dcblack56
dcblack56
Full Access
3 posts
August 19, 2014 at 7:09 pm

The UVM standard clearly states in the description of phase_ready_to_end() that "To prevent endless iterations due to coding error, after 20 iterations, phase_ended() is called regardless of whether previous iteration had any objections raised." Examination of the UVM implementation indicates this limit does exist.

If a transactor used this mechanism to extend a phase, then only 20 transactions would be allowed.

Replies

Log In to Reply
tfitz
tfitz
Forum Moderator
414 posts
January 05, 2015 at 7:47 am

The whole point of phase_ready_to_end() is to allow the "last transaction" to be processed before exiting the phase. It is not unreasonable to expect that users have enough knowledge of the system to be able to ensure that this be done with less than 20 calls. Objections should only be raised when necessary. Raise an objection in the test before starting your sequence(s) and drop from the test when the sequence(s) is(/are) complete. Usually the sequence(s) won't complete until the driver has completely processed the last transaction (including sending back a response via put_response() or item_done()), so the driver doesn't usually need phase_ready_to_end(). The monitor recognizes the same transaction and calls write(), which is a function, so it doesn't usually need phase_ready_to_end() either. The most common application has the scoreboard doing some kind of analysis to the last transaction that may include some time-consuming behavior, so it's usually the scoreboard that implements phase_ready_to_end().
Perhaps you could provide more of an explanation to justify why you think you need more than 20 calls to phase_ready_to_end(). If you really need that many, you could modify your copy of UVM and increase the number.

dcblack56
dcblack56
Full Access
3 posts
January 05, 2015 at 8:26 am

In reply to tfitz:

I agree with your approach.

My concern is that a number of folks I have talked with considered the use model for phase_ready_to_end() differently. Instead, they considered it as a way to avoid objections. In other words, just extend on-the-fly. I don't think this approach is viable.

Perhaps documentation should be more explicit about the use case for this feature.

Other things to consider:
Any time you fork join-none a sequence, it needs to decide if it cares about extending the phase.
What about drivers waiting on multiple outstanding responses (e.g. ethernet packets)?

I'm not saying that the limit of 20 is wrong. I am simply saying that using phase_read_to_end() needs to be qualified with that understanding.

Nico75
Nico75
Full Access
163 posts
October 21, 2016 at 2:27 am

When using this method only to get the last in flight transaction, we need just 1 call per scoreboard. But what if you have more than 20 scoreboards? When doing vertical reuse, we would easily get to more than 20.

Is this so uncommon?

© Mentor, a Siemens Business, All rights reserved www.mentor.com

Footer Menu

  • Sitemap
  • Terms & Conditions
  • Verification Horizons Blog
  • LinkedIn Group
SiteLock