AMS Interface · All levels
Equalization Overview: Expanded Case Study
Expanded Case Study for Equalization Overview.
Extended case study
Signoff review: eye opening, BER vs EQ setting, adaptation convergence regressed after a change touching Equalization Overview.
Background
Team had prior closure; latest integration run shows instability concentrated in one operating condition.
Symptoms observed
eye opening, BER vs EQ setting, adaptation convergence degradation
Cross-team disagreement on root cause
Directed tests pass but system scenario fails
Investigation timeline
Hour 0: freeze data tags, firmware build, and environmental conditions
Hour 1: diff boundary assumptions and handoff revisions
Hour 2: isolate first failing mode and trigger sequence
Hour 3: correlate waveform/log/report evidence
Hour 4: classify root cause and ownership
Hour 5: apply bounded fix
Hour 6: execute full regression and issue signoff memo
Root cause
Root cause tied to Equalization Overview: TX pre-emphasis and RX equalization compensate ISI and channel loss; over/under-equalization shifts noise sensitivity and error distribution.
Fix and validation
Bounded RTL/config/layout correction
Re-run EQ sweep report, eye diagram snapshot, adaptation log
Full cross-domain regression matrix
Lessons learned
Tag everything
Mechanism before commands
No signoff without owner agreement
CASE STUDY — Equalization Overview
baseline metric / regressed metric / post-fix metricSequence under stress
AMS BOUNDARY SEQUENCE — Equalization Overview
analog macro -> wrapper / boundary cell -> synchronizer or sampler -> digital consumer
| | | |
analog assumptions legal voltage/state clock/reset contract protocol/data validity
metric under watch: eye opening, BER vs EQ setting, adaptation convergenceAMS deep dive
SerDes closure requires protocol, training, and SI evidence together.
Concept diagram
SERDES FLOW
training -> equalization -> lane margin -> protocol stabilityMetric graph
BER VS EQ
BER
^
| high low high
+-----------------> EQ settingReports and artifacts
lane BER
training state transitions
EQ sweep report
link retry counters
Mini case study
Link looked protocol-clean but lane margin collapsed under thermal sweep.
Debug branches
Correlate LTSSM and lane metrics
Check SI margins
Review firmware timeout assumptions
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
TX pre-emphasis and RX equalization compensate ISI and channel loss; over/under-equalization shifts noise sensitivity and error distribution.
Metric: eye opening, BER vs EQ setting, adaptation convergence