AMBA AXI · Module 20
AXI Interview Checklist
A last-mile revision checklist before an AXI interview — the must-know fundamentals, the most-probed handshake and ordering rules, the design and verification points, and the high-frequency questions and myths, distilled into a final pre-interview pass so you walk in able to articulate the essentials crisply.
The previous checklists are for building — this one is for you, the night before an AXI interview. The AXI interview checklist is a last-mile revision list: the must-know points distilled into a final pass so the essentials are fresh and articulable. It's not for learning AXI (Modules 1–18 did that) — it's for revision: a compact set of the highest-frequency, highest-impact items to refresh before you walk in, organized so you can self-check ("can I state the handshake rule crisply? the ordering rules? size outstanding depth?"). This chapter distills the interview-mastery module (18) and the whole curriculum into a final pre-interview pass: the fundamentals, the most-probed rules, the design/verification essentials, and the myths to never state.
1. The Must-Know Fundamentals
Refresh the foundation — the answers you must give instantly. What AXI is: a high-performance AMBA bus that decouples address from data and supports multiple outstanding, out-of-order transactions, for high throughput. The five channels: AW, W, B (write) and AR, R (read) — independent, each with a VALID/READY handshake. The handshake: a beat transfers when both VALID and READY are high on a rising edge; payload held stable until accepted. Reads vs. writes: writes use three channels with one aggregated B; reads use two channels with per-beat RRESP. If any of these isn't instant and crisp, revise it first — they're the warm-up filters that gate everything else.
2. The Most-Probed Rules
These are the items interviewers push hardest — know each cold with its why. The handshake asymmetry (the #1 probe): READY may depend on VALID, but VALID must never depend combinationally on READY — else deadlock. The ordering rules: same-ID responses in order, different-ID in any order — and IDs are what enable out-of-order completion. The 4 KB rule: a burst must not cross a 4 KB boundary, because that's the minimum page size (one slave/one set of attributes). Burst span: (LEN+1) << SIZE; per-beat increment 1 << SIZE. WSTRB: per-byte write-enable for partial writes. For each, rehearse the crisp statement and the one-level-deeper why, because that's exactly where the interviewer probes.
3. The Design and Verification Essentials
Refresh the build-and-prove points for design/verification questions. Design: the structured approach (clarify → interface → FSM → handshake → corners); the canonical blocks (AXI4-Lite slave = two FSMs; skid buffer = two registers, the minimum for fully-registered full-throughput); the instincts (channel independence, VALID⊥READY, corner-awareness, reuse). Verification: the four layers (assertions = compliance, monitor = reconstruct, scoreboard = correctness, coverage = completeness); the two distinctions (compliance ≠ correctness, checking ≠ coverage). Performance: bandwidth = width × frequency × efficiency; Little's Law (outstanding ≈ bandwidth × latency); latency and throughput decoupled by outstanding. These cover the design, verification, and performance question rounds.
4. The Myths to Never State, and the Delivery
Finally, refresh the myths to never state (the confident-wrong traps) and the delivery discipline. The myths: "VALID waits for READY" (no — the asymmetry), "all responses ordered" (no — same-ID only), "a clean checker means verified" (no — compliance ≠ correctness), "high latency = low throughput" (no — decoupled by outstanding), "exclusive locks the bus" (no — that's locked access). The delivery: lead with the precise core, add the why, stop, go deeper on probe; avoid rambling and vague-but-confident; and when unsure, reason aloud from a known principle rather than guessing. A confident-wrong answer is the worst outcome — knowing the myths and the calibrated-reasoning habit is your insurance.
5. Common Misconceptions
6. Debugging Insight
7. Verification Insight
8. Interview Questions
9. Summary
The AXI interview checklist is the last-mile revision pass — for refreshing, not learning — distilling the highest-frequency, highest-impact items so they're fresh and articulable. Revise by round: fundamentals (what AXI is, the five channels, the handshake, reads vs. writes — the warm-up filters to have instant); most-probed rules (the handshake asymmetry as the #1 — READY may depend on VALID, VALID must never depend on READY, else deadlock; same-ID ordered / different-ID free; the 4 KB rule; burst span (LEN+1) << SIZE; Little's Law; WSTRB); design/verification/performance essentials (the design approach and canonical blocks; the four verification layers and two distinctions — compliance≠correctness, checking≠coverage; bandwidth = width × frequency × efficiency and latency/throughput decoupled by outstanding); and the myths to never state (VALID-waits-for-READY, all-ordered, checker=verified, latency=throughput, exclusive-locks-the-bus) with their corrections.
The disciplines: revise, don't cram (refresh what you know, prioritizing fundamentals — highest failure cost, most tempting to skip); revise the why, not just the what (interviewers probe the reason; memorized phrases collapse on the first probe); and rehearse the delivery and calibrated-reasoning habit (lead-core-add-why-stop; when unsure, reason aloud from a principle rather than guessing, since confident-wrong is the worst outcome). Use the checklist as a self-check the day before — test each item, patch your weak spots, rehearse delivery — because the day-before bottleneck is recall-and-articulation, not understanding, and readiness is articulation-of-understanding-under-pressure, a distinct skill from the knowledge itself. This is the operational complement to the deep understanding Modules 1–19 built and the communication Module 18 taught: walk in with the essentials fresh, the why ready, the calculations drillable, the myths avoided, and the delivery practiced. Next, the final chapter distills the single most valuable list — the common mistakes to never make, across design, verification, and interviews alike.
10. What Comes Next
You're now interview-ready; the final chapter is the most valuable list of all:
- 20.5 — Common Mistakes Checklist (coming next) — the recurring AXI mistakes to never make, in design, verification, debugging, and interviews — the curriculum's closing distillation of what most often goes wrong and how to avoid it.
Previous: 20.3 — AXI Integration Checklist. Related: 18.1 — Beginner Interview Questions for the fundamentals, 18.8 — Tricky Misconceptions for the myths, and 3.5 — Handshake Dependency & Deadlock Rules for the #1-probed asymmetry.
Continue learning
Related tutorials
- Related topic
AMBA — AHB · APB · AXI
ARM's AMBA family — channels, handshakes, ordering rules, and verification strategy.
- Related topic
AXI4 Write Channel — AW, W & B Handshake
The AMBA 5 AXI4 write path — AW/W/B channels, the VALID/READY handshake, channel-dependency rules, and BRESP write-response semantics.
- Related topic
AHB Interview Checklist
A last-mile revision checklist before an AHB interview — the must-knows to have ready. Seven areas: (1) the pipeline (the #1 fact — the address phase is one cycle ahead of the data phase; almost everything traces back to it); (2) HREADY (slave-driven, shared, inserts wait states, the master waits — not master-driven); (3) bursts (one address phase + beats with a defined pattern — not repeated singles); (4) the two-cycle ERROR (and the why — the pipeline); (5) arbitration (HBUSREQ/HGRANT/HMASTER; grant one cycle ahead, ownership at a boundary — grant is not ownership); (6) the misconceptions to correct; (7) the answer framework (FACT then WHY then EXAMPLE, and convey the pipeline across answers). The single most important thing to have ready is the pipeline — conveying it is the strongest signal of real understanding.
- Related topic
Beginner AXI Interview Questions
The fundamental AXI questions interviewers open with, and how to answer them crisply — what AXI is and why, the five channels, the VALID/READY handshake, reads vs. writes, and the one rule that must never be broken — with the structure of a strong beginner answer and the traps that signal a shallow one.
Standards & specifications
- Governing standard
- Arm AMBA AXI Protocol Specification (IHI 0022)(opens Arm in a new tab)
Defines the AXI channels, handshake and ordering rules. RTL structure, interconnect topology and verification strategy are design choices this specification does not mandate.
This page also covers RTL structure, verification approach and debugging technique. Those are engineering practice built on the standard, not requirements the standard itself imposes.
Where this fits
Part of the AMBA AXI curriculum.
