
VHDL AXI3 and AXI4 Master BFMs
execute_write_data_phase()
Mentor VIP AE AXI3/4 User Guide, V10.2b
321
September 2013
execute_write_data_phase()
This procedure executes a write data phase that is uniquely identified by the transaction_id
argument and previously created by the create_write_transaction() procedure. This phase can
be blocking (default) or nonblocking, defined by the transaction record operation_mode field.
The execute_write_data_phase() sets the WVALID protocol signal at the appropriate time
defined by the transaction record field data_valid_delay array index element and sets the
data_beat_done array index element to 1 when the phase completes.
Prototype
-- * = axi| axi4
-- ** = AXI | AXI4
procedure execute_write_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