Inputs and outputs contract

Inputs & Outputs for High-Speed SI Awareness focuses on SI-induced retries, lane margin, intermittent link drop rate. The goal is to connect observed symptom to boundary mechanism, ownership, and signoff risk.

Treat these inputs and outputs as signed interface guarantees. Ambiguity here creates the most expensive integration bugs.

INPUTS
  - AMS handoff contract and spec revision
  - mode definitions (power/clock/reset/traffic)
  - wrapper and boundary-cell assumptions
  - physical constraints: keepouts, guard, package limits

OUTPUTS
  - mode-tagged metric report
  - owner-signed debug or closure note
  - waiver manifest with expiry and controls
  - release recommendation

Boundary sequence

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

Ownership map

OWNERSHIP MAP — High-Speed SI Awareness

artifact                  owner
----------------------    -----------------------------
integration artifact    package owner
implementation artifact SI/PI owner
signoff artifact        SerDes integration owner

Every boundary issue needs a named owner before fixes start.

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