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

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Puzzle Bank
  • SystemVerilog Language Puzzles25
  • Difficulty Guide
  • Full Topic Map
  • Interview-Day Tips
  • Study Route: One Week Before the Interview
  • Study Route: Two Weeks
  • Study Route: Four Weeks (Full Course)4
  • OOP & Testbench Puzzles25
  • Concurrency & Timing Puzzles25
  • Randomization & Constraint Puzzles25
  • SVA Assertion Puzzles25
  • Functional Coverage Puzzles25
    • Covergroup and Coverpoint Puzzles
    • Cross Coverage Puzzles
    • Coverage Options Puzzles
    • Coverage Closure and Sampling Timing Puzzles
      • Sampling region off-by-one on state bins
      • Unreachable bin from stimulus constraints
      • Sampling on a derived clock sees the updated value
      • Reset-time samples filtered by iff
      • Unreachable cross tuple from protocol rules
      • at_least threshold causes closure plateau
    • Functional Coverage Puzzles: Tricky Q&A
  • Logic & Aptitude Puzzles25
  • Scenario & Debug Puzzles25
  • UVM Testbench Puzzles25
  • Clock, Reset & CDC Puzzles25
  • Bus and Interface Protocol Puzzles25
  • Interview Prep: Puzzle Rounds7
  • DV Puzzle Cheatsheet
Loading lesson

←Coverage Closure and Sampling Timing Puzzles
  1. Topics
  2. DV Interview Puzzles
  3. Functional Coverage Puzzles
  4. Coverage Closure and Sampling Timing Puzzles
  5. at_least threshold causes closure plateau
On this page

    VLSI DV Interview PuzzlesAll levels

    at_least threshold causes closure plateau

    Bins are touched but report remains 50%. Compute exact status and next action. Options set: option.at_least = 5 on cp_lat (weight = 1).

    Puzzle

    Difficulty: Medium · Puzzle 6 of 6 · Topic: Coverage Closure and Sampling Timing Puzzles

    Bins are touched but report remains 50%. Compute exact status and next action. Options set: option.at_least = 5 on cp_lat (weight = 1).

    Code

    design.sv
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    covergroup cg with function sample(bit [1:0] latency);
      cp_lat: coverpoint latency {
        option.at_least = 5;
        bins fast = {1};
        bins slow = {2};
      }
    endgroup
    
    initial begin
      cg c = new();
      repeat (5) c.sample(1);
      repeat (2) c.sample(2);
    end

    Hint

    Touch count is not enough; threshold controls covered/not-covered state.

    Step-by-step solution

    Diagram
    1) fast bin has 5 hits so it is covered.
    2) slow bin has 2 hits, below at_least=5, so not covered.
    3) Covered bins are 1 of 2 -> 50%.
    4) Need 3 more slow samples to close cp_lat to 100%.

    Answer

    Answer: Coverage is 50% because only fast meets threshold. slow needs 3 more hits.

    How this was checked

    Checked by running a model of the rule in a Python model. A model of the at_least rule: slow has 2 hits, below 5, so only fast is covered.

    Why candidates get it wrong

    Seeing both bins in the log and assuming both are covered: with at_least = 5 a bin hit 2 times counts as not covered, so the report stays at 50% while slow looks touched.

    Interviewer follow-up

    How would you bias constraint distributions to close slow without overfitting stimulus? Model answer: Leave the base random test alone and add a closure test or soft constraint that raises the weight of latency 2 (for example a dist), so slow gets at least 3 more hits while fast keeps its natural mix. Check that the new hits come from varied scenarios, not one repeated directed pattern.

    Say it out loud

    I would compare the hit counts with the threshold. With at_least of five, only the fast bin meets it, so coverage is 50 percent, and the slow bin needs three more hits. The trap is seeing both bins touched in the log and calling them covered. Next I would check whether the threshold is justified and bias stimulus toward the slow case.

    Related topics

    • Weights, Goals & at_least

    • Closing Techniques

    • Back to Coverage Closure and Sampling Timing Puzzles

    • Functional Coverage Puzzles section

    Previous

    159 / 293

    Next: Functional Coverage Puzzles: Tricky Q&A

    Up next

    Up nextFunctional Coverage Puzzles: Tricky Q&A

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Sampling region off-by-one on state bins
    • Unreachable bin from stimulus constraints
    • Sampling on a derived clock sees the updated value