AMS Floorplan Keepouts: Design Space

Design space exploration

For AMS Floorplan Keepouts, closure options trade robustness, schedule, and margin.

Option A — conservative

• Conservative boundary guard: helps high robustness

• Risk: area and schedule cost

• Validate with: first-silicon risk

Option B — balanced

• Balanced integration policy: helps practical closure

• Risk: needs discipline

• Validate with: production ramp

Option C — aggressive

• Aggressive late ECO: helps quick symptom relief

• Risk: cross-domain regressions

• Validate with: deadline crunch

Option D — structural

• Architecture-level reshaping: helps durable fix

• Risk: long lead time

• Validate with: repeat offenders

DESIGN SPACE — AMS Floorplan Keepouts
robustness <-> performance <-> schedule
choose by keepout violation count, analog disturbance incidents, ECO rework on product-representative scenarios

Design pitfalls

• Mode coverage too shallow

• Fixing symptom without ownership alignment

Tradeoff curve

BEFORE / AFTER — AMS Floorplan Keepouts

health score
  ^
  |                     --- target
  |         o regressed
  |               o before fix
  |                    o after bounded fix
  +--------------------------------------> debug iteration

Prove signal quality, timing margin, and integration safety together.

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