Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
Get email delivery of the Cadence blog featured here
If you use or plan to use C language models for verification - be they SystemC, C, or C++ -- you will probably want to connect them to a SystemVerilog verification environment. How can this be done? A newly archived Cadence webinar has the answer - use the multi-language support capability that Cadence developed for the Universal Verification Methodology (UVM), available as an open-source contribution at http://www.uvmworld.org/.
The webinar is titled "Oceans of Expertise Connecting the UVM to Sea (C/C++/SC)." Presenters are Adam Sherer, product marketing director at Cadence, and Phu Huynh, verification architect at Cadence. Sherer is also secretary of the Accellera committee that's working on UVM.
First, a bit of background. UVM 1.0 and 1.1, as standardized by Accellera, describe a verification methodology for SystemVerilog. The Cadence UVM-ML (multi-language) donation extends UVM to the e language and SystemC (although this webinar was focused on SystemC). Sherer noted in the webinar that Accellera is not expected to consider a multi-language version of UVM until after the release of UVM 1.2 next year. So for now, what was discussed in the webinar is freely available but is not yet an Accellera standard.
Why Multiple Languages?
A system-on-chip (SoC) verification project today can be like the proverbial Tower of Babel. As shown at right, Verification IP (VIP) and universal verification components (UVCs) may exist in different languages, including SystemVerilog, e, SystemC, or C/C++. If you want to put all this together into a UVM style testbench, you need something that makes it possible to coordinate and synchronize those verification components.
Sherer took a quick poll at the start of the webinar and found that most attendees use the SystemVerilog Direct Programming Interface (DPI) to connect SystemC or C/C++ models to UVM. "DPI is good, but one of the problems is that you don't have any standard API to connect the SystemC or C++ components to UVM," Huynh said. "That is what we are trying to address with the multi-language UVM solution."
Huynh noted that there are some issues to be taken care of when integrating components from different language domains. These include synchronizing the execution and phases of components, communicating between the components, and providing some unified common utilities. To allow synchronization and communication, the UVM-ML capability uses the Open SystemC Initiative (OSCI) transaction-level modeling (TLM) standard. (Note: examples in this webinar were given in TLM 1.0, but Cadence is also developing a TLM 2.0 capability for UVM-ML).
Key TLM Terminology
In the webinar, Huynh reviewed some of the basic concepts behind the TLM interface. Important terms include "port" and "export" and "initiator" and "target." For example, when a consumer pulls items from a producer using a TLM "get" function, the consumer is the initiator (see below). Conversely, when a producer pushes items to a consumer using a "put" function, the producer is the initiator. The "port" is the component that initiates the TLM operation, and the "export" is the component that implements the TLM operation. (A questioner noted, and Huynh agreed, that this SystemC terminology is backwards from what some people would expect).
To make a connection, Huynh explained, the user "wraps" the C language model with a SystemC wrapper that provides the required TLM port and export. The synchronization of phases (such as end_of_elaboration and end_of_simulation) is handled automatically by the Cadence UVM-ML extensions. As Huynh noted several times, there are just three basic steps to connecting SystemC components into UVM:
Huynh showed an example in which a SystemC reference model for a packet router was brought into a UVM verification environment and integrated into a UVM testbench. He also showed multi-language debugging using the Cadence Incisive SimVision interface. You can see this example for yourself on the UVM World site.
In summary, I think the webinar did represent "oceans of expertise" that you can tap into in order to develop a multi-language capability with UVM. But Cadence has already handled a lot of the depth with its UVM-ML contribution. To access the archived webinar, click here.