How Does AXI4-Lite Work? Channels, Handshakes, Timing
AXI splits every transfer across five independent channels: write address (AW), write data (W), write response (B), read address (AR) and read data (R). Each channel has the same handshake: the sender raises VALID with its information, the receiver raises READY when it can accept, and the transfer happens on the clock edge where both are high. AXI4-Lite is the simple subset for control registers: one 32-bit or 64-bit data transfer per transaction, no bursts, every byte lane selectable with a write strobe.
What you'll learn
- The five channels and which way each goes
- The VALID and READY handshake, and its two rules
- A write and a read, cycle by cycle
- Responses: OKAY and SLVERR
- What AXI4-Lite leaves out of full AXI4
The handshake rules
- A transfer happens on a rising clock edge where VALID and READY are both high.
- Once a source raises VALID it must keep VALID high, and the information stable, until the handshake happens. It may not wait for READY before raising VALID.
- A destination may wait for VALID before raising READY, and may raise READY early.
- The channels are independent: a slave must accept write data before, with or after the write address. The AW and W handshakes can happen in any order.
A write, cycle by cycle
This trace is from the peripheral built in the project post, simulated in Icarus Verilog. The master offers the address and the data together; the slave raises both READY signals one clock later; once it holds both, it raises BVALID with an OKAY response, and the master takes it with BREADY.
A read, cycle by cycle
The master offers the address on AR; the slave accepts it, then returns the data on R with RVALID and holds it until RREADY. Reading register 0x8 after writing 6 and 7 returns their product, 42.
Responses
Every write gets a response on B and every read carries one on R: OKAY (00) for success, SLVERR (10) when the slave refuses, for example a write to a read-only register, and DECERR (11), usually returned by the interconnect when no slave owns the address. The project's peripheral answers a write to its PRODUCT register with SLVERR.
AXI4-Lite vs AXI4
| Feature | AXI4 | AXI4-Lite |
|---|---|---|
| Bursts | Up to 256 beats | None: one beat per transaction |
| Data width | 32 to 1024 bits | 32 or 64 bits |
| Transaction IDs | Yes, for out-of-order responses | No |
| Write strobes | Yes | Yes |
| Typical use | Memory, DMA, high bandwidth | Control and status registers |
Common mistakes
- Waiting for READY before raising VALID. That can deadlock with a slave that waits for VALID.
- Changing data while VALID is high and READY is low.
- Assuming the address arrives before the data. A slave must accept them in either order.
- Dropping BVALID or RVALID before the master's READY.
- Treating a byte address as a register index: register n is at byte address 4n on a 32-bit bus.
Check your understanding
- Q1. On which edge does a transfer happen? Answer: a rising edge where VALID and READY are both high.
- Q2. Can a master wait for AWREADY before raising WVALID? Answer: it may, but the slave must not depend on that order; a correct slave accepts W before, with or after AW.
- Q3. A 32-bit AXI4-Lite slave has registers at 0x0, 0x4, 0x8 and 0xC. Which address bits pick the register? Answer: bits 3 and 2; bits 1 and 0 select a byte within the word.
The SoC series
Related
Last verified
Both traces were redrawn from an Icarus Verilog 12 simulation of scripts/soc/axil_mult.v on 17 November 2026; the handshake rules were checked against the AMBA AXI specification.