Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Paths
  • Concept Map
  • How to Read the Diagrams
  • Part 0: What Is a Protocol?10
  • Part 1: Timing and Clocking11
  • Part 2: Encoding and Framing12
  • Part 3: Handshakes13
  • Part 4: Flow Control17
  • Part 5: Transactions19
  • Part 6: Concurrency and Performance17
  • Part 7: Ordering13
  • Part 8: Sharing and Arbitration12
  • Part 9: Deadlock and Liveness13
  • Part 10: Reliability and Recovery20
  • Part 11: Bring-Up and Link Management10
  • Part 12: Power8
  • Part 13: Shared State and Coherence9
  • Part 14: Security and Isolation7
  • Part 15: Specifying and Verifying11
  • Part 16: Protocols Dissected17
  • Part 17: Capstones5
  • Part 18: Interview Preparation6
    • The Reasoning Framework
    • Question Bank: Foundation
    • Question Bank: Senior
    • Question Bank: Principal
    • Whiteboard Drills
    • System Design Questions
Loading lesson

‹Part 18: Interview Preparation
  1. Topics
  2. First Principles of Hardware Protocols
  3. Part 18: Interview Preparation
  4. Whiteboard Drills

Part 18 · Interview Preparation · Working (W)

Whiteboard Drills

Draw-it drills for interviews: a valid/ready transfer with a stall, a credit loop, ACK/NAK replay, an AXI burst and a round-robin arbiter. Draw each from memory, then compare with the model drawing and the points it must show.

On this page

    Note

    Level: Working (W) · Answers: Can you explain it under pressure?

    Before this: The Reasoning Framework

    "Draw it for me" is the fastest way for an interviewer to see whether you understand a mechanism. A good drawing is small, labelled, shows time running in one direction, and includes the corner case that makes the mechanism necessary. Draw each of these from memory in under three minutes before looking.

    Can you draw the core mechanisms from memory, with the case that matters?

    Drill 1: a valid/ready transfer with a stall

    Draw clk, valid, ready and data for three transfers, with ready low for two cycles during the second.

    Check yourself What must the drawing show?

    Transfers only on cycles where valid and ready are both high; during the stall, valid stays high and data stays unchanged; valid rose without waiting for ready. Label which cycles transfer.

    Drill 2: a credit loop

    The sender's counter falls with each flit and rises with each returned credit; it can never send more than the receiver has room for.
    Check yourself What must the drawing show, and what number should you say?

    Initial credits equal to buffer slots; decrement per flit; increment per returned credit; the round trip from sending a flit to getting its credit back. Say: full throughput needs buffer ≥ rate × round trip.

    Drill 3: ACK/NAK replay

    The receiver accepts only in-sequence good packets, NAKs once with the last good sequence number, and the sender replays everything after it from its replay buffer.
    Check yourself What must the drawing show?

    Sequence numbers, the replay buffer holding unacknowledged packets, discard of out-of-sequence packets, cumulative ACK, and the replay timer for lost ACKs. Say the window limit: 2^n − 1 for go-back-N.

    Drill 4: an AXI read burst

    Draw ARVALID, ARREADY, the address, RVALID, RREADY, RDATA and RLAST for a 4-beat burst with one stall on R.

    Check yourself What must the drawing show?

    One address handshake for the whole burst; four data beats, each on an RVALID and RREADY cycle; the stalled beat held stable; RLAST on beat 4; the read ID on each beat if asked about multiple outstanding.

    Drill 5: a round-robin arbiter

    Draw four requesters, the grant sequence when requesters 0, 2 and 3 request continuously, and the priority pointer.

    Check yourself What must the drawing show?

    Grants 0, 2, 3, 0, 2, 3...; the pointer moving to just after the last winner; requester 1 skipped because it is not requesting; the bound: each requester waits at most three other grants.

    Drawing habits

    • Time in one direction (left to right for waveforms, top to bottom for sequences).

    • Label every signal and every arrow; number the cycles you talk about.

    • Include the corner case: the stall, the error, the wrap-around, the empty pool.

    • Say the number that sizes the mechanism while you draw.

    Why this matters

    Senior lens. Practise until each drawing takes under a minute. In interviews and in design reviews alike, a correct small drawing with the critical corner case settles questions that paragraphs of explanation do not, and it shows you can think in time, which is what protocols are about.

    Key takeaways

    • Draw the five core mechanisms from memory: handshake, credits, replay, burst, arbitration.

    • Every drawing includes the corner case that makes the mechanism necessary.

    • State the sizing number (round trip, window, wait bound) while drawing.

    Keep going

    Next: Lesson 18.6, System Design Questions. "Design the interconnect for X", walked through end to end.

    Related topics

    • Part 18 overview: Interview Preparation

    Previous

    233 / 234

    Next: System Design Questions

    Up next

    Up nextSystem Design Questions

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • The Reasoning Framework
    • Question Bank: Foundation
    • Question Bank: Senior