TDEB Top Bar

Trending
Semiconductor Industry News — The Digital Electronics Blog
Follow Us

TDEB Masthead

The Semiconductor Hub

Semiconductors.  Chips and Systems.  Innovation.

Indexed by leading Search Engines, AI and referenced by Engineers worldwide 500+ Articles 10M+ Pageviews 30+ Reports 50+ Citations

Questa SV/AFV Compatibility Matrix with OVM, QVL and 0-In

mg
by
0
Share Facebook X LinkedIn WhatsApp Email

In February 2010 this post pointed to a compatibility matrix that Mentor Graphics kept on its SupportNet site (SupportNet access needed). The matrix illustrated the version compatibility between Questa SV/AFV and different versions of OVM, the Questa MVC library, QVL, 0-In and Questa ADMS. That technote is no longer online and has no public archive copy, so the original link has been removed.

What the matrix was for

A verification flow is rarely one tool. In 2010 a typical Mentor-based flow combined a simulator (Questa SV/AFV), a methodology library (OVM, written in SystemVerilog), verification IP (the Questa MVC library of protocol models), an assertion checker library (QVL), formal and clock-domain tools (0-In) and, for mixed-signal chips, Questa ADMS. Each of these had its own release cycle. A new simulator release might need a newer OVM, or a verification IP release might only have been tested against certain simulator versions.

The matrix answered one practical question: if I upgrade one piece, which versions of the others am I allowed to use? Getting that wrong shows up as compile errors, or worse, as subtle behavior changes in a regression that used to pass.

Why version compatibility matters

  • Reproducible regressions. A sign-off regression must be re-runnable months later with the same result. That means every tool and library version is recorded and pinned.
  • Library and simulator coupling. Methodology libraries such as OVM and its successor UVM use advanced SystemVerilog features. Simulator support for those features changed between releases, so a library release was tested against particular simulator versions.
  • Verification IP. Protocol models are often delivered compiled or encrypted, so they are tied to specific simulator releases.

What happened next

Within weeks of this post, the methodology side of the matrix began to change. On January 8, 2010, Accellera announced it would adopt OVM as the basis of its Universal Verification Methodology, as recounted in Siemens EDA's "UVM: The Next IEEE Standard (1800.2)" (Dennis Brophy, July 30, 2015). The same article traces the history: Mentor's AVM was first announced on May 8, 2006, and Mentor and Cadence announced their collaboration on OVM on August 16, 2007.

Accellera's UVM download page lists UVM 1.0 in February 2011. UVM later became an IEEE standard: Accellera announced on April 11, 2017 that the IEEE 1800.2 standard for UVM had been approved, with the standard offered free through the IEEE GET Program.

On the tool side, Mentor became part of Siemens, and its simulator line is now sold as Questa One Sim. Compatibility and release information for current versions is on the Siemens Support Center, which needs a customer login.

Deep dive: the numbers and details

This part lists the UVM release history and shows how to pin versions in practice. Skip it if the overview is all you need.

UVM releases on Accellera's download page

ReleaseDate listed
UVM 1.0February 2011
UVM 1.1June 2011
UVM 1.1a to 1.1dDecember 2011 to March 2013
UVM 1.2June 2014
UVM 2017-1.0 (aligned with IEEE 1800.2-2017)November 2018
UVM 2020-1.0December 2020
UVM 2020-3.2 (current at the time of writing)August 2026

That is more than a dozen library releases in 15 years, each of which a team may have to qualify against its simulator and verification IP.

How to read a compatibility matrix

Most matrices have tool releases on one axis and library or IP releases on the other, with each cell marked tested, supported or not supported. Three habits help:

  1. Find your simulator release first, then read across for every library you use. The usable combination is the intersection, not the newest of each.
  2. Treat "supported but not tested" as a risk to cover with your own regression.
  3. Check the minimum version as well as the maximum. Some libraries drop support for old simulators.

Pinning versions in a project

Record every version in one place under revision control, and make the run scripts read from it. A minimal example:

# tools.cfg: one line per tool or library, read by every run script
SIMULATOR      questa   x.y
METHODOLOGY    ovm      x.y
VIP            mvc      (release from the vendor matrix)
ASSERT_LIB     qvl      (release from the vendor matrix)

The version numbers above are placeholders to show the format, not a tested combination. When you upgrade, change one line at a time and rerun the full regression, so any change in results can be traced to one upgrade.

Interview angle

A common question for verification roles is how you would migrate an OVM testbench to UVM. A good answer covers the mechanical renaming of ovm_ prefixes to uvm_, the phase and objection changes, and the plan to run both old and new benches on the same tests until results match.

Share Facebook X LinkedIn WhatsApp Email

Post a Comment

0 Comments

Your comments will be moderated before it appears here.

Post a Comment (0)

#buttons=(Ok, Go it!) #days=(20)

Our website uses cookies to enhance your experience. Learn more
Ok, Go it!