
Mentor VIP AE AXI3/4 User Guide, V10.2b
446
VHDL AXI3 and AXI4 Slave BFMs
execute_read_data_phase()
September 2013
execute_read_data_phase()
This procedure executes a read data phase that is uniquely identified by the transaction_id
argument previously created by the create_slave_transaction() procedure. This phase can be
blocking (default) or nonblocking, defined by the transaction record operation_mode field.
The execute_read_data_phase() sets the RVALID protocol signal at the appropriate time
defined by the transaction record data_valid_delay field and sets the data_beat_done array
index element field to 1 when the phase completes. If this is the last data phase (beat) of the
burst, it also sets the transaction_done field on completion.
Prototype
-- * = axi| axi4
-- ** = AXI | AXI4
procedure execute_read_data_phase
(
transaction_id : in integer;
index : in integer; --optional
bfm_id : in integer;
path_id : in *_path_t; --optional
signal tr_if : inout *_vhd_if_struct_t
);
Arguments
transaction_id Transaction identifier. Refer to “Overloaded Procedure
Common Arguments” on page 203 for more details.
index (Optional) Data phase (beat) number.
bfm_id BFM identifier. Refer to “Overloaded Procedure Common
Arguments” on page 203 for more details.
path_id (Optional) Parallel process path identifier:
**_PATH_0
**_PATH_1
**_PATH_2
**_PATH_3
**_PATH_4
Refer to “Overloaded Procedure Common Arguments” on
page 203 for more details.
tr_if Transaction signal interface. Refer to “Overloaded Procedure
Common Arguments” on page 203 for more details.
Returns
None
Commenti su questo manuale