Fixed package pins fight the logical dataflow. What can floorplanning change?
From PDVerse PnR Interview Handbook, part of the pdVerse Mentor Guide
Short Answer
The package pin locations are usually a hard external constraint — you can't wish them away, so the real question is what floorplanning can still adapt to make the best of a fixed doorway. Macro locations are still yours to move — position macros to minimize the mismatch between where the package pins land and where your logical dataflow naturally wants to go.
Technical Explanation
- Block pin placement on your own hierarchy boundaries is adjustable — even if the outer package pins are fixed, you can still choose where internal block interfaces sit to shorten the path from package pin to first logic.
- Feedthroughs become a legitimate tool here — if the dataflow naturally wants to cross a block that happens to sit between a fixed pin and its destination logic, a deliberate feedthrough can bridge that gap more cheaply than a long detour.
- Aspect ratio and overall floorplan shape are still negotiable — reshaping the die/core proportions can sometimes realign your natural dataflow with where the fixed pins actually are.
- Routing corridors can be planned specifically around the fixed pin locations to preserve capacity exactly where the mismatch is worst.
- What you must preserve without compromise: differential pair and analog signal constraints — these have physical requirements (matched length, isolation, shielding) that can't be sacrificed just to make the floorplan tidier.
- Compare the real cost of each option using the same method: crossing count, bus ordering, critical-path impact, macro affinity, power/ground distribution, and resulting congestion — and escalate to renegotiating the package interface itself only if none of floorplanning's available levers can absorb the mismatch.
Formula Or Decision Rule
Decision rule: accept the package only with a credible on-die route and owned timing/congestion risk.
What To Check
- Warning sign: Pins are moved locally without package approval.
- Inspect: choose one affected region, macro, row, pin, path, or net and trace the physical cause.
- Correct: Keep fixed constraints, redesign internal geography, or return a quantified package change request.
Command Checks & Actions
- report_pin_placement -format {layer side offset}: reports pin layer, side, and offset
report_congestion-mode hot_spot: reports routing demand, capacity, overflow, or hot spotsreport_timing: reports timing paths in the active analysis context
Run only the commands needed for this question. Save the report with the floorplan version and analysis context.
Healthy, Suspicious & Hard-stop Results
- Healthy: Treat package pins as constraints, then adapt macro locations, block pins, feedthroughs, aspect ratio, and routing corridors around them. Escalate only when the package interface itself is negotiable.
- 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
The interviewer is testing whether you can connect “Fixed package pins fight the logical dataflow. ” 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 pins are moved locally without package approval. ”
Physical Design & Planning Handbook
Master ASIC Physical Design Planning & Floorplanning
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.
Continue practising