Jump to content


  • Content Count

  • Joined

  • Last visited

  1. UVM1.0 attracted the attentions of many, and this was visible at the multiple sessions at DVCON. One of the features that is new to UVM is a partial implementation of TLM 2.0 (only SV to SV ports are supported). A few introductory sessions nicely covered the technical attributes of TLM2.0 standard. At the same time, many users came away confused from the sessions about the role of TLM2.0 in verification testbenches vs. modeling and what can be done today. I wrote a short technical blog to clarify the guidelines and Cadence position on this. Follow this link for the technical discussion: htt
  2. Hi Don, In a previous UVM forum post, Tom Alsop, the co-chair of Accellera VIP-TSC addresses your concern about the early adopter vs.. the 1.0 version (see http://www.uvmworld.org/forums/showthread.php?69-Backward-Compatibility-of-UVM-1.0-from-UVM-1.0EA). Currently, we are discussing in Accellera complementary capabilities that do not change the high-level methodology nor contradict the library tips in the book. The new features being considered for the 1.0 release are useful but incremental to the core methodology which is already in the 1.0 EA release. The book (that cost less than a $1
  3. 2,565 downloads

    This document introduces UVM compliance checks defined for UVM verification environments. The compliance checklist was requested by corporations and UVM users wishing to ensure consistency, similar user experience, and compliance to the official UVM SystemVerilog User Guide and concepts. Static commercial tools such as DVT allow forcing these checks on user environments The checks are divided into several categories: * Packaging and Name Space Compliance Checks * Architecture Compliance Checks * Reset and Clock Compliance Checks * Checking Compliance Checks * Sequences Compliance Che
  • Create New...