VIP Smartsearch

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

$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

Product Base	Group
amba_svt	Ungrouped Sequences

Product Base

Group

amba_svt

Ungrouped Sequences

Sequence Group	Sequences	Sequences Description	Controls	Sequencer
default	svt_atb_master_base_sequence	This sequence raises/drops objections in the pre/post_body so that root sequences raise objections but subsequences do not. All other master sequences in the collection extend from this base sequence. It also polls continuously flush_or_sync_request_port to capture requests raised by Slave passed through Driver. Once it detects requests then it stores each request to its respective mailbox :: flush_request_mbox or sync_request_mbox one for Flush or Synchronization requests.	rand_percentage_to_start_zero_delay_response This sequence provides a mechanism to user to randomly pick a transaction from which it starts responding with zero data valid delay. Following parameter sets the percentage chance a master transaction will be used to start sending with zero delay response. num_txn_with_zero_ready_delay_response Once zero delay responses start being sent-out, it only stops after sending certain number of transactions with zero delay response. Following parameter holds a random value which determines the number of transactions with zeror delay response as described above.	svt_atb_master_sequencer
default	svt_atb_flush_with_nonzero_burst_sequence	This sequence also generates random master transactions. This sequence also checks whether Slave already requested to Flush Data or requested for Synchronization. If it finds such request pending then it first checks for Flush Request and then respond with Flush Data. When it detects Flush request, it ignores any Synchronization request pending at that point. This sequence sends FLUSH_DATA transaction with non-zero burst_length in response to flush request received from the slave. This sequence only serves last seen Synchronization Request which are not o overlapped with Flush Request from Slave.	sequence_length Number of Transactions in a sequence.	svt_atb_master_sequencer
default	svt_atb_flush_with_zero_burst_sequence	This sequence also generates random master transactions. This sequence also checks whether Slave already requested to Flush Data or requested for Synchronization. If it finds such request pending then it first checks for Flush Request and then respond with Flush Data. When it detects Flush request, it ignores any Synchronization request pending at that point. This sequence sends FLUSH_DATA transaction with burst_length zero in response to flush request received from the slave. This sequence only serves last seen Synchronization Request which are not o overlapped with Flush Request from Slave.	sequence_length Number of Transactions in a sequence.	svt_atb_master_sequencer
default	svt_atb_master_random_sequence	This sequence generates random master transactions. However, user can control type of transaction generated NORMAL Trace Data or TRIGGER Data based on following two define macros. `define svt_atb_master_random_sequence_NORMAL_DATA_WT (default value 50) `define svt_atb_master_random_sequence_TRIGGER_DATA_WT (default value 20) This sequence also checks whether Slave already requested to Flush Data or requested for Synchronization. If it finds such request pending then it first checks for Flush Request and then respond with Flush Data. When it detects Flush request, it ignores any Synchronization request pending at that point. Depending on the value of "send_flush_data_asap" flag it sets FLUSH_DATA transaction burst_length as 0 or non-zero. If it sets, burst_length = 0 then that causes driver to assert AFREADY immediately and hence data (which are already generated at Trace Source) transfer in-progress are marked as FLUSH DATA. Otherwise, it sends random number of Flush Data which can be controlled through svt_atb_master_transaction constraint. `define svt_atb_master_random_sequence_SEND_FLUSH_DATA_ASAP is used to control this behaviour. Default value 1 i.e. send Flush Data immediately. This sequence only serves last seen Synchronization Request which are not o overlapped with Flush Request from Slave.	sequence_length Number of Transactions in a sequence. send_flush_data_asap Description-Unavailable	svt_atb_master_sequencer
default	svt_atb_slave_base_sequence	This sequence raises/drops objections in the pre/post_body so that root sequences raise objections but subsequences do not. All other slave sequences in the collection extend from this base sequence. Execution phase: run_phase Sequencer: Slave agent sequencer	rand_percentage_to_start_zero_delay_response This sequence provides a mechanism to user to randomly pick a transaction from which it starts responding with zero data valid delay. Following parameter sets the percentage chance a master transaction will be used to start sending with zero delay response. num_txn_with_zero_ready_delay_response Once zero delay responses start being sent-out, it only stops after sending certain no. of transactions with zero delay response. Following parameter holds a random value which determines the number of transactions with zeror delay response as described above. rand_percentage_to_send_empty_flush_request Description-Unavailable num_wait_cycles_before_sending_empty_flush_request Description-Unavailable	svt_atb_slave_sequencer
default	svt_atb_slave_response_sequence	This sequence generates random responses to response requests. This sequence gets the slave response sequence item from slave sequencer, randomizes the response, and provides the randomized response to the slave driver. The sequence uses the built-in slave memory and writes received data into slave memory. This sequence runs forever, and so is not registered with the slave sequence library.	--	svt_atb_slave_sequencer
default	svt_atb_system_base_sequence	Base System Sequence to be used by all sequences that will use system sequencer to send transaction to any master ports.	--	svt_atb_system_sequencer
default	svt_atb_random_system_sequence	Basic Random Traffic Sequence sent to Master port 0	--	svt_atb_system_sequencer

Sequence Group

Sequences

Sequences Description

Controls

Sequencer

default

svt_atb_master_base_sequence

This sequence raises/drops objections in the pre/post_body so that root sequences raise objections but subsequences do not. All other master sequences in the collection extend from this base sequence.

It also polls continuously flush_or_sync_request_port to capture requests raised by Slave passed through Driver. Once it detects requests then it stores each request to its respective mailbox :: flush_request_mbox or sync_request_mbox one for Flush or Synchronization requests.

svt_atb_master_sequencer

default

svt_atb_flush_with_nonzero_burst_sequence

This sequence also generates random master transactions.

This sequence also checks whether Slave already requested to Flush Data or requested for Synchronization. If it finds such request pending then it first checks for Flush Request and then respond with Flush Data.

When it detects Flush request, it ignores any Synchronization request pending at that point.
This sequence sends FLUSH_DATA transaction with non-zero burst_length in response to flush request received from the slave.

This sequence only serves last seen Synchronization Request which are not o overlapped with Flush Request from Slave.

svt_atb_master_sequencer

default

svt_atb_flush_with_zero_burst_sequence

This sequence also generates random master transactions.

When it detects Flush request, it ignores any Synchronization request pending at that point.
This sequence sends FLUSH_DATA transaction with burst_length zero in response to flush request received from the slave.

This sequence only serves last seen Synchronization Request which are not o overlapped with Flush Request from Slave.

svt_atb_master_sequencer

default

svt_atb_master_random_sequence

This sequence generates random master transactions. However, user can control type of transaction generated NORMAL Trace Data or TRIGGER Data based on following two define macros. `define svt_atb_master_random_sequence_NORMAL_DATA_WT (default value 50) `define svt_atb_master_random_sequence_TRIGGER_DATA_WT (default value 20)

When it detects Flush request, it ignores any Synchronization request pending at that point.
Depending on the value of "send_flush_data_asap" flag it sets FLUSH_DATA transaction burst_length as 0 or non-zero. If it sets, burst_length = 0 then that causes driver to assert AFREADY immediately and hence data (which are already generated at Trace Source) transfer in-progress are marked as FLUSH DATA. Otherwise, it sends random number of Flush Data which can be controlled through svt_atb_master_transaction constraint.

`define svt_atb_master_random_sequence_SEND_FLUSH_DATA_ASAP is used to control this behaviour. Default value 1 i.e. send Flush Data immediately.

