
VHDL API Overview
Creating Transactions
Mentor VIP AE AXI3/4 User Guide, V10.2b
193
September 2013
The master BFM API allows you to create a master transaction by providing only the address
and burst length arguments for a read, or write, transaction. All other protocol transaction fields
automatically default to legal protocol values to create a complete master transaction record.
Refer to the create_read_transaction() and create_write_transaction() procedures for default
protocol read and write transaction field values.
The slave BFM API allows you to create a slave transaction by providing no arguments. All
protocol transaction fields automatically default to legal protocol values to create a complete
slave transaction record. Refer to the create_slave_transaction() procedure for default protocol
transaction field values.
The monitor BFM API allows you to create a slave transaction by providing no arguments. All
protocol transaction fields automatically default to legal protocol values to create a complete
address_ready_delay An integer to hold the delay value of the address channel
AWREADY and ARREADY signals (measured in ACLK cycles)
for a read or write transaction, respectively.
data_ready_delay An unsized array of integers to hold the delay values of the
data channel WREADY and RREADY signals (measured in
ACLK cycles) for a read or write transaction, respectively.
write_response_ready_delay An integer to hold the delay value of the write response
channel BREADY signal (measured in ACLK cycles) for a write
transaction.
gen_write_strobes Automatically correct write strobes flag. Refer to Automatic
Correction of Byte Lane Strobes for details.
operation_mode An enumeration to hold the operation mode of the transaction.
The two types of operation_mode are:
**_TRANSACTION_NON_BLOCKING
**_TRANSACTION_BLOCKING
delay_mode (AXI3) An enumeration to hold the delay mode control flag.
The types of delay_mode are:
AXI_VALID2READY
AXI_TRANS2READY
Refer to AXI3 BFM Delay Mode for details.
write_data_mode (AXI3) An enumeration to hold the write data mode control flag.
The types of write_data_mode are:
**_DATA_AFTER_ADDRESS
**_DATA_WITH_ADDRESS
data_beat_done An unsized bit array to hold the done flag for each beat in a
read or write data burst when it has completed.
transaction_done A bit to hold the done flag for a transaction when it has
completed.
Table 7-1. Transaction Fields (cont.)
Transaction Field Description
Kommentare zu diesen Handbüchern