Talk about stability -- OVM 2.1.1 has had 18 months as the core of Accellera's UVM and accumulated only 13 bugs. Not too shabby! With the OVM community preparing to migrate, Cadence and Mentor have posted a bug-fix update -- OVM 2.1.2 -- to OVMWorld to help you get ready to move to the UVM.
As you may have seen in my twitter feed, I've been out talking to customers a lot lately. Both OVM and VMM users have been telling me they are really happy that UVM is here and are preparing to migrate. On the OVM side, we've heard consistently "we are preparing to migrate at the end of this project, but it would be really good if the official OVM release could be updated one last time to support our legacy code." Mentor and Cadence have heard that and we provided that update as OVM 2.1.2.
When you look at the release notes you'll see the 10 bugs that were fixed and the 3 small API changes. There are no new features in OVM -- all of our engineering work is focused on UVM. In fact, the changes to OVM are more or less back-ports from the work done on UVM. Bottom line -- think of this bug-fix release as the safety net that enables you to move to the UVM with confidence!
Looking for another point of confidence? Come listen to Larry Ching of Boeing present his experiences migrating from OVM to UVM at the Accellera breakfast and again in the Cadence Theater at DAC on Tuesday June 7th.
I guess at some point I should probably comment on my own blog, :-) but let me just add to the latest comment.
Dennis did put it well echoing the "get ready to migrate to the UVM" message in this blog. However, I see the register package on UVM as one of those biggest motivations to migrate. Let's look at the two conditions in which the register package would affect your decision -- you are either not working with a register package on OVM already or you are but it's not the UVM one. ('cuz Mentor just integrated it!)
If you haven't already implemented a register package, its a big methodology advance. If you are going to make that deep investment, it probably makes the most sense to take the tiny step and run the UVM migration script to become fully immersed in the future rather than being bound to the past.
If you are already using either the Mentor or Cadence packages (or your own), I would agree that you can use a product like Duolog's Socrates to re-target your register descriptions relatively easily. However, you still need to fully re-validate your entire regression environment to be sure the migration was successful and that will take some time. Why not run that tiny UVM migration script and be fully in the methodology of the future?
I'm sure Mentor has a reliable implementation and you will make the right choice for your project's needs. However, the simple risk-analysis above indicates that if you are ready for a methodology change as big as adopting a new register package, then moving fully to the UVM is the lowest risk decision.
Back to Adam's message about OVM 2.1.2 getting one ready for UVM, it has also opened the OVM world of users to some of the new and compelling UVM features, like the UVM Register package.
In keeping with "tomacadence's" definition of open-source, the UVM 1.1 Register package for OVM 2.1.2 can be found on OVMWorld.org (http://bit.ly/m426gv) that allows an OVM 2.1.2 user to use UVM Register package code now.
I think this will help accelerate the OVM migration towards UVM by immediately binding them to one of the great new features found in UVM.
In the spirit of getting OVM users ready for UVM, today Mentor released a version of the UVM Register layer that works with OVM2.1.2. Now OVM users have a standard multi-vendor register package they can use, and they won't have to change their register code when/if they move to UVM. Learn more at blogs.mentor.com/.../uvm-register-kit-available-for-ovm-212
Dave, let me try to clarify my point. I'm arguing that people should generally go to the source, in this case OVM World, for open-source content. I don't understand why anyone would want to pay to get the same bits that are available legitimately for free. But I do understand that many companies make money offering value-adds to open-source content, including layered features, rapid bug fixes, support, convenience, bundling, etc.Red Hat surely fits this model, as do Cadence and Mentor to some extent.
It's fine for Mentor to provide a copy of OVM 2.1.1 for convenience to its customers, especially on a site that includes some of Mentor's value-adds in the form of training. I am merely pointing out that Verification Academy is not an open alternative to OVM World. If the original comment had said "...also available to Mentor customers at..." I would never have even brought up the point.
Tom, I stand by my statement - when I try to download the OVM 2.1.2 zip or tar file from Verification Academy I get "Access denied. You may need to login below or register to access this page." As I know from past experience, registration is not open to all. Q.E.D.
@tomatcadence Apparently, you don't understand open source software. How do you think RedHat is able to require a paid subscription to download Linux from their site? See www.opensource.org/.../definition.php.
In any case, the more widespread software is available, the better it is for the end users.
The premium content at Verification Academy requires registration, but there's a lot of valuable information that anyone can access, including the OVM2.1.2 download.
Why would you download open source from a closed site? Stick to OVM World. While I'm sure that "Verification Academy" admirably serves the needs of Mentor's customers, it is an exclusionary site. It doesn't seem in the spirit of open-source software to trumpet a closed site as the place to download it.
Don't forget that it's also available at verificationacademy.com/.../ovm-2.1.2-download-kit. Enjoy!