The library is based on the OVM 2.1.1 release and has a few of additional features:

• objector string (so that you can see who objected)
• log message catching (awesome for negative testing)
• callbacks change (a change that I haven’t looked into …)

As you would probably expect, I have posted the docs here:

http://www.intelligentdv.com/documents/index.html#uvmdox

If you find a bug in the doxygen documentation, then please let me know.

Your-New-VM!

2.1.1 is a bugfix and documentation update release.  It looks like there are a couple of tiny behaviour changes that have to do with stopping components and sequences.  You can take a look at the release-notes.txt file in the OVM release to see if any of the changes affect you.

As usual – I have the updated OVM docs posted here:

http://www.intelligentdv.com/documents/index.html#ovmdox

If you find a bug in the doxygen documentation, then please let me know.

BLTN!

Been busy…  (what?  where have *you* been?)

This release includes:

• bugfix: // inside single-line block comment fails to parse (#51)
• bugfix: #[space]( is not transformed to < (#52)

You can pick up the release from the downloads page here:

http://intelligentdv.com/downloads/index.html#doxygentools

Or – you can grab it directly from the subversion repository with your svn client (or using the WebSVN site here).

TIP! These blog announcements (like this one) often lag the actual release by several weeks…  so I recommend subscribing to the RSS feed for the Doxygen tags on the WebSVN site to keep up-to-date.

A Reminder: the doxygen filter is not a grammar — it, like the doxygen tool, is a lexical parser. So – you will find bugs.  And when you do – please file them to the bug tracker here:

http://intelligentdv.com/bugs/

Your tickets in the tracker are what pushes the filter improvements.

-back!

2.1 includes mostly new features and a few (hidden to you) API changes.  Changes include:

• end of test objection mechanism
• component callbacks
• new field macros for more types

As usual – I have the updated OVM docs posted here:

http://www.intelligentdv.com/documents/index.html#ovmdox

If you find a bug in the doxygen documentation, then please let me know.

Enjoy!

1.2 is an all new architecture. Changes include:

• update of support classes to parametrized classes (generators, channel, etc.)
• hierarchical structure like OVM — everything from vmm_object base; testbench components from vmm_unit
• hierarchical phasing: phasing built into the unit –> implicit phasing in unit children (so now its built into the xactor)
• class factory – replace components / objects from the testcase
• component interconnect with TLM2.0
• hierarchical configuration

As usual – I have the updated VMM docs posted here:

http://www.intelligentdv.com/documents/index.html#vmmdox

If you find a bug in the doxygen documentation, then please let me know.

New!

Finally!  Released what has been sitting in trunk for months now…

This release includes:

