How to download VIP smartsearch?
DESIGNWARE_HOMEto required designware home location where VIP Smartsearch should be downloaded.
vip_smartsearch_<version>.runfile.
$DESIGNWARE_HOME/vip/svt/vip_smartsearch/<version>
How to install VIP Smartsearch?
Please refer to the fileVIP_Smartsearch_installation_and_usage_guide.pdfin
$DESIGNWARE_HOME/vip/svt/vip_smartsearch/<version>for installation steps.
Customer Support
For more details about VIP smartsearch tool, contact support_center@synopsys.com.
☛ NOTE: Based on the AMBA Progressive Terminology updates, you must interpret the term Master as Manager, and Slave as Subordinate in the VIP documentation and messages.
Introduction
This is the Class Reference Manual of Synopsys ATB SVT VIP.
The User Guide is installed at:
The AMBA VIP Release Notes are installed at:
The Synopsys VIP for ATB is a suite of advanced verification components and data objects based on SystemVerilog OVM-compliant technology. This on-line help contains information about the classes, functions, and member variables. It shows class hierarchy and contents and it provides links you can use to navigate to more details. Below is the summary of the components and the user interface of the Synopsys ATB VIP.
ATB VIP Components
ATB VIP User Interface
Configuration Objects:
Configuration data objects convey the system level and port level testbench configuration. The configuration data objects contain built-in constraints, which come into effect when the configuration objects are randomized. If the configuration needs to be changed later, it can be done through reconfigure() method of the master, slave or system components. The ATB VIP defines following configuration classes:
Transaction Objects:
Transaction objects, which are extended from the ovm_transaction base class, define a unit of ATB protocol information that is passed across the bus. The attributes of transaction objects are public and are accessed directly for setting and getting values. Most transaction attributes can be randomized. The transaction object can represent the desired activity to be simulated on the bus, or the actual bus activity that was monitored. ATB VIP defines following transaction classes:
Analysis port:
The port monitor in the Master & Slave agents provides an analysis port. At the end of the transaction, the port monitor within the Master & Slave agents provides the completed svt_atb_master_transaction & svt_atb_slave_transaction object respectively, from its analysis port.
The analysis port used by port monitor within Master agent and Slave agent is:
Callbacks:
Callbacks are an access mechanism that enable the insertion of user-defined code and allow access to objects for scoreboarding and functional coverage. Each master and slave component is associated with a callback class that contains a set of callback methods. ATB VIP provides following callback class:
Interfaces and modports:
SystemVerilog models signal connections using interfaces and modports. Interfaces define the set of signals which make up a port connection. Modports define collection of signals for a given port, the direction of the signals, and the clock with respect to which these signals are driven and sampled. ATB VIP provides below interfaces:
Functional Coverage:
Functional Coverage is NOT FULLY SUPPORTED in this Release. For details of the coverage please refer to Coverage tab in this class reference documentation. ATB VIP provides below coverage callback classes:
Protocol Checks:
For a complete list of protocol checks supported by the ATB VIP, please click on the "Protocol Checks" tab in this class reference documentation.
ATB sequence collection:
For a complete list of sequences provided with the ATB VIP, please click on the "Sequences" tab in this class reference documentation.