High-Speed SI Awareness: Expanded Case Study

Extended case study

Signoff review: SI-induced retries, lane margin, intermittent link drop rate regressed after a change touching High-Speed SI Awareness.

Background

Team had prior closure; latest integration run shows instability concentrated in one operating condition.

Symptoms observed

• SI-induced retries, lane margin, intermittent link drop rate degradation

• Cross-team disagreement on root cause

• Directed tests pass but system scenario fails

Investigation timeline

1. Hour 0: freeze data tags, firmware build, and environmental conditions

2. Hour 1: diff boundary assumptions and handoff revisions

3. Hour 2: isolate first failing mode and trigger sequence

4. Hour 3: correlate waveform/log/report evidence

5. Hour 4: classify root cause and ownership

6. Hour 5: apply bounded fix

7. Hour 6: execute full regression and issue signoff memo

Root cause

Root cause tied to High-Speed SI Awareness: At multi-Gbps speeds, package/channel discontinuities and return-path quality convert into jitter and eye closure that appear as digital protocol instability.

Fix and validation

• Bounded RTL/config/layout correction

• Re-run channel compliance report, lane margin scan, SI waiver sheet

• Full cross-domain regression matrix

Lessons learned

• Tag everything

• Mechanism before commands

• No signoff without owner agreement

CASE STUDY — High-Speed SI Awareness
baseline metric / regressed metric / post-fix metric

Sequence under stress

AMS BOUNDARY SEQUENCE — High-Speed SI Awareness

analog macro -> wrapper / boundary cell -> synchronizer or sampler -> digital consumer
      |                 |                         |                     |
  analog assumptions    legal voltage/state       clock/reset contract   protocol/data validity

metric under watch: SI-induced retries, lane margin, intermittent link drop rate

AMS deep dive

SerDes closure requires protocol, training, and SI evidence together.

Concept diagram

SERDES FLOW

training -> equalization -> lane margin -> protocol stability

Metric graph

BER VS EQ

BER
 ^
 |  high  low  high
 +-----------------> EQ setting

Reports 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

At multi-Gbps speeds, package/channel discontinuities and return-path quality convert into jitter and eye closure that appear as digital protocol instability.

Metric: SI-induced retries, lane margin, intermittent link drop rate