• bugfix: SystemVerilog interfaces with parameters not supported (#47)
• change: improved routine for processing parameterizations

You can pick up the release from the downloads page here:

http://intelligentdv.com/downloads/index.html#doxygentools

Or – you can grab it directly from the subversion repository with your svn client (or using the WebSVN site here).

TIP! These blog announcements (like this one) often lag the actual release by several weeks…  so I recommend subscribing to the RSS feed for the Doxygen tags on the WebSVN site to keep up-to-date.

A Reminder: the doxygen filter is not a grammar — it, like the doxygen tool, is a lexical parser. So – you will find bugs.  And when you do – please file them to the bug tracker here:

http://intelligentdv.com/bugs/

Your tickets in the tracker are what pushes the filter improvements.

-improved!

2.0.3 includes mostly bug fixes with a few performance improvements.  Changes include:

• addition of messaging/logging macros to improve performance
• promotion of convert2string() from ovm_transaction to ovm_object – replacing the do_sprint() method.
• improved configuration performance
• and a bunch of bug fixes

As usual – I have the updated OVM docs posted here:

http://www.intelligentdv.com/documents/index.html#ovmdox

If you find a bug in the doxygen documentation, then please let me know.

-fix

As usual – documentation is posted here:

http://www.intelligentdv.com/documents/index.html#vmmdox

If you find a bug in the doxygen documentation, then please let me know.

-Interop

Shows how to:

• build a modern randomized SystemVerilog verification component / transaction in a generic fashion
• integrate a generic transaction / component into the VMM
• write a VMM transaction / transactor driver / transactor monitor
• build a VMM environment and signal layer
• connect a DUT to a class based testbench using interfaces with modport, clocking blocks and virtual interfaces
• use SystemVerilog constraints to get a desired result
• implement functional coverage
• use VMM callbacks to collect functional coverage
• create (and run) tests in the VMM style (vmm_test) – by instantiating and constraining the environment

Can be used to:

• drive one (or more) active high or low reset(s)
• drive a sync/async assert/deassert reset
• drive reset for a specific or random range duration
• assert / deassert asynchronously randomly within the clock period
• monitor existing reset(s) for coverage
• can be driven with transactions or with direct method calls of the bfm methods

All of the SystemVerilog library source code including the code required to document and run the environment are available to download here:

http://www.intelligentdv.com/downloads/index.html#svreset

The library is fully documented with doxygen and that documentation is available here:

http://www.intelligentdv.com/documents/index.html#resetdox

The complete details of what the library includes are after the break.

The library includes:

• A Base Library that includes:
  • Reset Transaction Class – idv_rst_trans – describes the DUT reset. The properties allow description of:
    • assertion clock relationship (async/sync)
    • deassertion clock relationship (async/sync)
    • number of cycles that reset is active
    • number of cycles to wait prior to assertion
    • number of cycles to wait after reset (prior to returning from the reset task)
    • for async assert: time from rising edge to assert
    • for async deassert: time from rising edge to deassert
  • Reset Transaction Defaults Class – idv_rst_trans_default – constrains the DUT reset. This class can be extended with the user overriding the constraints or used as an example to be reimplemented with user defined constraints.
  • Reset Bus Functional Model (BFM) Transactor Class – idv_rst_bfm – generates a reset based on the passed reset description
    • do_reset method does the reset based on passed in reset transaction (idv_rst_trans)
    • on construction handle to virtual interface (idv_rst_if) passed in
    • on construction definition of active high/low reset – BFM can generate active high or low reset
  • Reset Bus Functional Monitor Transactor Class – idv_rst_mon – generates a reset transaction (description) based on the monitored interface
    • do_reset method waits for reset to occur on interface and outputs a populated reset transaction object
    • on construction handle to virtual interface (idv_rst_if) passed in
    • on construction definition of active high/low reset – can monitor active high or low reset
    • implementation of monitor is limited to monitoring reset duration; other transaction properties are not populated
  • Reset Interface – idv_rst_if – SystemVerilog Interface
    • module ports (modport) defined for BFM, Monitor, and DUT perspectives
    • clocking block defined for BFM and Monitor – for synchronous activity
• A VMM implementation of the library that includes:
  • VMM Data Transaction Class – idv_rst_data – a vmm_data extended wrapper around the idv_rst_trans class. Includes implementation of the required vmm_data methods. File also includes macro calls to create the vmm_channel IPC channel and vmm_atomic_gen atomic generator.
  • VMM Xactor BFM Class – idv_rst_bfm_xactor – a vmm_xactor extended wrapper around the idv_rst_bfm class. Includes implementation of the required vmm_xactor methods. Input interconnect with generator uses vmm_channel.
  • VMM Xactor Monitor Class – idv_rst_mon_xactor – a vmm_xactor extended wrapper around the idv_rst_mon class. Includes implementation of the required vmm_xactor methods. Output interconnect with sink uses vmm_channel.
  • VMM Xactor Callbacks Class – idv_rst_xactor_callbacks – a vmm_xactor_callbacks extension with pure virutual pre and post transaction callback methods. Can be appended to either the reset bfm or monitor transactor.
  • VMM Xactor Coverage Callback Class – idv_rst_cov_callback – an implementation of reset coverage – can be appended to either the reset bfm or monitor xactor.
• A complete VMM environment to test the library, and to serve as an example VMM environment, that includes:
  • TestBench Top – tb_top – the signal layer top – instantiates the DUT, interfaces, and clock generator
  • Environment – env – the environment top – configures and instantiates the generators and transactors; drives the testbench sequence
  • Tests – testXXX – the testcases; each constrains a combination of the environment configuration and/or environment transactions to acheive a goal
  • Testcases – example testcases to drive specific scenarios

-reset

This release includes:

• bugfix: macros with `” aren’t properly handled (stringize issue) (#39)
• bugfix: protected keyword does not play well with multi-line enums and member variables (#45)
• bugfix: import package should be ignored (#40)
• feature: add support for SV Packages (#20)
• workaround: Does not handle nested OVM macros (doxygen issue) (#43)
• change: comments are no longer filtered from source (doxyfile delta change)
• change: added language switch for sv/svh extension — C++

You can pick up the release from the downloads page here:

http://intelligentdv.com/downloads/index.html#doxygentools

Or – you can grab it directly from the subversion repository with your svn client (or using the WebSVN site here).

TIP! These blog announcements (like this one) often lag the actual release by several weeks…  so I recommend subscribing to the RSS feed for the Doxygen tags on the WebSVN site to keep up-to-date.

A Reminder: the doxygen filter is not a grammar — it, like the doxygen tool, is a lexical parser. So – you will find bugs.  And when you do – please file them to the bug tracker here:

http://intelligentdv.com/bugs/

Your tickets in the tracker are what pushes the filter improvements.

-another fix