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

LogiCORE IP AXI Bus Functional Models (v3.00.a)
Table 16: Channel Level API for AXI4 Slave BFM (Cont’d)
API Task Name
Inputs
Outputs
RECEIVE_WRITE_DATA
This task drives the WREADY signal and monitors the
write data bus for write transfers coming from the master.
It then returns the data associated with the transaction
and the status of the last flag. NOTE: This would need to
be called multiple times for a burst > 1.
This task emits a “write_data_transfer_complete” event
upon completion.
None
DATA: Data transferred from
the master
STRB: Strobe signals used to
validate the data
LAST: Last transfer flag
WUSER: Write User Defined
Signals
RECEIVE_WRITE_BURST
This task receives and processes a write burst on the
write data channel. It does not wait for the write address
transfer to be received. This task uses the
RECEIVE_WRITE_DATA task from the channel level API.
This task returns when the complete write burst is
complete.
This task automatically supports narrow transfers and
unaligned transfers; that is, this task aligns the output data
with the burst so the final output data should only contain
valid data (up to the size of the burst data).
This task emits a “write_data_burst_complete” event
upon completion.
ADDR: Write Address
LEN: Burst Length
SIZE: Burst Size
BURST: Burst Type
DATA: Data received from the
write burst
DATASIZE: The size in bytes of
the valid data contained in the
output data vector
WUSER: This is a vector that is
created by concatenating all
master write user signal data
together
SEND_READ_BURST
This task does a read burst on the read data lines. It does
not wait for the read address transfer to be received. This
task uses the SEND_READ_DATA task from the channel
level API.
This task returns when the complete read burst is
complete.
This task automatically supports the generation of narrow
transfers and unaligned transfers; that is, this task aligns
the input data with the burst so data padding is not
required.
This task emits a “read_data_burst_complete” event upon
completion.
ID: Read ID tag
ADDR: Read Address
LEN: Burst Length
SIZE: Burst Size
BURST: Burst Type
LOCK: Lock Type
DATA: Data to be sent over the
burst
RUSER: This is a vector that is
created by concatenating all
required slave read user signal
data together
None
SEND_READ_BURST_RESP_CTRL
This task does a read burst on the read data lines. It does
not wait for the read address transfer to be received. This
task uses the SEND_READ_DATA task from the channel
level API.
This task returns when the complete read burst is
complete.
This task automatically supports the generation of narrow
transfers and unaligned transfers; that is, this task aligns
the input data with the burst so data padding is not
required.
This task emits a “read_data_burst_complete” event upon
completion.
ID: Read ID tag
ADDR: Read Address
LEN: Burst Length
SIZE: Burst Size
BURST: Burst Type
DATA: Data to be sent over the
burst
RESPONSE: This is a vector that
should contain all of the desired
responses for each read data
transfer
RUSER: This is a vector that is
created by concatenating all
required slave read user signal
data together
None
DS824 July 25, 2012
www.xilinx.com
28
Product Specification