{"id":4407,"date":"2011-06-02T14:31:27","date_gmt":"2011-06-02T21:31:27","guid":{"rendered":"https:\/\/blogs.mentor.com\/verificationhorizons\/?p=4407"},"modified":"2026-03-27T08:41:48","modified_gmt":"2026-03-27T12:41:48","slug":"uvm-register-kit-available-for-ovm-212","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/2011\/06\/02\/uvm-register-kit-available-for-ovm-212\/","title":{"rendered":"UVM Register Kit Available for OVM 2.1.2"},"content":{"rendered":"<p>When we looked at requirements for UVM in Accellera, one of the highest priority requests from users was to have a single standard Register Modeling Package. After much discussion in the committee, Mentor and Synopsys worked together to create the UVM Register package, which was subsequently adopted as part of UVM.<\/p>\n<p>In developing the UVM register layer, we combined the VMM RAL data model with a sequence-based API that lets you write UVM sequences in terms of register read\/write transactions, independent of the specific address or bus protocol implemented on the desired interface. The collaboration was productive and efficient and gave UVM a head start in addressing a substantial installed base of register users while keeping a consistent use model for OVM-savvy users as they consider moving to UVM.<\/p>\n<p>So we asked ourselves, if having a standard register package is so important, why not make it available to OVM users without requiring them to move everything else to UVM? Our answer was to release a UVM Register package that does, in fact, work with OVM 2.1.2. As it says in the Release Notes, &#8220;This package is a near verbatim copy of the register layer portion of the Accellera Universal Verification Methodology (UVM 1.1) reference library. Minor additions and modifications\u00a0 were made to enable its use as a standalone package and be compatible\u00a0 with OVM 2.1.2. &#8221; Having this register package means that OVM users now have a standard, robust and vendor-independent register solution that will not require rewrites or use-model changes if\/when they decide to migrate to UVM.<\/p>\n<p>To use the UVM Register package with OVM, you&#8217;ll need to import the uvm_reg_pkg and include the uvm_reg_macros.svh file:<\/p>\n<blockquote>\n<pre>`include \"ovm_macros.svh\"\n`include \"uvm_reg_macros.svh\"\npackage my_reg_model;\n  import ovm_pkg::*;\n  import uvm_reg_pkg::*;\n  ...\nendpackage<\/pre>\n<\/blockquote>\n<p>That&#8217;s it! If you&#8217;re using a code generator that creates UVM register code <!--[if gte mso 9]&gt;  Normal 0     false false false  EN-US X-NONE X-NONE            MicrosoftInternetExplorer4              &lt;![endif]--><!--[if gte mso 9]&gt;                                                                                                                                            &lt;![endif]--><!--[if gte mso 10]&gt;--> <!--[endif] -->directly, you can use that code as-is with the UVM Register Package and OVM2.1.2, with the minor caveat of requiring the import and include statements mentioned above.<\/p>\n<p class=\"MsoPlainText\">The OVM2.1.2 and UVM Register package kits are available at the Verification Academy<strong> <\/strong><a href=\"http:\/\/verificationacademy.com\/news\/ovm-2.1.2-kit-and-uvm-register-kit\" target=\"_blank\" rel=\"noopener\">here<\/a><\/p>\n<p>Enjoy!<\/p>\n<p>-Tom<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When we looked at requirements for UVM in Accellera, one of the highest priority requests from users was to have&#8230;<\/p>\n","protected":false},"author":71936,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[],"coauthors":[],"class_list":["post-4407","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/4407","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/users\/71936"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/comments?post=4407"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/4407\/revisions"}],"predecessor-version":[{"id":14548,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/posts\/4407\/revisions\/14548"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/media?parent=4407"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/categories?post=4407"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/tags?post=4407"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/industry?post=4407"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/product?post=4407"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/verificationhorizons\/wp-json\/wp\/v2\/coauthors?post=4407"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}