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
    • Sequence Puzzles
    • Implication Puzzles
    • Temporal Corner Puzzles
    • Assertion Debug Puzzles
      • disable iff Abort Semantics
      • Multiclock Ack Visibility
      • Vacuity Hidden by Mode Gating
      • throughout Glitch Before Completion
      • within Timeout Window Escape
      • Intersect Requirement in Dual Checks
    • SVA Assertion Puzzles: Tricky Q&A
  • Functional Coverage Puzzles25
  • Logic & Aptitude Puzzles25
  • Scenario & Debug Puzzles25
  • Interview Prep: Puzzle Rounds5
  • DV Puzzle Cheatsheet
Loading lesson

‹Assertion Debug Puzzles
  1. Topics
  2. DV Interview Puzzles
  3. SVA Assertion Puzzles
  4. Assertion Debug Puzzles
  5. throughout Glitch Before Completion

VLSI DV Interview Puzzles · All levels

throughout Glitch Before Completion

Property intent: once start happens, valid must remain high throughout the done-arrival window (1 to 3 cycles). Timeline: C70 start=1 valid=1, C71 valid=1, C72 valid=0, C73 d1. Determine the verdict.

On this page

    Puzzle

    Difficulty: Hard · Puzzle 4 of 6 · Topic: Assertion Debug Puzzles

    Property intent: once start happens, valid must remain high throughout the done-arrival window (1 to 3 cycles). Timeline: C70 start=1 valid=1, C71 valid=1, C72 valid=0, C73 done=1. Determine the verdict.

    Code

    design.sv
    property p_valid_throughout_wait;
      @(posedge clk) start |-> valid throughout (##[1:3] done);
    endproperty

    Hint

    A single-cycle valid glitch inside the chosen window is enough to fail throughout.

    Step-by-step solution

    Diagram
    1) start at C70 triggers consequent.
    2) done matches via ##3 at C73.
    3) valid must hold continuously over the matched wait interval.
    4) valid is 0 at C72, violating throughout before done arrives.

    Answer

    Answer: FAIL - valid drops during the active wait window, so throughout constraint is broken.

    Why candidates get it wrong

    Debuggers often inspect only the done cycle and miss mid-window validity glitches.

    Interviewer follow-up

    If done occurred at C71 instead, would the same valid waveform still fail?

    Related topics

    • Back to Assertion Debug Puzzles

    • SVA Assertion Puzzles section

    Previous

    126 / 210

    Next: within Timeout Window Escape

    Up next

    Up nextwithin Timeout Window Escape

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • disable iff Abort Semantics
    • Multiclock Ack Visibility
    • Intersect Requirement in Dual Checks