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 SVT UVM Documentation - Interfaces Reference

Interfaces for AMBA SVT UVM Documentation: Show All Interfaces

Product Interface Group Interfaces Sub-interfaces
amba_svt Default Group svt_axi_master_if
svt_axi_lp_if
svt_axi_slave_if
svt_axi_if
svt_ahb_master_if
svt_ahb_slave_if
svt_ahb_if svt_ahb_slave_if, svt_ahb_master_if
svt_apb_slave_if
svt_apb_if svt_apb_slave_if
CHI Request Node interface. This is a sub-interface of svt_chi_if. svt_chi_rn_if
CHI Slave Node interface. This is a sub-interface of svt_chi_if. svt_chi_sn_if
CHI IC Request Node interface. This is a sub-interface of svt_chi_if. svt_chi_ic_rn_if
CHI IC Slave Node interface. This is a sub-interface of svt_chi_if. svt_chi_ic_sn_if
Top Level interface for CHI VIP svt_chi_if svt_chi_ic_sn_if, svt_chi_sn_if, svt_chi_ic_rn_if, svt_chi_rn_if

Interface Definition Documentation

 interface svt_axi_master_if
(
input logic common_aclk
)

General description:

The master interface svt_axi_master_if defines the AXI signals appropriate for a single port, along with the modports needed for the AXI master and monitor VIP. Debug signals and a debug modport are also defined. The debug port provides useful information for debugging.

Clock signal description:

Signal Name Signal Description
aclk If all AXI interfaces in the system are expected to run on a different clock, user can use the aclk signal in the port interfaces. Set the configuration parameter svt_axi_system_configuration :: common_clock_mode to 0. In this case, connect the aclk signal in each port interface to the appropriate port specific clock in the testbench.

Debug port description:
In active and passive mode, the VIP assigns a unique number to each transaction. This number is also displayed in the messages issued by the VIP. The debug port reflects this unique transaction number. This makes it easy to fnd a particular transaction on the waveforms, by looking at the debug port signals. For example, if messages mentions that there is a error on transaction #100, used can jump to value #100 on debug port signals, to find the transaction. A seperate debug port is provided for each AXI channel, so that you can jump to the address phase, data phase or response phase of a given transaction, for example transaction #100.

Signal Name Signal Description
read_addr_xact_num Transaction number on read address channel. Used in active mode.
read_data_xact_num Transaction number on read data channel. Used in active mode.
read_data_xfer_id Data transfer number on read data channel. Used in active mode.
write_addr_xact_num Transaction number on write address channel. Used in active mode.
write_data_xact_num Transaction number on write data channel. Used in active mode.
write_data_xfer_id Data transfer number on write data channel. Used in active mode.
write_resp_xact_num Transaction number on write response channel. Used in active mode.
snoop_addr_xact_num Transaction number on snoop address channel. Used in active mode.
snoop_data_xact_num Transaction number on snoop data channel. Used in active mode.
snoop_data_xfer_id Data transfer number on snoop data channel. Used in active mode.
snoop_resp_xact_num Transaction number on snoop response channel. Used in active mode.
mon_read_addr_xact_num Transaction number on read address channel. Used in passive mode.
mon_read_data_xact_num Transaction number on read data channel. Used in passive mode.
mon_read_data_xfer_id Data transfer number on read data channel. Used in passive mode.
mon_write_addr_xact_num Transaction number on write address channel. Used in passive mode.
mon_write_data_xact_num Transaction number on write data channel. Used in passive mode.
mon_write_data_xfer_id Data transfer number on write data channel. Used in passive mode.
mon_write_resp_xact_num Transaction number on write response channel. Used in passive mode.
mon_snoop_addr_xact_num Transaction number on snoop address channel. Used in passive mode.
mon_snoop_data_xact_num Transaction number on snoop data channel. Used in passive mode.
mon_snoop_data_xfer_id Data transfer number on snoop data channel. Used in passive mode.
mon_snoop_resp_xact_num Transaction number on snoop response channel. Used in passive mode.

AXI signal description:
This sub-interface supports signals for AXI3, AXI4, ACE and AXI4 Stream protocols. The names of the signals match the names specified in the AXI specification. Please refer to the AXI specification for specific description of any of the signals.



Modports

Clocking blocks

Functions