Ready handshake signal delay transaction fields, Transaction done, Table 7-3. master and slave *_ready_delay fields – Altera Mentor Verification IP Altera Edition AMBA AXI4-Lite User Manual
Page 149
VHDL API Overview
Operational Transaction Fields
Mentor Verification IP AE AXI4-Lite User Guide, V10.3
149
April 2014
*READY Handshake Signal Delay Transaction Fields
The transaction record contains a *_ready_delay transaction field for each of the five protocol
channels to store the delay value between the assertion of the *VALID and *READY
handshake signals for the channel.
specifies the *_ready_delay field corresponding to
the *READY signal delay.
Transaction Done
There is a transaction_done transaction field in each transaction that indicates when the
transaction has completed.
In a BFM test program, you call the respective BFM get_transaction_done() procedure to
investigate whether a read or write transaction has completed.
Table 7-3. Master and Slave *_ready_delay Fields
Signal
Operational Transaction Field
AWREADY
address_ready_delay
WREADY
data_ready_delay
BREADY
write_response_ready_delay
ARREADY
address_ready_delay
RREADY
data_ready_delay