How to download VIP smartsearch?
DESIGNWARE_HOMEto required designware home location where VIP Smartsearch should be downloaded.
vip_smartsearch_<version>.runfile.
$DESIGNWARE_HOME/vip/svt/vip_smartsearch/<version>
How to install VIP Smartsearch?
Please refer to the fileVIP_Smartsearch_installation_and_usage_guide.pdfin
$DESIGNWARE_HOME/vip/svt/vip_smartsearch/<version>for installation steps.
Customer Support
For more details about VIP smartsearch tool, contact support_center@synopsys.com.| svt_apb_random_slave_write_transfer_with_random_pstrb_sequence | Abstract: svt_apb_random_slave_write_transfer_with_random_pstrb_sequence defines a sequence in which a APB WRITE is followed by a APB READ to the same address and data integrity check is performed. |
| svt_apb_master_random_transfer_sequence | Abstract: svt_apb_master_random_transfer_sequence defines a sequence in which random APB transactions are issued and based on config_db flags and other values performs the self checks and necessary operations. Sequence is generated using `svt_xvm_do_on_with macros. |
| svt_apb_system_base_sequence | This sequence creates a reporter reference |
| svt_apb_slave_memory_sequence | This sequence generates memory responses to slave requests. This sequence gets the slave request from slave sequencer, randomizes the response, and then either updates the internal memory for write transations or updates the transaction with memory data for read transactions. If the requested address is outside of the configured bounds for the memory then the slave will return with a pslverr response. |
| svt_apb_slave_random_response_sequence | Abstract: class svt_apb_slave_random_response_sequence defines a sequence class that provides random slave response. The sequence receives a response object of type svt_apb_slave_transaction, from slave sequencer. The sequence class then randomizes the response with constraints and provides it to the slave driver within the slave agent. |
| svt_apb_slave_base_sequence | This base sequence obtains the configuration from the sequencer during the pre_body callback. It does not raise or drop objections because slave sequences are reactive, and so are always running. |
| svt_apb_master_read_xact_sequence | This sequence generates a single random read transaction. |
| svt_apb_master_write_xact_sequence | This sequence generates a single random write transaction. |
| svt_apb_master_transaction_sequence_library | APB VIP provides a pre-defined APB Master sequence library svt_apb_master_transaction_sequence_library, which can hold the APB Master sequences. The library by default has no registered sequences. You are expected to call svt_apb_master_transaction_sequence_library :: populate_library method to populate the sequence library with master sequences provided with the VIP. The system configuration is provided to the populate_library method as an argument. Based on the configuration, appropriate sequences are added to the sequence library. You can then load the sequence library in the sequencer within the master agent. |
| apb_master_unalinged_write_read_data_compare_sequence | This sequence generates alternate write and read transactions, with address, data and pstrb not randomized for read. This sequence can also be used for 64Bit address and Data width |
| apb_master_write_read_data_compare_sequence | This sequence generates alternate write and read transactions, with address, data and pstrb not randomized for read. This sequence can also be used for 64Bit address and Data width |
| svt_apb_master_blocking_write_read_addr_sequence | This sequence generates alternate write and read transactions for minimum, middle and maximum address values to traverse the addr range. |
| svt_apb_master_blocking_write_read_all_slave_data_sequence | This sequence generates alternate write and read transactions for all existing slaves. The min, mid and max data values are written and read for each slave . |
| svt_apb_master_random_sequence | This sequence generates random master transactions. |
| svt_apb_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. |