DenseChip

AMS Interface · All levels

Abutment Rules: Expanded Case Study

Expanded Case Study for Abutment Rules.

Extended case study

Signoff review: abutment DRC count, manual exception count, integration turnaround regressed after a change touching Abutment Rules.

Background

Team had prior closure; latest integration run shows instability concentrated in one operating condition.

Symptoms observed

  • abutment DRC count, manual exception count, integration turnaround degradation

  • Cross-team disagreement on root cause

  • Directed tests pass but system scenario fails

Investigation timeline

  1. Hour 0: freeze data tags, firmware build, and environmental conditions

  2. Hour 1: diff boundary assumptions and handoff revisions

  3. Hour 2: isolate first failing mode and trigger sequence

  4. Hour 3: correlate waveform/log/report evidence

  5. Hour 4: classify root cause and ownership

  6. Hour 5: apply bounded fix

  7. Hour 6: execute full regression and issue signoff memo

Root cause

Root cause tied to Abutment Rules: Macro abutment rules encode legal proximity and orientation constraints; violation causes reliability or functional escapes at block boundaries.

Fix and validation

  • Bounded RTL/config/layout correction

  • Re-run macro abutment guide, DRC exception log, floorplan review deck

  • Full cross-domain regression matrix

Lessons learned

  • Tag everything

  • Mechanism before commands

  • No signoff without owner agreement

diagram
CASE STUDY — Abutment Rules
baseline metric / regressed metric / post-fix metric

Sequence under stress

diagram
AMS BOUNDARY SEQUENCE — Abutment Rules

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

metric under watch: abutment DRC count, manual exception count, integration turnaround

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

Macro abutment rules encode legal proximity and orientation constraints; violation causes reliability or functional escapes at block boundaries.

Metric: abutment DRC count, manual exception count, integration turnaround

Practice this lesson