Cadence.com will be under maintenance from Friday, Oct. 3rd at 6pm (PST) thru Sunday, Oct 5th at 11pm (PST).
Cadence.com login, registration, community posting and commenting functionalities will be disabled.
Home > Community > Blogs > Functional Verification > introducing uvm multi language open architecture
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more convenient.

Register | Membership benefits
Get email delivery of the Functional Verification blog (individual posts).
 

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Introducing UVM Multi-Language Open Architecture

Comments(0)Filed under: DAC, SystemVerilog, SystemC, e, verification, Incisive, uvm, UVM ML, UVMWorld, SoCs, AMD, UVM Multi-Language

The new  UVM Multi-Language (ML) Open Architecture (OA) posted to the new UVMWorld is the result of a collaboration between Cadence and AMD.  It uniquely integrates e, SystemVerilog, SystemC, C/C+, and other languages into a cohesive verification hierarchy and runs on multiple simulators.  Moreover, the new solution is open for additional collaboration and technology enhancement. 

Since Cadence introduced ML verification four years ago, the need for it has never been greater.  Complex SoCs are verified with a combination of industry-standard languages and frameworks including IEEE 1647 (e), 1800 (SystemVerilog), 1666 (SystemC), and Accellera UVM, as well as C/C++, VMM, Perl, and others.  The previous ML solution enabled the standard connections but had some limitations.  Among the limitations included are a focus on “quick-stitch” integration that allowed for data communication but required significant additional coding to synchronize the communication. In addition, the solution was built primarily for the Incisive Enterprise Simulator.

Bryan Sniderman, Verification Architect for AMD, introduces the requirements that drove the development, the limitations in existing solutions, and the features you can expect in this UVM ML OA video.  In the video, Bryan describes how the new solution enables hierarchical integration of the frameworks, seamless phasing, seamless configuration, and has the ability to run on multiple simulators.

You can also learn more about the solution in our webinar, “Introducing UVM Multi-Language Open Architecture,” archived on Cadence.com. If you are at DAC, stop by the Cadence Theater on Wednesday at 4:30pm to hear Mike Stellfox present the solution and take part in our Q/A that will follow.  Of course, you can also stop by the booth to learn more as well or send an email to support_uvm_ml@cadence.com if you have any questions.  Finally, note that you will need to register in the Accellera Forums to download the UVM ML OA and that registration is open to all.

Think of the UVM ML OA as a new beginning.  As you read through and watch the background materials, you’ll probably see a mix of exciting new features and opportunities to further improve the solution.  We welcome that input.  The solution you see here represents a solid foundation, but there is more that we can do and we are happy to expand the collaboration to bring in those new ideas.

 

=Adam Sherer on behalf of the AMD and Cadence collaboration

 

 

Comments(0)

Leave a Comment


Name
E-mail (will not be published)
Comment
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.