How do pitch, offset, direction, and width define routing tracks?
From PDVerse PnR Interview Handbook, part of the pdVerse Mentor Guide
Short Answer
Pitch controls repetition, offset sets the first coordinate, direction selects X or Y track lines, and width can reserve a wire width. Technology rules decide legality.
Technical Explanation
- Routing track grids define the physical wire highways for every metal layer in the design, established in the technology LEF and floorplan DEF.
- Pitch: Center-to-center distance between adjacent routing tracks (w_min + s_min). Pitch determines the total wire capacity of a layer.
- Offset: The starting distance from the origin (0,0) to the first routing track centerline. Track offset is critical because it must align directly with standard cell pin port centerlines; a misaligned offset forces the detailed router to insert off-grid jogs, triggering thousands of via enclosure and spacing DRC violations.
- g. M1/M3/M5 Vertical, M2/M4/M6 Horizontal) to eliminate cross-talk coupling capacitance and optimize router maze-search throughput.
- Width & Non-Default Rules (NDR): Standard signal tracks use 1x minimum width, while critical clock trees and power stripes allocate wide non-default rules (2x W, 2x S) to slash interconnect resistance and shield against crosstalk glitch noise.
- In advanced FinFET and EUV nodes (7nm/5nm/3nm), track grids also enforce multi-patterning coloring tracks (Mask 1 vs Mask 2), where odd and even tracks are assigned to different lithography masks.
Formula Or Decision Rule
Track coordinate = offset + k x pitch, where k is an integer.
What To Check
- Warning sign: Tracks exist but do not cross the core or miss all important pins.
- Inspect: choose one affected region, macro, row, pin, path, or net and trace the physical cause.
- Correct: Correct the technology or project track definition and rerun floorplan and pin checks.
Command Checks & Actions
- create_track -layer <layer> -space <pitch> -coord <offset> -width <width> -dir <X_or_Y>: creates a routing-track pattern
report_design-floorplan: reports the floorplan state understood by the tool
Run only the commands needed for this question. Save the report with the floorplan version and analysis context.
Healthy, Suspicious & Hard-stop Results
Technology rules decide legality.
- 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 tracks exist but do not cross the core or miss all important pins. โ
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