Extended case study

Signoff review: boundary violation count, level-shifter coverage, clamp correctness regressed after a change touching Boundary Cell Design.

Background

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

Symptoms observed

• boundary violation count, level-shifter coverage, clamp correctness 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 Boundary Cell Design: Boundary cells protect logic domains at analog interfaces by enforcing voltage tolerance, clamp behavior, and legal signal ownership during power sequencing.

Fix and validation

• Bounded RTL/config/layout correction

• Re-run boundary-cell checklist, level-shifter audit report, reset isolation table

• Full cross-domain regression matrix

Lessons learned

• Tag everything

• Mechanism before commands

• No signoff without owner agreement

CASE STUDY — Boundary Cell Design
baseline metric / regressed metric / post-fix metric

Sequence under stress

AMS BOUNDARY SEQUENCE — Boundary Cell Design

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

metric under watch: boundary violation count, level-shifter coverage, clamp correctness

AMS deep dive

Boundary assumptions must be explicit, versioned, and testable.

Concept diagram

BOUNDARY CONTRACT FLOW

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

Metric graph

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

Boundary cells protect logic domains at analog interfaces by enforcing voltage tolerance, clamp behavior, and legal signal ownership during power sequencing.

Metric: boundary violation count, level-shifter coverage, clamp correctness