
Mentor VIP AE AXI3/4 User Guide, V10.2b
538
VHDL AXI3 and AXI4 Monitor BFMs
get_read_or_write()
September 2013
get_read_or_write()
This nonblocking procedure gets the read_or_write field for a transaction that is uniquely
identified by the transaction_id field previously created by the create_monitor_transaction()
procedure.
AXI3 Example
-- Create a monitor transaction. Creation returns tr_id to identify
-- the transaction.
create_monitor_transaction(tr_id, bfm_index, axi_tr_if_0(bfm_index));
....
-- Get the read_or_write field of tr_id transaction.
get_read_or_write(read_or_write, tr_id, bfm_index,
axi_tr_if_0(bfm_index));
AXI4 Example
-- Create a monitor transaction. Creation returns tr_id to identify
Prototype
-- * = axi| axi4
-- ** = AXI | AXI4
get_read_or_write
(
read_or_write: out integer;
transaction_id : in integer;
bfm_id : in integer;
path_id : in *_path_t; --optional
signal tr_if : inout *_vhd_if_struct_t
);
Arguments
read_or_write Read or write transaction:
**_TRANS_READ = 0
**_TRANS_WRITE = 1
transaction_id Transaction identifier. Refer to “Overloaded Procedure Common
Arguments” on page 203 for more details.
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
read_or_write
Commentaires sur ces manuels