Home > Community > Blogs > Functional Verification > update to the ovm register package
 
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more conveniennt.

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: *

Update to the OVM Register Package

Comments(3)Filed under: Functional Verification, OVM, OVMWorld, IES, Register Package, IP-XACT, verification, Incisive, uvm

OVM users have something new to give thanks for this holiday season -- an update to the OVM Register Package (new link!!). This package is used by novice and advanced users and embodies years of experience gathered through hundreds of SystemVerilog projects.

The Cadence genIES team has been remiss since the demise of the OVM World, which left the OVM community to use OVM_RGM 2.5.  We did try to post to UVM World, but that is really dedicated to the UVM.  Therefore, we will be picking up the contribution thread and maintaining the Cadence contributions to the OVM here.  By far the most popular is the register package so we are posting the latest version 2.7.1 here.  We've included the release notes from 2.6, 2.7, and 2.7.1 to bring you all up to date.  Of course, the complete release note history is in the tarball. 

Release Notes for OVM_RGM2.7.1
Nov 18, 2011

** Bug Fixed:
   ¯¯¯¯¯¯¯¯¯ 
  ¤ Fixed issue with backdoor read for special read fields
  ¤ Fixed issue with sync for special read fields


Release Notes for OVM_RGM2.7
Sept 21, 2011

** Bug Fixed:
   ¯¯¯¯¯¯¯¯¯ 
  ¤ Walking one sequence did not create the regOp when writing
  ¤ Mode based register enum field macro having wrong case statement
  ¤ Typo in DPI file (vhpiHandleT changed to vpiHandle)
  ¤ Check for address overlap for indirect / shared and mode-based corrected

** Enhancements:
   ¯¯¯¯¯¯¯¯¯¯¯¯ 
  ¤ Added support for mode based registers having separate storage

Release Notes for OVM_RGM2.6.1
Aug 18, 2011

** Bug Fixed:
   ¯¯¯¯¯¯¯¯¯ 
  ¤ Fixed issue with syncing to VHDL
  ¤ Register overlap check error with end address
  ¤ Backdoor read of register fields was not properly masked
  ¤ Filtering of registers having unknown value is now only for rd_all regs seq

** Enhancements:
   ¯¯¯¯¯¯¯¯¯¯¯¯ 
  ¤ Allowed backdoor write to read-only fields
  ¤ Allowed register's reset value over-ride using plusArgs
  ¤ Added register array delete at the end of built-in-seq
  ¤ Added support field-level backdoor access for shared register
  ¤ Modified shared_reg_backdoor example and added ipxact file
  ¤ Removed all uvm deprication warnings from examples
  ¤ Added more support for VHDL backdoor std_ulogic_[ports|signals|vector_signals]
  ¤ Modified all headers of XML files to get schema from http
  ¤ Added objection to built-in-sequences
  ¤ Added a global field to mask-out comparison of all non-read-write fields
  ¤ Added a global field to enable warning when accessed address is outside container

 =Incisive genIES Team

 

Comments(3)

By Scheng on November 29, 2011
Hi, would you please check your download link and file again, because I am getting errors while trying to extract the ovm_reg_2.7.1.tar.gz. It seems the archive is damaged. Thanks.

By genIES on November 30, 2011
Scheng,
Thanks for noticing the problem with the file.  We had a problem uploading that left the zip corrupt.  We tried it from both Chrome and IE and it works.
=genIES

By Packaging Connections on July 16, 2012
Great Post! I appreciate this post as its very interesting and informative.... keep posting regarding the same.....
Thank you.....

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.