This sequence only serves last seen Synchronization Request which are not o overlapped with Flush Request from Slave.

svt_atb_master_sequencer

default

svt_atb_slave_base_sequence

This sequence raises/drops objections in the pre/post_body so that root sequences raise objections but subsequences do not. All other slave sequences in the collection extend from this base sequence.

Execution phase: run_phase Sequencer: Slave agent sequencer

svt_atb_slave_sequencer

default

svt_atb_slave_response_sequence

This sequence generates random responses to response requests. This sequence gets the slave response sequence item from slave sequencer, randomizes the response, and provides the randomized response to the slave driver. The sequence uses the built-in slave memory and writes received data into slave memory.

This sequence runs forever, and so is not registered with the slave sequence library.

svt_atb_slave_sequencer

default

svt_atb_system_base_sequence

Base System Sequence to be used by all sequences that will use system sequencer to send transaction to any master ports.

svt_atb_system_sequencer

default

svt_atb_random_system_sequence

Basic Random Traffic Sequence sent to Master port 0

svt_atb_system_sequencer

VIP Smartsearch

ATB SVT OVM Documentation - Sequence Page

Product: amba_svt - Sequence Details:

All Sequence Group Sequences Sequences Description Controls Sequencer

VIP Smartsearch

ATB SVT OVM Documentation - Sequence Page

Product: amba_svt - Sequence Details:

Show/Hide All Sequence Group Sequences Sequences Description Controls Sequencer

All Sequence Group Sequences Sequences Description Controls Sequencer