AMS Floorplan Keepouts: Worked Example

Worked example

Worked Example 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.

A stress workload shows keepout violation count, analog disturbance incidents, ECO rework. The first review mistake is broad blame. A better review tracks one boundary transition, validates contract assumptions, and proves the first failing mechanism in AMS Floorplan Keepouts.

Sequence under inspection

AMS BOUNDARY SEQUENCE — AMS Floorplan Keepouts

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

metric under watch: keepout violation count, analog disturbance incidents, ECO rework

Floorplan keepout model

analog macro [keepout + quiet routes + dedicated supplies]
surrounding digital switching must respect noise boundaries.

1. Capture tagged waveform/log/report set.

2. Mark mode boundary and first failure timestamp.

3. Map to contract and owner.

4. Compare against floorplan keepout map, congestion overlay, integration signoff note.

5. Propose one reversible fix and predefine regression matrix.

Did the fix work?

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