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 Course
  • Reading Path
  • STA Glossary
  • STA Metrics Reference
  • STA Mastery Cheatsheet
  • Timing Paths and Checks16
  • Constraints & SDC Fundamentals20
  • Delay Graph & Path Analysis16
  • Beyond Setup and Hold16
  • Multi-Corner Multi-Mode Signoff16
  • OCV, AOCV, POCV and Variation16
  • Crosstalk and Noise16
  • ECO and Closure16
  • STA Debug Playbook16
    • Constraint Bug Patterns
    • View Mismatch Triage
      • Same Design, Different Numbers
      • Library and Parasitic Mismatch
      • Constraint Version Drift
      • Mismatch Triage Checklist
    • Path Group War Room
    • Signoff Regression Hygiene
  • STA Interview Prep26
  • Capstone Timing Signoff Lab4
Loading lesson

‹STA Debug Playbook
  1. Topics
  2. Static Timing Analysis
  3. STA Debug Playbook
  4. View Mismatch Triage

Part 9 · Debug Playbook · All levels

View Mismatch Triage

When two runs of the same design give different numbers: find the stage where they first diverge, catch library and parasitic mismatches, and detect constraint drift.

  • 4topics
  • 4lessons

Two reports of the same design disagree. Before anyone argues about which is right, the disagreement has to be localised. This topic gives a staged comparison that finds the first point of divergence, two cheap sanity checks for libraries and parasitics, a heuristic for suspicious constraint changes, and a triage checklist driven by the distribution of the differences.

Lesson

After it you can...

Same Design, Different Numbers

Find the first stage at which two flows diverge.

Library and Parasitic Mismatch

Detect unit errors and swapped corners.

Constraint Version Drift

Flag a suspicious improvement from a constraint change.

Mismatch Triage Checklist

Classify a difference from its distribution.

This topic extends Signoff vs Implementation Views from measuring correlation to localising a break.

Check yourself Why localise before debugging individual paths?

If the cause is a global setting, every path is affected the same way and debugging one path rediscovers it a thousand times; locating the stage and distribution first tells you what kind of problem it is.

Interview

Walk through the stages: common libraries and netlist, constraints, library mapping, parasitics, derates, and compare after each.

PreviousNext: Same Design, Different Numbers

Up next

Up nextSame Design, Different Numbers

Sign in to save progress

Practice this lessonReport an error

See also

  • Constraint Bug Patterns
  • Path Group War Room
  • Signoff Regression Hygiene