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

  • RTL Foundations36
  • Combinational Design25
  • Sequential Design27
  • FSM & Control27
  • Timing & Clocking39
  • Reset & CDC34
  • Memory & Buses57
  • Advanced RTL28
  • Senior & Interview76
    • Low-Power RTL Hub
    • DFT and Scan Hub
    • Physical Awareness Hub
    • Waveform Debug Hub
    • STA and ECO Hub
    • RTL-to-Implementation Closure
    • DFT-Ready RTL
    • Capstone: Resilient Streaming Peripheral
    • Principal Design Review
    • Senior RTL Interview Questions & Model Answers
      • Interview: Combinational and Arithmetic
      • Interview: Sequential and Pipelines
      • Interview: FSM and Control
      • Interview: Timing and STA
      • Interview: CDC and Reset
      • Interview: Memories and Buses
      • Interview: Low-Power Design
      • Interview: Debug and ECO
        • X-propagation discipline
        • Why simulation and silicon disagree
        • Capturing an intermittent failure
        • ECO or RTL change
      • Interview: Coding and Whiteboard
  • Glossary and Notation
Loading lesson

←Senior RTL Interview Questions & Model Answers
  1. Topics
  2. RTL Design
  3. Senior & Interview
  4. Senior RTL Interview Questions & Model Answers
  5. Interview: Debug and ECO
On this page

    Part 9 of 9Part 9 of 9/SeniorSenior

    Interview: Debug and ECO

    How senior candidates show debug and ECO judgment: X discipline, sim-silicon gaps, intermittent capture, ECO calls.

    • 4topics
    • 4lessons

    Topics in this section

    1. 1X-propagation discipline1 lesson
    2. 2Why simulation and silicon disagree1 lesson
    3. 3Capturing an intermittent failure1 lesson
    4. 4ECO or RTL change1 lesson

    Debug and ECO interviews test judgment with evidence: where unknowns come from, why passing simulations still fail in silicon, how intermittent bugs get captured, and when a late fix is a gate edit or an RTL change.

    Lessons in this topic

    4 lessons, about 17 min

    1. 1X-propagation disciplineYou can list where X comes from, show how if, case and ternary treat an X select, and state the three-part discipline that keeps X out of sign-off.5 min
    2. 2Why simulation and silicon disagreeYou can list the usual simulation idealisations, say what silicon does instead, and name the check that removes each gap.4 min
    3. 3Capturing an intermittent failureYou can list what a full replay configuration contains, set a trigger with pre-failure history, and shrink a failing case.4 min
    4. 4ECO or RTL changeYou can decide between a gate-level ECO and an RTL change from the failure's locality, and say what evidence closes an ECO.4 min
    Check yourself An interviewer asks for the single strongest habit in debug. What is the one-line answer?

    Check the first divergence, not the last symptom. Every lesson in this topic is that habit applied to a different gap.

    The thread across all four lessons: name the idealization, show the evidence, and pick the fix whose risk fits the schedule.

    Revision sheet

    The whole topic on one page, taken from each lesson's Remember box. Read it before an interview, or print it.

    X-propagation discipline

    • X comes from uninitialised flops, incomplete reset, undefined memories and powered-down domains.

    • An X select takes the else branch of an if, holds the old value in a case, and gives X from a ternary with disagreeing inputs.

    • X means unknown, not don't care. Silicon picks a real value the testbench never checked.

    Rule of thumb: close every X at its source: reset it, define it, or clamp it.

    Why simulation and silicon disagree

    • Every gap has one shape: the simulator models something silicon does not honour.

    • Model gaps far outnumber tool bugs, so audit the model before blaming the tool.

    • A wrong constraint or an unconstrained crossing makes STA check something other than the hardware.

    Rule of thumb: name the idealisation first, then add the check that removes it.

    Capturing an intermittent failure

    • A seed alone is not a run configuration. Record source revision, tools, defines, parameters, inputs and reset schedule.

    • Trigger on the earliest divergence and keep pre-trigger history in a circular buffer. Dumping after the failure loses causes.

    • Vary one knob at a time and halve the stimulus until the failure fits in one wave window.

    Rule of thumb: seed it, trigger on the first divergence, halve until small.

    ECO or RTL change

    • Check the constraint first. A wrong clock definition gives a violation the hardware never sees.

    • A single failing path takes a local gate edit. A structural shortfall across many paths takes an RTL change.

    • Fix setup and hold together, and close an ECO with equivalence, regressions and all timing views.

    Rule of thumb: repeated ECOs on the same logic mean the structure is wrong.

    Practise it

    • Mini project: the capstone: a resilient streaming peripheral, stage by stage

    • Practice question: 3-to-8 decoder: unique/priority case and X-propagation

    • Code lab: X-propagation model

    • Interview: run a mock interview on this topic

    PreviousNext: X-propagation discipline

    Up next

    Up nextX-propagation discipline

    Sign in to save progress

    Practice this lessonPrevious lessonReport an error

    See also

    • Interview: Combinational and Arithmetic
    • Interview: Sequential and Pipelines
    • Interview: FSM and Control