Archive for June, 2010

UVM Source Code Documentation with Doxygen Posted

Thursday, June 17th, 2010

The Accellera VIP TSC has released their ‘early adopter’ release of the UVM (Universal Verification Methodology)!

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:

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


OVM 2.1.1 Release – Documentation Posted

Tuesday, June 15th, 2010

A while back Mentor and Cadence released 2.1.1…  thought that I should catch up and post the docs.  (Looking at the web server logs a few of you tried to get the 2.1.1 docs directly – sorry.  They’re up now!)

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:

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


Doxygen Filter for System Verilog 2.6.2 Released

Monday, June 14th, 2010

A new filter release!

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:

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:

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