AMS Interface · All levels

AMS Interface Cheatsheet

Dense reference for boundary debug, signoff, and senior interviews.

Debug order

diagram
BOUNDARY -> MODE -> MECHANISM -> METRIC -> ARTIFACT -> OWNER -> REGRESSION

Boundaries: cells, wrappers, reset and CDC assumptions
Clocking: lock quality, jitter budget, uncertainty impact
High-speed I/O: training state, BER, lane margin, SI context
Converters: sample timing, calibration hooks, validity flags
Physical: keepouts, guard/substrate, package and IR/noise
Signoff: dashboard blockers, waivers, owner approvals

Questions before proposing a fix

  1. Which boundary fails first under which mode?

  2. Which mechanism explains that failure?

  3. Which metric and artifact prove it?

  4. Who owns smallest reversible fix?

  5. Which regressions are mandatory before release?