VIP Smartsearch

X
  • VIP Smartsearch is a framework that supports search within VIP reference documents using query in natural language. It facilitates reordering of search results and keeps record of user’s decision for the ordering of result display and applies that in search of same query on subsequent usage.
  • How to download VIP smartsearch?

    1. Get VIP Smartsearch (Available as a seperate run file).
    2. Set environment variable
      DESIGNWARE_HOME
      to required designware home location where VIP Smartsearch should be downloaded.
    3. Run
      vip_smartsearch_<version>.run
      file.
      VIP Smartsearch will be downloaded to the location
      $DESIGNWARE_HOME/vip/svt/vip_smartsearch/<version>
  • How to install VIP Smartsearch?

    Please refer to the file
    VIP_Smartsearch_installation_and_usage_guide.pdf
    in
    $DESIGNWARE_HOME/vip/svt/vip_smartsearch/<version>
    for installation steps.
  • Customer Support

    For more details about VIP smartsearch tool, contact support_center@synopsys.com.
    Mention your queries along with below details and send email to above email id.
    Product: Verification IP
    Sub Product: <vip_title>
    Tool: VIP Smartsearch

DTI SVT UVM Documentation main page

Version W-2024.09

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 DTI SVT VIP.

The DTI SVT User Guide is installed at:

The AMBA VIP Release Notes are installed at:

The Synopsys VIP for DTI is a suite of advanced verification components and data objects based on SystemVerilog UVM-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 DTI VIP.

DTI VIP Components

DTI 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, interconnect or system components. The DTI VIP defines following configuration classes:

Transaction Objects:
Transaction objects, which are extended from the uvm_transaction base class, define a unit of DTI 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. DTI 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_dti_master_transaction & svt_dti_slave_transaction object respectively, from its analysis port.
The Port Monitor in the Interconnect Master Agent and Interconnect Slave agent also provides an analysis port. At the end of the transaction on the interconnect ports, the port monitor within the Interconnect Master Agent and Interconnect Slave agent provides the completed svt_dti_ic_master_transaction and svt_dti_ic_slave_transaction object respectively, from its analysis port.
The analysis port used by port monitor within Master agent, Slave agent, Interconnect Master Agent and Interconnect Slave agent is:

The port monitor in the Master & Slave agents provides an analysis port to provide pre-completion transaction object. The port monitor within the Master & Slave agents will provide svt_dti_master_transaction & svt_dti_slave_transaction object respectively into this new analysis port just after svt_dti_port_monitor new_transaction_started callback is issued.
The analysis port used by port monitor within Master agent, Slave agent is: The port monitor in the Master agent provides an analysis port to provide completed DTI response object and DTI request object in passive mode.
The analysis port used by port monitor within Master 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. DTI VIP provides following callbacks classes:

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. DTI VIP provides below interfaces:

The port sub-interface provides below modports to connect VIP to the DUT: Functional Coverage:
The Synopsys DTI Verification IP provides default transaction coverage. The coverage is shaped based on the configuration. DTI VIP provides below coverage callback classes: The coverage data callback class defines default data and event information that are used to implement the coverage groups. The coverage data callback class is extended from callback class svt_dti_port_monitor_callback . This class itself does not contain any cover groups. This class is extended from the coverage data callback class. This class includes default cover groups.

Protocol Checks:
For a complete list of protocol checks supported by the DTI VIP, please click on the "Protocol Checks" tab in this class reference documentation.

DTI sequence collection:
The DTI VIP provides a collection of DTI master & slave sequences. These sequences can be registered with the master & slave sequencers within the master & slave agents respectively, to generate different types of DTI scenarios.

For a complete list of Sequences supported by the DTI VIP, please click on the "Sequences" tab in this class reference documentation.