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.Inheritance diagram for class svt_axi_slave:
This class is an SVT Driver extension that implements an AXI Slave component.
|
||||||
Build Phase Constructs the common class
| ||||||
|
|
||
Returns the number of outstanding slave transactions.
|
|
||||
|
|
||||
|
|
||||||
|
|
||
Callback issued to allow the testbench to collect functional coverage information from a transaction received at the seq_item_port.
xact - A reference to the data descriptor object of interest. |
|
||
Called when there user wants to drive user injected check values on non-transaction parity signals.
signal_context - Context to why the callback is called for a given signal. parity_signal - Name of parity signal for which the callback is being called. calculated_parity_signal_val - Value of the parity signal. |
|
||||||
|
|
||
Called after getting a transaction from the input tlm port.
xact - A reference to the data descriptor object of interest. |
|
||
Called by the component after pulling a AXI Service Requst out of its AXI Service Request input, but before acting on the AXI Service Request in any way.
xact - A reference to the data descriptor object of interest. |
|
||
Called before driving the read data phase of a transaction.
xact - A reference to the data descriptor object of interest. |
|
||
Called before driving write response phase of a write transaction.
xact - A reference to the data descriptor object of interest. |
|
||||
Called when a new configuration is applied to the VIP
| ||||
|
|
||||
Report phase execution of the OVM component
| ||||
|
|
||||||
Run phase Starts persistent threads like consume_from_seq_item_port()
| ||||||
|
|
|
Configuration object copy to be used in set/get operations.
|
|
|
Common features of AXI Slave components
|
|
|
Response port provided to supply respone and data information in a delayed manner. Refer user guide for a detailed description.
|
|
|
Event triggers when slave has received the new read transaction on the port interface
|
|
|
Event triggers when slave has received the new write transaction on the port interface
|
|
|
Event triggers when slave driver consumes the transaction object . At this point, transaction object is not yet processed or transmitted on the bus.
|
|
|
Event triggers when slave has completed transaction i.e. for WRITE transaction this events triggers once slave sends the write response and for READ transaction this event triggers when slave has send all read data.
|
|
|
Shared status object
|
|
|
Request port provided to supply snoop transactions to a slave port that is instantiated in the interconnect.
|
|
|
Snoop request port provided to allow snoop requests to be sent from the slave, using Slave snoop sequencer
|
|
|
AXI Service TLM Sequence Item Pull Port
Provides a mechanism for submitting service requests recognized by the driver. The handle to this TLM sequence item pull port can be set or obtained through the driver's public member svc_seq_item_port. |
|
||||
|
|