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
      • Named cross bins that group tuples
      • Pure auto cross count
      • Explicit ignore_bins instead of a default catch-all
      • intersect filter removes one tuple
      • illegal cross tuple does not close coverage
      • Three-way cross with overlapping ignore_bins
    • Coverage Options Puzzles
    • Coverage Closure and Sampling Timing Puzzles
    • 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

←Cross Coverage Puzzles
  1. Topics
  2. DV Interview Puzzles
  3. Functional Coverage Puzzles
  4. Cross Coverage Puzzles
  5. Pure auto cross count
On this page

    VLSI DV Interview PuzzlesAll levels

    Pure auto cross count

    No ignores, no custom bins. Compute auto cross denominator and percentage. Options: none set (all defaults: at_least = 1, weight = 1, auto_bin_max = 64).

    Puzzle

    Difficulty: Easy · Puzzle 2 of 6 · Topic: Cross Coverage Puzzles

    No ignores, no custom bins. Compute auto cross denominator and percentage. Options: none set (all defaults: at_least = 1, weight = 1, auto_bin_max = 64).

    Code

    design.sv
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    covergroup cg with function sample(bit [1:0] a, bit b);
      cp_a: coverpoint a {
        bins a0 = {0};
        bins a1 = {1};
        bins a2 = {2};
      }
      cp_b: coverpoint b {
        bins b0 = {0};
        bins b1 = {1};
      }
      x_ab: cross cp_a, cp_b;
    endgroup
    
    initial begin
      cg c = new();
      c.sample(0,0);
      c.sample(1,1);
      c.sample(2,1);
      c.sample(2,0);
    end

    Hint

    Cross denominator is product of coverpoint bin counts.

    Step-by-step solution

    Diagram
    1) cp_a has 3 bins and cp_b has 2 bins -> auto cross has 6 bins.
    2) Hit tuples are (a0,b0), (a1,b1), (a2,b1), (a2,b0) -> 4 unique cross bins hit.
    3) Coverage = 4/6 = 66.67%.

    Answer

    Answer: Cross denominator is 6 bins and achieved coverage is 66.67%.

    How this was checked

    Checked by running a model of the rule in a Python model. A model of the auto-cross rule: 3 x 2 gives 6 tuples and 4 distinct ones are hit.

    Why candidates get it wrong

    Judging by the coverpoints instead of the cross: cp_a is 3/3 = 100% and cp_b is 2/2 = 100%, yet the cross is only 4/6 = 66.67%. Full coverage of each variable says nothing about the combinations.

    Interviewer follow-up

    Which exact two tuples are still uncovered after the shown traffic? Model answer: (a0,b1) and (a1,b0): the six tuples are a0/a1/a2 x b0/b1 and the four hit are (a0,b0), (a1,b1), (a2,b1), (a2,b0).

    Say it out loud

    I would multiply the coverpoint bins: the auto cross has six bins, and four are hit, so the cross is 66.67 percent. Each coverpoint is 100 percent on its own, but covering each variable says nothing about the combinations. The trap is quoting the coverpoint numbers as closure. Next I would list the two missing combinations and ask whether they are reachable.

    Related topics

    • Cross Basics

    • Crosses and the Combinatorial Explosion

    • Back to Cross Coverage Puzzles

    • Functional Coverage Puzzles section

    Previous

    143 / 293

    Next: Explicit ignore_bins instead of a default catch-all

    Up next

    Up nextExplicit ignore_bins instead of a default catch-all

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • intersect filter removes one tuple
    • illegal cross tuple does not close coverage
    • Three-way cross with overlapping ignore_bins