DenseChip

AMS Interface · All levels

AMS Handoff Contract: Expanded Case Study

Expanded Case Study for AMS Handoff Contract.

Extended case study

Signoff review: handoff completeness score, late-change churn, integration escape count regressed after a change touching AMS Handoff Contract.

Background

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

Symptoms observed

  • handoff completeness score, late-change churn, integration escape count 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 AMS Handoff Contract: A complete AMS handoff defines legal clocks, resets, power states, wrapper assumptions, and validation evidence so digital integration does not guess analog intent.

Fix and validation

  • Bounded RTL/config/layout correction

  • Re-run AMS handoff package, interface spec matrix, signoff checklist

  • Full cross-domain regression matrix

Lessons learned

  • Tag everything

  • Mechanism before commands

  • No signoff without owner agreement

diagram
CASE STUDY — AMS Handoff Contract
baseline metric / regressed metric / post-fix metric

Sequence under stress

diagram
AMS BOUNDARY SEQUENCE — AMS Handoff Contract

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

metric under watch: handoff completeness score, late-change churn, integration escape count

AMS deep dive

Boundary assumptions must be explicit, versioned, and testable.

Concept diagram

diagram
BOUNDARY CONTRACT FLOW

analog intent -> boundary implementation -> digital wrapper -> signed review

Metric graph

diagram
BOUNDARY RISK MIX

missing boundary cells    ███████
stale handoff assumptions ██████
silent mode changes       ████

Reports and artifacts

  • boundary-cell coverage

  • isolation/ESD review

  • handoff contract checklist

  • integration waiver log

Mini case study

Noise bursts traced to missing isolation clamp on one low-power transition mode.

Debug branches

  • Validate boundary-cell insertion

  • Diff handoff assumptions

  • Reproduce with tagged mode sequence

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

A complete AMS handoff defines legal clocks, resets, power states, wrapper assumptions, and validation evidence so digital integration does not guess analog intent.

Metric: handoff completeness score, late-change churn, integration escape count

Practice this lesson