ExpertQuestion 77 of 161

How does create_clock_straps decide whether it's building a mesh or a spine, and what does -margins actually control?

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

By Tabish Iqbal, who has 9+ years of VLSI Physical Design experience

Short Answer

The -type option per direction decides the topology: stripe in both directions builds a mesh; one direction as user_route (with the orthogonal direction as detect for spine detection) builds a spine instead. -margins sets the margin within which a strap may move -- default 0, which means an exact position or no strap at all, a real constraint if you need flexible strap placement rather than fixed coordinates.

Technical Reference DiagramHow does create_clock_straps decide whether it's building a mesh or a spine, and what does -margins actually control?

Technical Explanation

  • The -type option per direction decides the topology: -type stripe in both directions builds a mesh (2D grid); one direction set to user_route with the orthogonal direction using detect builds a spine structure instead.
  • -margins sets the margin within which a strap may move from its specified position -- the default is 0, meaning exact position or no strap at all, not a soft placement suggestion.
  • -grid accepts either a single distance (one strap), an iterator list (start/end/increment for multiple straps in one direction), or a list-of-lists for both directions at once (horizontal specified first).
  • -allow_floating true permits straps unconnected to orthogonal straps, which is NOT allowed by default -- floating straps require this explicit opt-in.
  • -bias/-bias_to_nets/-bias_margins provide shielding by biasing strap position relative to PG nets or specific nets -- a signal-integrity feature layered on top of the basic mesh/spine geometry.

Formula Or Decision Rule

Mesh: both directions -type stripe. Spine: one direction -type user_route, detect on the orthogonal direction. -margins default 0 = exact position only.

What To Check

  • Warning sign: create_clock_straps produces fewer straps than expected, or straps land at unexpected positions.
  • Inspect: check the -margins value -- if left at default 0, straps that can't land at their exact specified position are simply not created, not moved nearby.
  • Correct: set an explicit non-zero -margins value if flexible strap placement was actually the intent.

Command Checks & Actions

ICC2create_clock_straps -nets [get_nets clk1_mesh] -layers {M7 M8} -widths {2.4 2.4} -types {stripe stripe} -grids {{20 1200 100} {60 980 150}}

Builds a mesh (both directions stripe).

ICC2create_clock_straps -types {stripe user_route}

Builds a spine structure instead (mixed types).

ICC2route_clock_straps -nets clk1_mesh

Routes to the created straps once geometry is defined.

Healthy, Suspicious & Hard-stop Results

  • Expected: the resulting structure (mesh or spine) matches the intended -type configuration, and strap count/positions match expectations given the -margins setting.
  • Investigate: fewer straps were created than the -grid specification implies -- check -margins first, since default 0 silently drops straps that can't land exactly.
  • Stop: a mesh was intended but -type configuration was actually set for a spine (or vice versa) -- verify the per-direction -type values match the intended topology before routing proceeds.

Common Mistake

The Trap: Assuming -margins is a soft/optional placement hint -- its default of 0 means exact position or no strap, a hard constraint that needs explicit relaxation if flexible placement is actually needed.

What The Interviewer Is Testing

Whether you know the precise mechanism distinguishing mesh from spine construction (the -type option per direction) and that -margins defaults to a hard, not soft, constraint.

Practical Example

Debug Scenario: create_clock_straps with -grids specifying 12 straps in one direction produces only 8 in the built structure. Checking -margins, it was left at the default 0 -- meaning straps that couldn't land at their exact computed position (due to existing obstructions) were simply not created rather than nudged nearby.

PnR Flow Mentor Guide

Read the complete 8-chapter PnR Flow Mentor Guide free on the web — library setup through placement, clock tree synthesis, routing, chip finishing, hierarchical implementation, and ECO, all the way to stream-out.

Explore PnR Flow Mentor Guide →

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.

Continue practising

Related PnR (Place & Route) questions

ExpertHow does the tool actually decide what counts as a "root net" for clock NDR purposes, and what's the edge case that can silently change that?ExpertHow does -bias_to_nets actually provide shielding on a clock mesh, and why would you want that specifically for clock straps?ExpertWhat is CCD (Concurrent Clock and Data optimization), and what does it actually change in the clock tree?ExpertWhat problem do via ladders actually solve on a clock tree, and where does insert_via_ladders fit in the clock_opt flow?