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 CHI-A SVT VMM Documentation - Group Class List

Here are the Group classes with brief descriptions:
svt_chi_interconnect_group This class encapsulates the functionality of the interconnect VIP It connects to the link layer of each RN/SN, processes the transactions and routes them to the appropriate port. Currently the interconnect does not route to any SN. Key features: 1. Supports configurable number of RNs, SNs and HNs 2. Receives transactions from RN and snoops other RNs. If transaction is non-snoopable or if none of the snoops returned data, data if fetched from internal memory of interconnect since it currently does not route transactions to SN. 3. Support for snoop filter. The interconnect tracks allocations and de-allocations in each RN. An RN is snooped only if an allocation is present. Enabled by snoop_filter_enable parameter in interconnect configuration. 4. Models configurable number of HNs. This is visible in the interface through the assignment of DBID for normal transactions and TxnID for snoop transactions. DBID and TxnID assignments are made based on the HN that is targetted by a transaction. 5. Support for RETRY based on number of outstanding transactions. The number of outstanding transactions for each port (not HN, but each port that connects to RN) can be configured using the num_outstanding_read_xact and num_outstanding_write_xact of each port of the interconnect. If the number of outstanding transactions exceed the threshold, the interconnect sends a RETRYACK. It then monitors the outstanding transactions and issues a PCRDGRANT when the number of outstanding transactions decreases below the threshold. Known limitations: 1. Does not forward transactions to SN. Uses memory embedded in interconnect instead routing transactions to SN
svt_chi_system_group Description-Unavailable
svt_chi_ic_sn_group Defines a VMM group for the CHI IC SN component.
svt_chi_sn_group Defines a VMM group for the CHI SN component.
svt_chi_ic_rn_group Defines a VMM group for the CHI IC RN component.
svt_chi_rn_group Defines a VMM group for the CHI RN component.
13 August 2024, Copyright © 2024 Synopsys, Inc.