What this topic teaches

AXI-Lite & AXI-Stream is about converting a protocol rule into a measurable silicon contract. AXI-Lite removes bursts for control paths while AXI-Stream moves ordered data without addresses. The hard part is never the happy-path diagram; it is proving, under real traffic, which layer and which transaction broke the contract.

The senior-engineer question

When register response latency, stream bubble rate, packet boundary errors moves, can you identify the transaction, the protocol layer, the responsible owner, and the smallest experiment that proves the root cause?

PROTOCOL STACK VIEW — AXI-Lite & AXI-Stream

software / firmware intent
        |
        v
transaction semantics: address, ID, length, attributes, ordering
        |
        v
link / channel behavior: handshake, credits, backpressure, retries
        |
        v
physical or timing layer: clocking, reset, pins, lanes, PHY
        |
        v
observability: waveform, VIP transaction, counter, analyzer trace

Debug rule: never jump layers without carrying the transaction identity with you.

Picture the protocol

Start every study session by drawing the behavior before reading signals. The diagrams below are the mental models to reproduce on a whiteboard.

AXI-Stream packet with TLAST

AXI-STREAM PACKET

clk     _|‾|_|‾|_|‾|_|‾|_|‾|_|‾|_
tvalid  _|‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾|_____
tready  _|‾‾‾‾‾|__|‾‾‾‾‾‾‾‾‾|_____   (consumer backpressure mid-packet)
tdata    B0  B1  --  B2  B3
tlast    ________________|‾|_____   (marks end of packet)

Bubble: when tready=0, the same beat is held; data must not change.

AXI-Lite vs AXI-Full

AXI-LITE vs AXI-FULL

AXI-Lite : single beat, no burst, no ID reorder  -> control/registers
AXI-Full : bursts, IDs, reorder, outstanding      -> data movement

Use Lite for a register block; do not pay for burst logic you never use.

Transaction sequence

SEQUENCE — AXI-Lite & AXI-Stream

  initiator            interconnect/PHY            target
      |  request (id) ------->  |                     |
      |                         |  forward ----------> |
      |                         |                     | work
      |                         |  <---- response ---- |
      |  <----- complete ------ |                     |
      |
   metric captured here: register response latency, stream bubble rate, packet boundary errors

Who owns which layer

LAYER RESPONSIBILITY — AXI-Lite & AXI-Stream

layer          owns                         common failure
-----------    --------------------------   -----------------------
software       intent, ordering needs       wrong assumption
transaction    id/addr/len/attributes       ordering / outstanding
link/channel   handshake, credits, retry    backpressure / deadlock
physical       clock/reset/lanes/PHY        timing / training / SI
observability  waveform/log/counter         missing evidence

Evidence to collect

• Primary metric: register response latency, stream bubble rate, packet boundary errors.

• Primary artifact: TVALID/TREADY trace, TLAST packet log, control register access test.

• Owners to bring into review: IP owner, verification owner, driver owner.

• Spec clause or requirement ID for every claim.

• One traffic replay that fails and one reduced sequence that isolates the rule.

Ownership map

OWNERSHIP MAP — AXI-Lite & AXI-Stream

evidence type        owner who reads it
-----------------    ---------------------------
waveform/RTL        IP owner
spec/VIP            verification owner
firmware/system     driver owner

Rule: every metric must have a named owner before a review starts.

Subpages in this topic

Each topic is taught across mechanism, inputs/outputs, reports, debug, worked example, pitfalls, interview, checklist, theory, design space, expanded case study, walkthrough, comparison matrix, software view, and silicon PPA impact.

Key takeaways

• Carry transaction identity across waveform, log, counter, and spec view.

• Separate protocol violation, integration configuration, and performance bottleneck before proposing a fix.

• Draw the diagram first; the waveform should confirm the picture, not replace it.

Common pitfalls

• Debugging only one channel or layer.

• Treating a VIP error message as root cause instead of evidence.

• Quoting peak interface bandwidth without payload efficiency.

Protocol deep dive

AMBA is the on-chip lingua franca: APB for control, AHB for legacy bursts, AXI for high-performance coherent fabrics.

Concept diagram

AMBA INTEGRATION MAP

CPU --AXI--> NIC --AXI--> SRAM
  |              |
  +--AXI-Lite--> peripherals (GPIO, timers)
  +--AXI-Stream-> video pipe

Every bridge is a contract rewrite: width, ID, burst, cache attrs.

Metric graph

AXI CHANNEL ACTIVITY (mixed traffic)

AW+W     ████████████
AR       ████████████████
R        ██████████████
B        ████████

Read-heavy phase: AR/R dominate; write resp may look idle while system is healthy.

Metrics and artifacts to collect

• AR/AW/R/B channel utilization

• write resp latency

• read OSTD depth

• SLVERR/DECERR count

• bridge hang log

Mini case study

Write burst hung because W beats arrived before AW for a narrow bridge that reordered channels. VIP flagged nothing until full-system traffic interleaved reads and writes.

Debug branches

• Hung write: verify AW/W ordering and wlast alignment.

• Hung read: check arready stall and rlast per ID.

• Decode errors: address map vs interconnect route table.

Senior review question

Ask: what is the first transaction that deviates, and which spec rule does it test?

Key takeaways

• Connect every protocol claim to a transaction identity and measurable metric.

• Store the artifact (waveform, log, counter) next to every signoff decision.

Common pitfalls

• Debugging timeouts without finding the first bad transaction.

• Quoting peak bus width without payload efficiency and retry overhead.

• Treating VIP compliance as a substitute for system integration replay.