«
»

VMM 1.2 Released

A holiday gift from Synopsys: VMM 2.0 1.2!

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!

This entry was posted on Thursday, January 7th, 2010 at 1:00 am and is filed under Documentation, Doxygen. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Responses to “VMM 1.2 Released”

  1. Jacob Sander Andersen Says:
    February 15th, 2010 at 5:57 am

    Hi,

    I have tried to download your Doxygen filters (I think your work is great and I appreciate it quite a bit) for SV and the VMM scripts. Then I tried to run them on my downloaded versions of VMM 1.0.1, 1.1 and 1.2 from vmm-central.org.

    Everything went fine on 1.0.1, but some warnings were reported on 1.1 and errors were reported on 1.2. I didn’t want to file a bug, since I don’t have an overview of what is already filed. I can send you the log files via mail or file a bug – let me know what you want me to do.

    Regards, JacobSA

  2. Jacob Sander Andersen Says:
    February 15th, 2010 at 5:59 am

    Btw. I was using:

    Doxygen-2.6.1.r133.tar.gz
    VMMdocs-1.6.2.r40.tar.gz

    and doxygen version 1.4.7 on Centos.

  3. Sean Says:
    February 18th, 2010 at 8:23 am

    @Jacob

    Thanks for letting me know about the issue.
    You need to be using the current version of the doxygen binary (1.62).
    If moving to the current version doesn’t solve your issue then please file a bug.

    -Sean

Leave a Reply