DS824 Datasheet, PDF (17/55 Pages) Xilinx, Inc – LogiCORE IP AXI Bus Functional Models (v3.00.a)

LogiCORE IP AXI Bus Functional Models (v3.00.a)
AXI3 Master BFM Test Writing API
The channel level API for the AXI3 Master BFM is detailed in Table 10.
Table 10: Channel Level API for AXI3 Master BFM
API Task Name and Description
Inputs
SEND_WRITE_ADDRESS
Creates a write address channel transaction. This task returns
after the write address has been acknowledged by the slave.
This task emits a “write_address_transfer_complete” event
upon completion.
ID: Write Address ID tag
ADDR: Write Address
LEN: Burst Length
SIZE: Burst Size
BURST: Burst Type
LOCK: Lock Type
CACHE: Cache Type
PROT: Protection Type
SEND_WRITE_DATA
Creates a single write data channel transaction. The ID tag
should be the same as the write address ID tag it is associated
with. The data should be the same size as the width of the data
bus. This task returns after is has been acknowledged by the
slave. The data input is used as raw bus data, that is, no
realignment for narrow or unaligned data.
This task emits a “write_data_transfer_complete” event upon
completion.
Note: Should be called multiple times for a burst with correct
control of the LAST flag
ID: Write ID tag
STOBE: Strobe signals
DATA: Data for transfer
LAST: Last transfer flag
SEND_READ_ADDRESS
Creates a read address channel transaction. This task returns
after the read address has been acknowledged by the slave.
This task emits a “read_address_transfer_complete” event
upon completion.
ID: Read Address ID tag
ADDR: Read Address
LEN: Burst Length
SIZE: Burst Size
BURST: Burst Type
LOCK: Lock Type
CACHE: Cache Type
PROT: Protection Type
RECEIVE_READ_DATA
This task drives the RREADY signal and monitors the read
data bus for read transfers coming from the slave that have the
specified ID tag. It then returns the data associated with the
transaction and the status of the last flag. The data output here
is raw bus data, that is, no realignment for narrow or unaligned
data.
This task emits a “read_data_transfer_complete” event upon
completion.
Note: This would need to be called multiple times for a
burst > 1.
ID: Read ID tag
Also, the user must call the “remove_pending_transaction”
task when all data is received to ensure that the pending
transaction counter is decremented. This is done
automatically by the RECEIVE_READ_BURST and
RECEIVE_WRITE_RESPONSE channel level API tasks.
None
Outputs
None
None
DATA: Data transferred by
the slave
RESPONSE: The slave read
response from the following:
[OKAY, EXOKAY, SLVERR,
DECERR]
LAST: Last transfer flag
DS824 July 25, 2012
www.xilinx.com
17
Product Specification