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
      • Coupling and Aggressors
      • Switching Windows
      • Delta Delay Arithmetic
      • Setup Versus Hold Impact
    • Noise and Glitch Analysis
    • SI ECO Fix Order
    • SI Signoff Reports
  • ECO and Closure16
  • STA Debug Playbook16
  • STA Interview Prep26
  • Capstone Timing Signoff Lab4
Loading lesson

‹Delta Delay Mechanism
  1. Topics
  2. Static Timing Analysis
  3. Crosstalk and Noise
  4. Delta Delay Mechanism
  5. Coupling and Aggressors

Part 7 · Crosstalk and Noise · All levels

Coupling and Aggressors

Coupling capacitance behaves like a different load depending on what the neighbour does: about double when it switches the opposite way, about nothing when it switches the same way.

On this page

    Why it matters

    A wire's delay depends on the capacitance it must charge. Part of that capacitance goes to the neighbouring wire. If the neighbour holds still, the coupling capacitance acts as ordinary capacitance. If it switches, the voltage across it changes, and the charge the victim's driver must supply changes with it.

    The first-order model

    Neighbour (aggressor) behaviour

    Effective coupling factor

    Effect on the victim

    Switches in the same direction

    about 0

    Victim is helped: delay decreases

    Stays quiet

    1

    Reference: coupling acts as ground capacitance

    Switches in the opposite direction

    about 2

    Victim is hindered: delay increases

    Diagram
    C_effective = C_ground + k * C_coupling
    k = 0 (same direction), 1 (quiet), 2 (opposite direction)
    delay (lumped, first order) = 0.69 * R_driver * C_effective
    example.py
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    R = 2000.0                    # driver resistance, ohm
    Cg, Cc = 8.0, 6.0             # ground and coupling capacitance, fF (illustrative)
    def delay_ps(k):
        return 0.69 * R * (Cg + k * Cc) / 1000.0      # ohm * fF = fs, so divide by 1000 for ps
    d = {k: round(delay_ps(k), 2) for k in (0, 1, 2)}
    assert d == {0: 11.04, 1: 19.32, 2: 27.6}
    slowdown = round(d[2] - d[1], 2)
    speedup = round(d[1] - d[0], 2)
    assert slowdown == 8.28 and speedup == 8.28
    assert round(d[2] / d[1], 3) == 1.429
    print("PASS: delay by aggressor behaviour", d, "; slowdown", slowdown, "ps and speedup", speedup, "ps relative to quiet")

    With 8 fF to ground and 6 fF of coupling, the same victim takes 19.32 ps with a quiet neighbour, 27.60 ps with a neighbour switching against it and 11.04 ps with one switching with it. The opposite-direction case is 43% slower than the quiet one. The factors 0 and 2 are the textbook idealisation of an aggressor that switches as fast as the victim; real analysis uses the actual slews and a proper electrical model, so treat the numbers as an orientation.

    What the review looks for

    • SI analysis is on in every setup and hold scenario that signoff depends on.

    • Coupling capacitance appears in the extracted parasitics and the same extraction feeds timing and SI.

    • The worst-delay nets are checked for their aggressors, not only for their nominal delay.

    Common pitfall

    Timing with coupling capacitance lumped to ground. That corresponds to the quiet case: it hides both the slowdown and the speedup, and each will cost you at a different check.

    Interview

    State the three cases and the factors 0, 1 and 2, and mention that the factors are idealised.

    Check yourself Why can the same neighbour be harmful for setup and for hold on different paths?

    When it switches against the victim it slows it (hurting setup on that path); when it switches with the victim it speeds it up (hurting hold on that path).

    Related topics

    • Next: Switching Windows

    Previous

    106 / 183

    Next: Switching Windows

    Up next

    Up nextSwitching Windows

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Delta Delay Arithmetic
    • Setup Versus Hold Impact