AMS Interface · All levels

Jitter Budgeting: Comparison Matrix

Comparison Matrix for Jitter Budgeting.

Comparison matrix

PLL strategy trades jitter margin, lock time, and implementation complexity.

diagram

+------------------+----------------+----------------+----------------+
| Approach         | Strength       | Weakness       | Best when      |
+------------------+----------------+----------------+----------------+
| Conservative     | robust         | more overhead  | new tapeout    |
| Balanced         | practical      | needs rigor    | mature flow    |
| Aggressive       | faster         | high regressions | late stage     |
| Architectural    | durable        | slow loop      | recurring issue |
+------------------+----------------+----------------+----------------+

When to choose each approach

Choose the smallest change that proves mechanism and preserves system margins.

Interview traps

Treating all AMS problems as analog-only
Skipping package and power evidence

Evidence comparison

diagram

AMS EVIDENCE MATRIX — Jitter Budgeting

+-------------------+------------------------+--------------------------+-------------------------+
| Evidence           | Tells you              | Does not prove           | Next action             |
+-------------------+------------------------+--------------------------+-------------------------+
| Waveform/log pair  | sequence behavior      | physical root cause      | correlate with signoff  |
| Signoff report     | metric movement        | contract correctness     | audit assumptions       |
| Floorplan view     | physical proximity     | dynamic mode behavior    | run stress mode         |
| Firmware trace     | state progression      | analog quality           | combine with lab data   |
| Dashboard summary  | closure status         | single-failure mechanism | inspect raw artifacts   |
+-------------------+------------------------+--------------------------+-------------------------+

AMS deep dive

Clock quality evidence must include jitter and sequencing, not lock status alone.

Concept diagram

diagram

CLOCKING FLOW

reference -> PLL/DLL -> distribution -> endpoint margin

Metric graph

diagram

JITTER TREND

jitter ps
  ^
  |   o baseline
  |      o stress mode
  |         o failure edge

Reports and artifacts

jitter budget
lock/unlock counters
phase-noise snapshot
STA uncertainty deltas

Mini case study

False-lock condition released reset early; endpoint logic sampled unstable clock edge patterns.

Debug branches

Lock qualification policy
Reset sequencing check
Package/supply contributors

Senior review question

Ask: what boundary condition proves this topic is actually closed?

Key takeaways

State boundary, mode, and evidence tag with every claim.
Always align analog, digital, and physical owners before signoff decisions.

Common pitfalls

Fixing averages while tails still fail.
Skipping package/supply evidence in jitter or SerDes issues.
Shipping with waivers that lack owner and expiration criteria.

Principal AMS review addendum

System timing margin is consumed by source jitter, transfer jitter, supply noise, and distribution skew; the budget must close from reference clock to endpoint sampler.

Metric: total jitter budget, deterministic/random split, downstream timing margin

Practice this lesson