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
13 August 2024, Copyright © 2024 Synopsys, Inc.

AMBA SVT UVM Documentation - Agent Class List

Here are the Agent classes with brief descriptions:
svt_apb_slave_agent The slave agent encapsulates slave sequencer, slave driver, and system monitor. The slave agent can be configured to operate in active mode and passive mode. The user can provide APB sequences to the slave sequencer. The slave agent is configured using system configuration svt_apb_slave_configuration . The system configuration should be provided to the slave agent in the build phase of the test. Within the slave agent, the slave driver gets sequences from the slave sequencer. The slave driver then drives the APB transactions on the APB port. The slave driver and system monitor components within slave agent call callback methods at various phases of execution of the APB transaction. After the APB transaction on the bus is complete, the completed sequence item is provided to the analysis port of port monitor, which can be used by the testbench.
svt_apb_master_agent The master agent encapsulates master sequencer, master driver, and system monitor. The master agent can be configured to operate in active mode and passive mode. The user can provide APB sequences to the master sequencer. The master agent is configured using system configuration svt_apb_system_configuration . The system configuration should be provided to the master agent in the build phase of the test. Within the master agent, the master driver gets sequences from the master sequencer. The master driver then drives the APB transactions on the APB port. The master driver and system monitor components within master agent call callback methods at various phases of execution of the APB transaction. After the APB transaction on the bus is complete, the completed sequence item is provided to the analysis port of port monitor, which can be used by the testbench.
svt_ahb_decoder This class implements an AHB DECODER component.
svt_ahb_arbiter This class implements an AHB ARBITER component
svt_ahb_slave_agent The svt_ahb_slave_agent encapsulates sequencer, driver, and slave monitor. The svt_ahb_slave_agent can be configured to operate in active mode and passive mode. The user can provide AHB sequences to the sequencer. The svt_ahb_slave_agent is configured using slave configuration svt_ahb_slave_configuration . The slave configuration should be provided to the svt_ahb_slave_agent in the build phase of the test. In the slave agent, the slave monitor samples the AHB port signals. When a new transaction is detected, slave monitor provides a response request transaction to the slave sequencer. The slave response sequence within the sequencer programs the appropriate slave response. The updated response transaction is then provided by the slave sequencer to the slave driver. The slave driver in turn drives the response on the AHB bus. The driver and slave monitor components within svt_ahb_slave_agent call callback methods at various phases of execution of the AHB transaction. After the AHB transaction on the bus is complete, the completed sequence item is provided to the analysis port of slave monitor in both active and passive mode, which can be used by the testbench.
svt_ahb_master_agent The svt_ahb_master_agent encapsulates the sequencer, driver and master monitor. The svt_ahb_master_agent can be configured to operate in active mode and passive mode. The user can provide AHB sequences to the sequencer. The svt_ahb_master_agent is configured using the svt_ahb_master_configuration object. The master configuration should be provided to the agent in the build phase of the test. Within the agent, the driver gets sequence items from the sequencer. The driver then drives the AHB transactions on the AHB bus. The driver and monitor components within the agent call callback methods at various phases of execution of the AHB transaction. After the AHB transaction on the bus is complete, the completed sequence item is provided to the analysis port of the monitor in both active and passive mode, which can be used by the testbench.
svt_chi_ic_sn_agent This class is the SN Agent class.
svt_chi_sn_agent This class is the SN Agent class.
svt_chi_ic_rn_agent This class is the SN Agent class.
svt_chi_rn_agent This class is the RN Agent class.
svt_axi_ic_slave_agent The slave agent encapsulates slave sequencer, slave driver, and port monitor. The slave agent can be configured to operate in active mode and passive mode. The user can provide AXI response sequences to the slave sequencer. The slave agent is configured using port configuration, which is available in the system configuration. The port configuration should be provided to the slave agent in the build phase of the test. In the slave agent, the port monitor samples the AXI port signals. When a new transaction is detected, port monitor provides a response request sequence to the slave sequencer. The slave response sequence within the sequencer programs the appropriate slave response. The updated response sequence is then provided by the slave sequencer to the slave driver. The slave driver in turn drives the response on the AXI bus. The slave driver and port monitor components within the slave agent call the callback methods at various phases of execution of the AXI transaction. After the AXI transaction on the bus is complete, the completed sequence item is provided to the analysis port of port monitor, which can be used by the testbench.
svt_axi_lp_master_agent The master agent encapsulates port monitor. The master agent can be configured to operate in active mode and passive mode. Currently only supported in passive mode. The master agent is configured using port configuration svt_axi_lp_port_configuration , which is available in the system configuration svt_axi_system_configuration . The port configuration should be provided to the master agent in the build phase of the test. After the AXI low power handshake is complete on the master, the completed sequence item is provided to the analysis port of port monitor, which can be used by the testbench.
svt_axi_slave_agent The slave agent encapsulates slave sequencer, slave driver, and port monitor. The slave agent can be configured to operate in active mode and passive mode. The user can provide AXI response sequences to the slave sequencer. The slave agent is configured using port configuration, which is available in the system configuration. The port configuration should be provided to the slave agent in the build phase of the test. In the slave agent, the port monitor samples the AXI port signals. When a new transaction is detected, port monitor provides a response request sequence to the slave sequencer. The slave response sequence within the sequencer programs the appropriate slave response. The updated response sequence is then provided by the slave sequencer to the slave driver. The slave driver in turn drives the response on the AXI bus.
svt_axi_ic_master_agent The master agent encapsulates master sequencer, master driver, and port monitor. The master agent can be configured to operate in active mode and passive mode. The user can provide AXI sequences to the master sequencer. The master agent is configured using port configuration svt_axi_port_configuration , which is available in the system configuration svt_axi_system_configuration . The port configuration should be provided to the master agent in the build phase of the test. Within the master agent, the master driver gets sequences from the master sequencer. The master driver then drives the AXI transactions on the AXI port. The master driver and port monitor components within master agent call callback methods at various phases of execution of the AXI transaction. After the AXI transaction on the bus is complete, the completed sequence item is provided to the analysis port of port monitor, which can be used by the testbench.
svt_axi_master_agent The master agent encapsulates master sequencer, master driver, and port monitor. The master agent can be configured to operate in active mode and passive mode. The user can provide AXI sequences to the master sequencer. The master agent is configured using port configuration svt_axi_port_configuration , which is available in the system configuration svt_axi_system_configuration . The port configuration should be provided to the master agent in the build phase of the test. Within the master agent, the master driver gets sequences from the master sequencer. The master driver then drives the AXI transactions on the AXI port. The master driver and port monitor components within master agent call callback methods at various phases of execution of the AXI transaction. After the AXI transaction on the bus is complete, the completed sequence item is provided to the analysis port of port monitor, which can be used by the testbench.
13 August 2024, Copyright © 2024 Synopsys, Inc.