IntermediateQuestion 161 of 162Source: Synopsys ICC2 Implementation User Guide: Routing

What changes when routing across voltage areas?

From PDVerse PnR Interview Handbook · pdVerse Mentor Guide

Short Answer

Signals crossing between voltage areas must go through the right isolation cells or level shifters, and the router must not create physical paths that break the power intent. Voltage area rules control whether nets may pass through an area and whether buffers can be added there. Cells with secondary power pins, such as always-on buffers, also need those pins routed to the correct supply.

Technical Reference DiagramWhat changes when routing across voltage areas?
Two voltage areas with a signal crossing between them through a level shifter, and an always-on net highlighted as it passes through a switchable area.

Technical Explanation

  • A voltage area is a region of the layout tied to a power domain. Cells inside it run from that domain's supplies.
  • A signal crossing between domains at different voltages needs a level shifter, and one leaving a domain that can be switched off needs isolation. These cells come from the power intent, and routing must connect them as intended, not bypass them.
  • By default, physical feedthrough nets are allowed through voltage areas. create_voltage_area_rule with -allow_pass_through false stops that, so nets detour around the area instead.
  • Voltage area rules also control buffering: whether new cells, buffers and physical or logical feedthroughs are allowed. This matters when routing and optimization add buffers on long nets.
  • Cells like always-on buffers have secondary power and ground pins. They need is_secondary_pg and port_type attributes in the frame view, and they are routed with route_group on the supply net, for example the always-on supply.
  • check_routes reports voltage area violations, and check_mv_design checks the multivoltage design for power intent problems.
  • Always-on nets passing through a switchable area should be buffered only with always-on cells powered from the always-on supply.

What To Check

  • check_mv_design result after routing and any ECO.
  • Voltage area violations from check_routes.
  • That secondary PG pins are all connected to the intended supply.
  • Nets passing through voltage areas where pass-through should not be allowed.

Command Checks & Actions

ICC2create_voltage_area_rule -name VA1_rule -voltage_areas VA1 -allow_pass_through false

Stops physical feedthrough nets from crossing voltage area VA1.

ICC2route_group -nets VDD_AON

Routes the secondary power pins of always-on cells to the always-on supply net.

ICC2check_mv_design

Checks the design for multivoltage and power intent violations.

ICC2check_routes

Includes voltage area violations along with DRCs and opens.

Healthy, Suspicious & Hard-stop Results

  • Healthy (illustrative): check_mv_design clean, no voltage area violations, and every secondary PG pin connected.
  • Suspicious (illustrative): A few nets crossing a voltage area they should avoid, found before signoff and rerouted.
  • Hard stop: A domain-crossing signal routed without its level shifter or isolation, or an always-on buffer whose secondary pin is unconnected.

Common Mistake

The Trap: Letting optimization buffer a long always-on net inside a switchable area with an ordinary buffer. The buffer is powered from the switchable supply, so when the domain turns off, the always-on signal dies with it. A voltage area rule with -allow_buffering false on that area would have kept the buffer out, or the buffer had to be an always-on cell on the always-on supply.

What The Interviewer Is Testing

  • Whether you know voltage area rules and what they control.
  • Do you know how secondary PG pins are routed?
  • A strong answer shows you check with multivoltage checks, not just DRC.

Follow-up Question & Model Response

"Why would you forbid nets from passing through a voltage area at all?"

Candidate Model Response: A net passing through an area that can be switched off is at risk if anything along it needs buffering, because a buffer placed there would be powered by that area. There can also be noise or layout concerns in sensitive domains. Forbidding pass-through makes nets detour around, which costs wire length, but guarantees nothing in that domain carries unrelated signals.

Practical Example

Tapeout Scenario: A block has a switchable domain PD_SW and an always-on domain (illustrative). Twelve nets from the always-on logic cross PD_SW on their way to an interface. The team sets create_voltage_area_rule -name sw_rule -voltage_areas VA_SW -allow_pass_through false, and those nets detour, adding about 60 um each. Four always-on buffers inside PD_SW that drive the power switch enable chain have secondary power pins, which route_group -nets VDD_AON connects. check_mv_design and check_routes then both come back clean.

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.

Low-Power VLSI & UPF Handbook — nine chaptersLow-Power & UPFDomains, isolation, retention, and multivoltage UPF. →