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 Puzzle Bank
  • SystemVerilog Language Puzzles25
  • Difficulty Guide
  • Full Topic Map
  • Interview-Day Tips
  • OOP & Testbench Puzzles25
  • Concurrency & Timing Puzzles25
  • Randomization & Constraint Puzzles25
  • SVA Assertion Puzzles25
  • Functional Coverage Puzzles25
  • Logic & Aptitude Puzzles25
  • Scenario & Debug Puzzles25
    • Testbench Debug Puzzles: Why Did the Test Hang?
    • Deadlock Scenario Puzzles: Objection and Phase Stalls
    • Scoreboard Puzzles: Mismatch or Ordering Bug?
    • Real Interview Rounds: End-to-End Debug Walkthrough
      • Round Walkthrough: Sequencer Waits for item_done
      • Round Walkthrough: Objection Deadlock with Clean Waves
      • Round Walkthrough: APB Reads Return Previous Data
      • Round Walkthrough: Out-of-Order Channel Mismatch
      • Round Walkthrough: Rare Parallel Deadlock
      • Round Walkthrough: End-of-Test False Fail
    • Scenario & Debug Puzzles: Tricky Q&A
  • Interview Prep: Puzzle Rounds5
  • DV Puzzle Cheatsheet
Loading lesson

‹Real Interview Rounds: End-to-End Debug Walkthrough
  1. Topics
  2. DV Interview Puzzles
  3. Scenario & Debug Puzzles
  4. Real Interview Rounds: End-to-End Debug Walkthrough
  5. Round Walkthrough: APB Reads Return Previous Data

VLSI DV Interview Puzzles · All levels

Round Walkthrough: APB Reads Return Previous Data

Interview trace: every APB read returns previous address data. You must separate protocol violation from monitor bug in five clear steps.

On this page

    Puzzle

    Difficulty: Medium · Puzzle 3 of 6 · Topic: Real Interview Rounds: End-to-End Debug Walkthrough

    Interview trace: every APB read returns previous address data. You must separate protocol violation from monitor bug in five clear steps.

    Code

    design.sv
    1
    2
    3
    4
    5
    6
    7
    always @(posedge pclk) begin
      if (start_read) begin
        psel   <= 1'b1;
        penable<= 1'b1;
        paddr  <= req.addr; // updated too late
      end
    end

    Hint

    APB setup and enable phases must be distinct and ordered.

    Step-by-step solution

    Diagram
    1) Symptom: read data lags by one transfer under back-to-back traffic.
    2) Hypotheses: APB phase timing violation, monitor sampling skew, or DUT pipeline bug.
    3) Instrumentation: annotate setup/access phase wave markers and compare against APB spec.
    4) Root cause: paddr and penable are asserted in same cycle, violating setup-before-enable timing.
    5) Fix + validation: drive paddr/psel in setup cycle, penable in next cycle; rerun directed read sequence.

    Answer

    Answer: Actual bug: APB driver violates setup/access sequencing, so DUT samples stale address. Fix: split drive into correct two-phase APB timing.

    Why candidates get it wrong

    Many candidates inspect scoreboard first; this is stimulus protocol timing.

    Interviewer follow-up

    Which assertion would you write to enforce APB setup/access sequencing in future regressions?

    Related topics

    • Back to Real Interview Rounds: End-to-End Debug Walkthrough

    • Scenario & Debug Puzzles section

    Previous

    200 / 210

    Next: Round Walkthrough: Out-of-Order Channel Mismatch

    Up next

    Up nextRound Walkthrough: Out-of-Order Channel Mismatch

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Round Walkthrough: Sequencer Waits for item_done
    • Round Walkthrough: Rare Parallel Deadlock
    • Round Walkthrough: End-of-Test False Fail