AMS Interface · All levels

Boundary Cell Design: Comparison Matrix

Comparison Matrix for Boundary Cell Design.

Comparison matrix

Boundary strategy choices trade robustness, area, and schedule risk.

diagram

+------------------+----------------+----------------+----------------+
| Approach         | Strength       | Weakness       | Best when      |
+------------------+----------------+----------------+----------------+
| Conservative     | robust         | more overhead  | new tapeout    |
| Balanced         | practical      | needs rigor    | mature flow    |
| Aggressive       | faster         | high regressions | late stage     |
| Architectural    | durable        | slow loop      | recurring issue |
+------------------+----------------+----------------+----------------+

When to choose each approach

Choose the smallest change that proves mechanism and preserves system margins.

Interview traps

Treating all AMS problems as analog-only
Skipping package and power evidence

Evidence comparison

diagram

AMS EVIDENCE MATRIX — Boundary Cell Design

+-------------------+------------------------+--------------------------+-------------------------+
| Evidence           | Tells you              | Does not prove           | Next action             |
+-------------------+------------------------+--------------------------+-------------------------+
| Waveform/log pair  | sequence behavior      | physical root cause      | correlate with signoff  |
| Signoff report     | metric movement        | contract correctness     | audit assumptions       |
| Floorplan view     | physical proximity     | dynamic mode behavior    | run stress mode         |
| Firmware trace     | state progression      | analog quality           | combine with lab data   |
| Dashboard summary  | closure status         | single-failure mechanism | inspect raw artifacts   |
+-------------------+------------------------+--------------------------+-------------------------+

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

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

Practice this lesson