Bump Map & Escape Planning

What this topic teaches

Bump Map & Escape Planning is about making top-level contracts measurable and enforceable. Bump maps and escape strategy determine routability, IR quality, and package feasibility before final pad-ring freeze. The hard part is proving owner accountability and reproducibility under schedule pressure.

The senior-engineer question

When bump congestion, reroute churn, escape DRC violations moves, can you identify the first broken boundary, responsible owner, and smallest reversible fix with complete regression scope?

SOC INTEGRATION STACK — Bump Map & Escape Planning

program contract (scope, milestones, ownership)
        |
        v
architecture contract (budgets, interfaces, assumptions)
        |
        v
implementation contract (rtl, timing, physical, package)
        |
        v
validation contract (bring-up, workload, signoff evidence)
        |
        v
release contract (manifest, waivers, tapeout decision)

Debug rule: always identify which contract layer broke first.

Picture the integration flow

Start by drawing boundaries and ownership before diving into logs. The diagrams below are the whiteboard models to reproduce in reviews.

Bump escape planning

BUMP + ESCAPE

die bumps -> redistribution -> package balls
      |             |
   power grid    high-speed lane escape

Early escape planning prevents late route deadlock.

Integration sequence

SOC INTEGRATION FLOW — Bump Map & Escape Planning

requirements + budgets
        |
        v
IP handoff + collateral check
        |
        v
integration build + bring-up smoke
        |
        v
cross-domain signoff evidence
        |
        v
tapeout readiness decision

Metric in focus: bump congestion, reroute churn, escape DRC violations

Layer ownership

SOC INTEGRATION LAYERS — Bump Map & Escape Planning

layer               owns                          failure mode
-----------------   ---------------------------   ------------------------
architecture        partition + contracts         impossible budgets
ip handoff          models + collateral           integration mismatch
fabric/clock/reset  global behavior               domain deadlock
physical/package    route + SI/PI + IO            late closure churn
signoff process     manifests + waivers           non-reproducible claims
program governance  owners + escalations          schedule collapse

Evidence to collect

• Primary metric: bump congestion, reroute churn, escape DRC violations.

• Primary artifact: bump map revision, escape routing plan, package feasibility report.

• Owners to include: package owner, top-level PD owner, power integrity owner.

• Manifest baseline and revision for every claim.

• One focused repro and one full-system regression result.

Ownership map

OWNERSHIP MAP — Bump Map & Escape Planning

artifact             owner
-----------------    -----------------
primary owner     package owner
co-owner          top-level PD owner
review owner      power integrity owner

No top-level issue should remain ownerless beyond one review cycle.

Subpages in this topic

Each topic includes 15 subpages: mechanism, inputs/outputs, reports, debug, worked example, pitfalls, interview, checklist, theory, design space, expanded case study, walkthrough, comparison matrix, software view, and silicon PPA impact.

Key takeaways

• Tie every integration claim to a baseline manifest and owner.

• Fix the first broken boundary before broad optimizations.

• Regression scope is part of the fix, not a follow-up task.

Common pitfalls

• Comparing results across changing baselines.

• Unowned risks hidden behind green aggregate metrics.

• Waiving high-impact issues without expiry and revalidation.

SoC deep dive

Package assumptions must be treated as first-class chip constraints.

Concept diagram

PACKAGE CO-DESIGN
die io <-> package routing <-> board constraints

Metric graph

PACKAGE RISK MIX
SI margin █████
power integrity ████
lane mapping ███

Reports and artifacts

• bump map revision log

• SI/PI margin report

• IO co-design checklist

• package bring-up failures

Mini case study

Link degradation on product board came from package routing assumptions not reflected in pre-silicon model.

Debug branches

• Compare package model versions

• Audit lane mapping

• Correlate SI/PI margins to failures

Senior review question

Ask: what baseline, owner, and artifact prove this topic is truly closed?

Key takeaways

• State baseline manifest and owner with every closure metric.

• Run cross-domain regression after every top-level fix.

Common pitfalls

• Comparing results across different manifests.

• Unowned issues slipping through review cycles.

• Waiving risks without expiry and validation plan.