AMS Floorplan Keepouts: Review Checklist

Review checklist

Review Checklist for AMS Floorplan Keepouts focuses on keepout violation count, analog disturbance incidents, ECO rework. The goal is to connect observed symptom to boundary mechanism, ownership, and signoff risk.

• Boundary assumptions are versioned and signed.

• Mode matrix (power/clock/reset/stress) is explicit.

• Physical context (floorplan/package/power) is included where relevant.

• Metric and artifact references are reproducible.

• Waivers have owner, expiry, and mitigation.

• Owners signed: floorplan owner, analog lead, PD lead.

Sign-off ownership

OWNERSHIP MAP — AMS Floorplan Keepouts

artifact                  owner
----------------------    -----------------------------
integration artifact    floorplan owner
implementation artifact analog lead
signoff artifact        PD lead

Every boundary issue needs a named owner before fixes start.

AMS deep dive

Physical proximity and boundary rules are functional constraints in AMS SoCs.

Concept diagram

INTEGRATION FLOW

floorplan keepouts -> guard strategy -> abutment policy -> PV signoff

Metric graph

INTEGRATION ESCAPES

layout boundary issues ███████
waiver drift           ████

Reports and artifacts

• keepout violations

• guard-ring checks

• abutment DRC

• mixed-signal PV dashboard

Mini case study

Late macro move violated quiet-zone assumptions and caused intermittent converter noise excursions.

Debug branches

• Review macro adjacency

• Re-check guard assumptions

• Re-run PV with correct deck variant

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

Keepout regions protect analog blocks from aggressor routing, switching clusters, and noisy clocks that inject disturbance through substrate and supplies.

Metric: keepout violation count, analog disturbance incidents, ECO rework