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
    • Delta Delay Mechanism
    • Noise and Glitch Analysis
    • SI ECO Fix Order
    • SI Signoff Reports
      • Reading SI Reports
      • Windows and Filters
      • False Aggressors
      • SI Signoff Checklist
  • ECO and Closure16
  • STA Debug Playbook16
  • STA Interview Prep26
  • Capstone Timing Signoff Lab4
Loading lesson

‹SI Signoff Reports
  1. Topics
  2. Static Timing Analysis
  3. Crosstalk and Noise
  4. SI Signoff Reports
  5. SI Signoff Checklist

Part 7 · Crosstalk and Noise · All levels

SI Signoff Checklist

A short list of evidence that SI analysis was complete, final and honest; open items on it block signoff.

On this page

    Why it matters

    SI analysis is easy to run and easy to run incorrectly: wrong parasitics, a missing corner, a threshold left from an experiment. A short checklist with evidence for each line is the last defence.

    The checklist

    Item

    Evidence

    SI is enabled in every setup and hold scenario used for signoff

    Per-scenario settings read back

    Parasitics are final and contain coupling

    Extraction version and coupling flag

    Clock nets are in the analysis

    Clock victim list is non-empty and reviewed

    Thresholds and filters documented, hidden totals reported

    Filter table with hidden delay on the worst victims

    Noise analysis run with receiver margins; critical receivers clean

    Noise summary by class

    Exclusivity and case-analysis claims reviewed

    Claim list with owners and evidence

    Last ECO verified before and after

    Before-and-after endpoint table

    example.py
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    items = {
        "SI enabled in all signoff scenarios": True,
        "parasitics final with coupling": True,
        "clock nets analysed": True,
        "filters documented with hidden totals": False,
        "noise run, critical receivers clean": True,
        "exclusivity claims reviewed": True,
        "last ECO verified": True,
    }
    open_items = [k for k, v in items.items() if not v]
    wns_si = 0.004
    assert open_items == ["filters documented with hidden totals"]
    ready = not open_items and wns_si >= 0
    assert ready is False
    print("PASS: not ready; open items", open_items, "although WNS with SI is", wns_si, "ns")

    With SI on, the worst setup slack is +0.004 ns and everything looks fine, but one item is open: the filter table with hidden totals is missing, so nobody knows how much delay the thresholds hide. A signoff review treats the missing evidence, not the positive WNS, as the deciding fact. The WNS is 4 ps: the hidden total might be larger than that.

    What the review looks for

    • Every line has a link to the run and the date; a line without evidence is open.

    • The checklist is repeated, not copied, after each ECO that changes routing.

    • Open items have an owner and an expiry date before signoff is declared.

    Common pitfall

    Declaring SI done because the last run was clean. If the thresholds, parasitics or scenario list differ from the signoff definition, the run proves nothing about signoff.

    Interview

    Present the checklist as evidence per line, not as a list of things somebody claims to have done.

    Check yourself Why does a 4 ps WNS make the missing hidden-total evidence matter more?

    Because the filters can hide several picoseconds of delay; with only 4 ps of slack, the hidden total could be enough to turn the result negative.

    Related topics

    • False Aggressors

    Previous

    121 / 183

    Next: ECO and Closure

    Up next

    Up nextECO and Closure

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Reading SI Reports
    • Windows and Filters