IntermediateQuestion 68 of 222

Why are notches and narrow channels risky?

From PDVerse PnR Interview Handbook, part of the pdVerse Mentor Guide

Short Answer

A narrow passage between macros can be geometrically "open" and still be effectively useless if every entry into it is blocked โ€” an open channel with no legal access is not usable routing/placement space. These regions concentrate routes and pins into a small area, which fragments standard-cell rows, complicates power/ground continuity, and often leaves dead space that neither cells nor wires end up using well.

Technical Reference DiagramWhy are notches and narrow channels risky?

Technical Explanation

  • The places to specifically inspect are concave corners, two macro edges facing each other, pins that face into the channel from both sides, leftover row remnants, the preferred routing-layer direction through the channel, and whether vias actually have room to land there.
  • Think of it like a hallway that's wide enough on a floor plan but has support pillars right at both doorways โ€” the raw width number doesn't tell you it's usable.
  • Treat notch/channel review as a dedicated floorplan check, not something that "will probably route fine" โ€” this is one of the more common late-stage congestion surprises.

Formula Or Decision Rule

Decision rule: remove or justify every notch and prove capacity with the post-reservation routing model.

What To Check

  • Warning sign: A notch survives legality checks but produces a persistent local hot spot.
  • Inspect: choose one affected region, macro, row, pin, path, or net and trace the physical cause.
  • Correct: Move or align macros, widen the corridor, redirect pins, or reserve it explicitly, then rerun.

Command Checks & Actions

  • check_floorplan_rules: reports configured floorplan-rule violations
  • create_channel_congestion_map -boundary <coordinates>: estimates congestion in channel regions

Run only the commands needed for this question. Save the report with the floorplan version and analysis context.

Healthy, Suspicious & Hard-stop Results

  • Healthy: They concentrate routes and pins, fragment rows, complicate PG continuity, and can create dead space that neither cells nor wires use well.
  • Hard stop: required legality or physical feasibility is missing or unexplained.

Common Mistake

The Trap: Do not hide the symptom with an arbitrary utilisation, halo, channel, blockage, pin move, or die-size change.

What The Interviewer Is Testing

โ€ to measurable physical evidence and an owned correction.

Follow-up Question & Model Response

"* Candidate Model Response: Model response: โ€œI would change it if the same controlled rerun shows that a notch survives legality checks but produces a persistent local hot spot. โ€

Physical Design & Planning Handbook

Dive into 14 comprehensive chapters covering netlist sanity, FinFET grids, macro placement, power grids, CTS, and timing budgeting.

Offline PDF Bundle

Want all 1109 questions offline?

Get the complete 4-book PDF bundle (PnR, STA, MMMC, Low Power) with a clickable table of contents - no ads, no internet needed.

See what's inside the bundle
PnR Flow Physical Design Mentor Guide โ€” eight chaptersPnR Flow Mentor GuideEight chapters, library setup through to stream-out.