Skip to Content

SV

Posted on  by  from the site Verification Martial Arts
Srinivasan Venkataramanan, CVC Pvt. Ltd. Vishal Namshiker, Brocade Communications India Any complex system requires debugging at some point or the other. To ease the debug process, a good, proven coding practice is to add enough messages for the end user to aid in debug. However as systems become mature the messages tend to become too many and quickly users feel a need for controlling the messages.
Srinivasan Venkataramanan
Posted in
Posted on  by  from the site Verification Martial Arts
  Weihua Han, CAE, Synopsys As a well-known Object-Oriented technique, class factory has actually been applied in VMM since inception. For instance, in the vmm atomic and scenario generators, by assigning different blueprints to randomized_obj and scenario_set[] properties, these generators can generate transactions with user specified patterns. Using the class factory pattern, users create an instance with a pre-defined method (such as allocate() or copy()) instead of the constructor.
Wei-Hua Han
Posted in
Posted on  by  from the site Verification Martial Arts
Fabian Delguste / Synopsys Verification Group I’m very pleased to announce that VMM 1.2 beta is now available. You’re welcome to enroll our VMM 1.2 Beta program by signing up the form on VMM Central at: http://www.vmmcentral.org/cgi-bin/beta/reg1.cgi As you know, the VMM methodology defines industry best practices for creating robust, reusable and scalable verification environments using SystemVerilog.
Fabian Delguste
Posted in
Posted on  by  from the site Verification Martial Arts
Weihua Han, CAE, Synopsys Functional coverage plays an essential role in Coverage Driven Verification. In this blog, I’ll explain a modular way of modeling and implementing  functional coverage models. SystemVerilog users can take the advantage of  the “covergroup” construct to implement functional coverage. However this is not enough.
Wei-Hua Han
Posted in
Posted on  by  from the site Verification Martial Arts
Adiel Khan, Synopsys CAE Increasingly, more design-oriented engineers are writing VMM code. Some are trying to map typically good design architecture practices to verification development. A dangerous mapping is parameterization, from modules to classes. In my old Verilog testbenches I would develop reusable modules and use #parameters extensively to control the settings of the modules I was instantiating. (It was a sad day when I heard IEEE was deprecating my friend the defparam). 1.
Adiel Khan
Posted on  by  from the site Verification Martial Arts
Weihua Han, CAE, Synopsys Here I describe one major difference between virtual and non-virtual methods, and how type name hiding can collide with these methods. This is commonly used OOP feature in SystemVerilog. “type name hiding” here refers to the situation where a user type definition in the derived class uses the same type name defined in base class, i.e, the new type definition in derived class “hides” the type definition in base class.
Wei-Hua Han
Posted in
Posted on  by  from the site Verification Martial Arts
Even though VMM 1.1 is only the second Open Source release of the VMM library, it follows in a long series of customer-based productivity enhancements that have been made to VMM since the original specification was published back in 2005. I would like to thank all of the customers who kindly contributed to the requirement specification, reviews and beta-testing.
janick
Posted in
Posted on  by  from the site Verification Martial Arts
The VMM Register Abstract Abstraction layer is documented with a 64-bit data value system.
janick
Posted in
Syndicate content