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

AMBA CHI-A SVT VMM 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 CHI SVT VIP that supports 'AMBA5 CHI Issue A Specification'.

The CHI VIP Release Notes are installed at:

The AMBA VIP Release Notes (for all other models like AXI, AHB, APB) are installed at:

The CHI VIP VMM User Guide is installed at:

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

CHI VIP Components

CHI 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 CHI VIP defines following configuration classes:

Transaction Objects:
Transaction objects, which are extended from the vmm_data base class, define a unit of CHI 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. CHI VIP defines following transaction classes:

Analysis port:
The monitor in all the groups provide an analysis port. At the end of the CHI transaction, the monitor within the CHI RN & SN groups provides the completed svt_chi_rn_transaction & svt_chi_sn_transaction object respectively, from its analysis port.
The analysis port used by port monitor within the groups is:

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

Functional Coverage:
For a complete list of coverage groups supported by the CHI VIP, please click on the "Covergroups" tab in this class reference documentation.

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

Debug features: