
VHDL Slave BFM
get_data_ready_delay()
Mentor Verification IP AE AXI4-Lite User Guide, V10.3
247
April 2014
get_data_ready_delay()
This nonblocking procedure gets the data_ready_delay field for a transaction that is uniquely
identified by the transaction_id field previously created by the create_slave_transaction()
procedure.
Example
-- Create a slave transaction. Creation returns tr_id to identify
-- the transaction.
create_slave_transaction(tr_id, bfm_index, axi4_tr_if_0(bfm_index));
-- Get the read data channel RREADY delay for the
-- data phase (beat) of the tr_id transaction.
get_data_ready_delay(data_ready_delay, 0, tr_id, bfm_index,
axi4_tr_if_0(bfm_index));
Prototype
get_data_ready_delay
(
data_ready_delay: out integer;
transaction_id : in integer;
bfm_id : in integer;
path_id : in axi4_path_t; --optional
signal tr_if : inout axi4_vhd_if_struct_t
);
Arguments
data_ready_delay Data channel array to hold RREADY/WREADY delay
measured in ACLK cycles for this transaction.
transaction_id Transaction identifier. Refer to “Overloaded Procedure
Common Arguments” on page 151 for more details.
bfm_id BFM identifier. Refer to “Overloaded Procedure Common
Arguments” on page 151 for more details.
path_id (Optional) Parallel process path identifier:
AXI4_PATH_0
AXI4_PATH_1
AXI4_PATH_2
AXI4_PATH_3
AXI4_PATH_4
Refer to “Overloaded Procedure Common Arguments” on
page 151 for more details.
tr_if Transaction signal interface. Refer to “Overloaded Procedure
Common Arguments” on page 151 for more details.
Returns
None
Kommentare zu diesen Handbüchern