AMS Interface · All levels

AMS Floorplan Keepouts: Step-by-Step Walkthrough

Step-by-Step Walkthrough for AMS Floorplan Keepouts.

Step-by-step analysis walkthrough

Use this when you own AMS Floorplan Keepouts during an AMS war room.

Capture failing mode and environmental condition.
Pull synchronized waveform, logs, and report artifacts.
Mark first boundary where legal behavior diverges.
Audit reset/clock/power sequence assumptions.
Check physical coupling contributors (floorplan/power/package) where relevant.
Assign single-thread ownership for the first fix.
Propose bounded change and define success criterion.
Run scenario and safety regressions.
Document findings in closure memo.
Update signoff dashboard and waiver state.

Artifacts to collect

floorplan keepout map, congestion overlay, integration signoff note
handoff contract
firmware/config tag
physical signoff snapshot
decision memo

Decision memo template

diagram

AMS DECISION MEMO — AMS Floorplan Keepouts
mode/condition:
metric:
hypothesis:
fix:
regression:
owners: floorplan owner, analog lead, PD lead

Reference visuals

Floorplan keepout model

diagram

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

AMS deep dive

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

Concept diagram

diagram

INTEGRATION FLOW

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

Metric graph

diagram

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

Practice this lesson