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
    • Latches and Time Borrowing
    • Clock Gating Checks
    • Recovery, Removal and Async
    • Pulse Width and Min Period
      • Minimum Pulse Width
      • Minimum Period
      • Duty Cycle Distortion
      • Pulse Width Signoff
  • Multi-Corner Multi-Mode Signoff16
  • OCV, AOCV, POCV and Variation16
  • Crosstalk and Noise16
  • ECO and Closure16
  • STA Debug Playbook16
  • STA Interview Prep26
  • Capstone Timing Signoff Lab4
Loading lesson

‹Pulse Width and Min Period
  1. Topics
  2. Static Timing Analysis
  3. Beyond Setup and Hold
  4. Pulse Width and Min Period
  5. Pulse Width Signoff

Part 4 · Beyond Setup and Hold · All levels

Pulse Width Signoff

A review list for pulse width and minimum period: both phases, all corners, propagated clocks, macros listed, and distortion bounded.

On this page

    Why it matters

    Pulse width and period checks are sometimes left out of the main summary because they do not involve data paths. They matter for exactly the cells that are most expensive to fix late: memories and macros. A short list prevents their omission.

    The review list

    Item

    Evidence

    Checks are enabled and reported

    A pulse width and period section in the signoff summary

    All macros and latches are covered

    List of clock pins with limits, and a count of checks

    Both phases, every corner

    Per-view table of worst high and low slack

    Propagated clocks used

    Checks are against leaf arrival times, not the ideal clock

    Distortion reviewed

    Duty cycle at the leaves, per corner

    Period limits match the clock definitions

    Divided and multiplexed clocks reviewed

    example.py
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    views = {
        "ss_0p72v_125c": {"high": 0.05, "low": -0.04},
        "ff_0p88v_m40c": {"high": 0.11, "low": 0.09},
        "tt_0p8v_25c":   {"high": 0.08, "low": 0.03},
    }
    fails = {v: [ph for ph, s in d.items() if s < 0] for v, d in views.items() if min(d.values()) < 0}
    assert fails == {"ss_0p72v_125c": ["low"]}
    worst_high = min(d["high"] for d in views.values())
    assert worst_high == 0.05
    print("PASS: failing views and phases", fails, "; worst high slack", worst_high)

    Only the slow corner fails, and only the low phase: one phase in one corner points to duty cycle distortion, because rise and fall delays differ by corner, rather than to a frequency problem: with symmetric limits a frequency problem fails both phases together, while with asymmetric per-phase limits the tighter phase fails first, so state both limits before diagnosing. The fix is on the clock tree, and the next review reads the leaf duty cycle.

    Typical fixes

    Symptom

    Fix

    One phase narrow in the slow corner

    Reduce rise/fall mismatch in the tree

    Both phases fail together (with symmetric limits; with asymmetric per-phase limits the tighter phase fails first, so state both limits before diagnosing)

    Clock too fast for the cell: use a slower or divided clock

    Period violation at a macro

    Divider or separate macro clock

    Pulse width at a gating cell

    Review enable and gate cell, and the clock before the gate

    Common pitfall

    Waiving a pulse width violation at a macro because no data path fails. The macro itself can fail in silicon, and a late fix is expensive.

    Interview

    Say what pattern points at distortion: one phase fails in one corner, while with symmetric limits both failing together means the frequency is too high for the cell; with asymmetric per-phase limits the tighter phase fails first, so state both limits before diagnosing.

    Check yourself In the example, why check the leaf duty cycle and not the source duty cycle?

    The check is at the cell's clock pin, which sees the waveform after the whole tree. The source waveform is only the starting point.

    Related topics

    • Duty Cycle Distortion

    Previous

    73 / 183

    Next: Multi-Corner Multi-Mode Signoff

    Up next

    Up nextMulti-Corner Multi-Mode Signoff

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Minimum Pulse Width
    • Minimum Period