Supply Noise Coupling Paths and PSRR Across Frequency: Theory Deep Dive

Foundational theory

Supply Noise Coupling Paths and PSRR Across Frequency is a core topic in Noise & Signal Integrity. Treat every design choice as a measurable reliability and integration decision.

Core concepts explained

• Power-supply noise reaches sensitive nodes through finite gain-stage rejection, bias mirrors, substrate coupling, package parasitics, and shared return inductance that converts di/dt into local ground bounce. PSRR is strongly frequency-dependent: low-frequency rejection can be high due to loop gain, then collapse near amplifier poles where feedthrough and parasitic capacitances dominate. Digital switching regulators and clock trees inject deterministic ripple and harmonics that can mix with signal paths, creating spurs in converters and sidebands in PLL or SerDes clocks. Robust design combines local decoupling impedance shaping, low-noise references/LDO partitioning, star-domain isolation strategy, and layout discipline (current return control, guard structures, deep-nwell where available), while system teams validate worst-case coupling using realistic package/board impedance and simultaneous-switching activity.

• Primary metric: PSRR(dB) versus frequency, output spur amplitude at switching harmonics, and supply-induced ENOB/SNDR degradation.

• Primary artifact: End-to-end supply-coupling map from board rail to critical analog nodes with PSRR-vs-frequency limits and spur budget signoff.

• Owners: power integrity owner, analog macro designer, package and board engineer, SoC integration owner, post-silicon validation owner

• Separate deterministic interference from stochastic noise mechanisms

• Map source-path-victim before selecting mitigations

Why this matters in mixed-signal products

Noise and SI closure is path-based: source, transfer, victim sensitivity, and operating envelope. Teams that apply this avoid false closure and late-stage bring-up churn.

Mental model

NOISE SPECTRUM VIEW

noise PSD
  ^
  |  | \  1/f noise region
  |  \
  |   \___________________ thermal floor
  |                         \
  +--------------------------------------> frequency

Spurs appear as narrow peaks above the floor.
Integration over bandwidth gives total RMS noise.

Worked intuition

1. Define the failing metric and operating context first.

2. Classify candidate mechanism family (noise, bandwidth, loop, coupling, or interface).

3. Capture one high-confidence artifact tied to first failing boundary.

4. Quantify movement in PSRR(dB) versus frequency, output spur amplitude at switching harmonics, and supply-induced ENOB/SNDR degradation. before broad architectural changes.

5. Apply one bounded mitigation and replay stress conditions.

6. Publish closure memo with owner signoff and rollback criteria.

Common misconceptions

• One nominal-corner success proves robust analog closure.

• Lock or static transfer checks guarantee dynamic quality.

• Single-number margins replace frequency-dependent analysis.

• Digital abstractions can absorb analog uncertainty by default.

Analog deep dive

Noise and SI closure is achieved by frequency-aware path analysis, not one-number guard-bands.

Concept diagram

NOISE PATH VIEW

source -> transfer function -> victim sensitivity -> system margin

Metric graph

NOISE CLOSURE

path unknown             ██████
path classified          █████████
validated mitigations    ███████

Metrics and artifacts to collect

• white/1-f noise decomposition

• PSRR versus frequency profile

• alias-folding sensitivity map

• phase-noise to jitter integration summary

Mini case study

A broadband spur issue persisted until teams modeled package and return-path coupling instead of relying on low-frequency PSRR numbers.

Debug branches

• Classify deterministic versus random contributors first.

• Map dominant transfer path before adding generic filtering.

• Use operating-mode-specific aggressor profiles in validation.

Senior review question

Ask: which source-path-victim boundary failed first, and which artifact proves it reproducibly?

Key takeaways

• Tie every analog claim to one measurable metric and one proving artifact.

• Prefer minimal reversible mitigations with explicit owner and rollback criteria.

Common pitfalls

• Treating all noise as one scalar instead of path and frequency dependent behavior.

• Changing multiple analog knobs at once and losing causality.

• Declaring closure from nominal behavior without stress replay evidence.

Theory reinforcement

Theory is useful only when it predicts measurable behavior and mitigation boundaries.

Translate formulas into integration decisions with explicit owners.