How do you estimate whether a macro channel is wide enough?
From PDVerse PnR Interview Handbook · pdVerse Mentor Guide
Short Answer
Start with usable routing layers and track pitches, subtract PG straps, blockages, via keepouts, shielding, and edge rules, then compare remaining directional capacity with signal and pin demand.
Technical Explanation
Channel width matters only through the resources it leaves usable. Facing pin density, parallel buses, clock/reset needs, repeater space, and macro-corner access can dominate. Space reserved for wires may not be usable for standard cells.
Formula Or Decision Rule
Approximate usable tracks = floor(usable channel width / relevant pitch), before detailed rule reductions.
What To Check
• Warning sign: The geometric track count looks adequate but vias and PG shapes remove access. • Inspect: choose one affected region, macro, row, pin, path, or net and trace the physical cause. • Correct: Build a channel congestion map, inspect layers and pin walls, then adjust geometry or resource allocation.
Command Checks & Actions
• create_channel_congestion_map -channel_width_threshold <width>: estimates congestion in channel regions
• report_congestion -mode summary: reports routing demand, capacity, overflow, or hot spots
Run only the commands needed for this question. Save the report with the floorplan version and analysis context.Healthy, Suspicious & Hard-stop Results
• Healthy: Start with usable routing layers and track pitches, subtract PG straps, blockages, via keepouts, shielding, and edge rules, then compare remaining directional capacity with signal and pin demand. • Suspicious: The geometric track count looks adequate but vias and PG shapes remove access. • Hard stop: required legality or physical feasibility is missing or unexplained. Build a channel congestion map, inspect layers and pin walls, then adjust geometry or resource allocation.
Common Mistake
Do not hide the symptom with an arbitrary utilisation, halo, channel, blockage, pin move, or die-size change. The geometric track count looks adequate but vias and PG shapes remove access.
What The Interviewer Is Testing
The interviewer is testing whether you can connect “How do you estimate whether a macro channel is wide enough?” to measurable physical evidence and an owned correction.
Follow-up Question & Model Response
Follow-up probe: What would make you change your decision? Model response: “I would change it if the same controlled rerun shows that the geometric track count looks adequate but vias and PG shapes remove access. I would use the named objects and reports to decide whether to iterate, waive, or return the issue.”
Practical Example
Symptom: The geometric track count looks adequate but vias and PG shapes remove access. Corrective path: Build a channel congestion map, inspect layers and pin walls, then adjust geometry or resource allocation.
Continue practising