VMM Users -- Welcome to the OVM!

VMM users -- welcome to the OVM!  We've been talking together about the benefits of the OVM -- ecosystem-drive business value and built-in ability to scale the technical solution -- for quite a while.  While thousands of verification engineers are already using it, many of you have said "Yes, I see the value, but what about my VMM legacy?" In the tradition of the OVM, Cadence (see press release here) has provided you with an open solution at OVMWorld.org!

Now that you have read the press release, you may have some questions.  Here are a few questions we've heard from customers during the past few months as we developed the migration package and a few that are likely to be on your mind as you read through all of the blogs and forum threads on this subject.

What is OVM adoption package and what does it provide for VMM users?

OVM adoption package is a library and methodology that allows users to use legacy VMM VIP components within an OVM testbench. That process does not give the VMM VIP the scalability and reuse of an OVC (OVM Verification Component), but it does allow the legacy VMM to be controlled by a system level OVM sequence, and supply data to other OVCs and VMM components in the testbench.

How does this open source release provide a proof-of-concept to the Accellera VIP TSC?

Cadence created this solution during the third quarter of 2008 based on customer and OVM ecosystem partner requests.  Those companies provided additional expert input and validation of our solution.  As a result, we were able to lead the definition of meaningful requirements in the Accellera VIP TSC (Technical SubCommittee).  The other active committee members worked on those requirements leading to the interoperability document accepted by the committee on Wednesday December 3. 2008.  The result is the open source and associated documentation released by Cadence on the OVMworld at http://www.ovmworld.org/contributions-details.php?id=24&keywords=VMM_to_OVM_migration_library.

Is this a proven migration path to OVM?

Yes.  The package was proven to work with VMM users with different application domains. The package was also reviewed, enhanced and approved by several independent sources intimately familiar with OVM and VMM.

What resources are available for Vera and VMM migration to the OVM?

In addition to the OVM Adoption package on the OVMWorld.org, there are several OVM ecosystem partners providing Vera and VMM migration services and Cadence is one of them.  We have people experienced with the process, some automation to help with the process, and several customers who have successfully made the transition.  For additional help and information contact your local account team or email support@cadence.com with the subject "Vera/VMM Migration to the OVM".

What is the relationship between the Cadence and Mentor announcements made the same day?

Each company has *many* customers wishing to move from VMM to the OVM while preserving some of their VIP investment, so each developed a solution independently. Though similar in spirit, there are some technical differences due to the needs of the respective customers.  In addition, the two companies continue to jointly develop and maintain the OVM with the next release of OVM – OVM 2.0.1 – expected to be available this month.

Why did Mentor and Cadence not converge on a single solution before release?

There is already an Accellera TSC with the charter to define interoperability between OVM and VMM, so setting up a parallel effort would not in the best interests of the industry. We decided that the most timely and effective way that we could contribute to Accellera was to make both solutions available immediately as open source "proofs of concept" and then work with the other TSC members on standardization.

So, VMM users, does this sound interesting?  What other questions do you have on your mind?  Comment here and we'll answer them or feel free to contact your Cadence support and/or account representatives.

=Adam Sherilog