Editing Advanced eXtensible Interface (section)

==== Reads ====
[[File:AXI read transaction.svg|thumb|upright=2.25|Example of an AXI read transaction. The initiator requests 4 beats (ARLEN + 1<ref name="axlen">{{cite web |author1=Arm Holdings |title=AMBA AXI and ACE Protocol Specification |url=https://static.docs.arm.com/ihi0022/e/IHI0022E_amba_axi_and_ace_protocol_spec.pdf |website=developer.arm.com |access-date=5 July 2019 |page=44 |language=en}}</ref>) of 4 Bytes each starting from address 0x0 with INCR type. The target returns 0x10 for address 0x0, 0x11 for address 0x4, 0x12 for address 0x8 and 0x13 for address 0xc, all with the OKAY status. Only the most relevant signals are shown here.]]

To start a read transaction, the initiator has to provide on the Read address channel:
* the start address on ARADDR
* the burst type, either FIXED, INCR or WRAP, on ARBURST (if present)
* the burst length on ARLEN (if present).
Additionally, the other auxiliary signals, if present, are used to define more specific transfers.

After the usual ARVALID/ARREADY handshake, the target has to provide on the Read data channel:
* the data corresponding to the specified address(es) on RDATA
* the status of each beat on RRESP
plus any other optional signals.
Each beat of the target's response is done with a RVALID/RREADY handshake and, on the last transfer, the target has to assert RLAST to inform that no more beats will follow without a new read request.