Skip to content

Commit 0812b35

Browse files
authored
Merge pull request #2637 from Pinata-Consulting/docs-ROUTING_LAYER_ADJUSTMENT-color
docs: add some ROUTING_LAYER_ADJUSTMENT color
2 parents b18f57c + 523e374 commit 0812b35

File tree

1 file changed

+26
-1
lines changed

1 file changed

+26
-1
lines changed

flow/scripts/variables.yaml

Lines changed: 26 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,32 @@ TNS_END_PERCENT:
4242
- grt
4343
ROUTING_LAYER_ADJUSTMENT:
4444
default: 0.5
45-
description: Default routing layer adjustment
45+
description: >
46+
Adjusts routing layer capacities to manage congestion and
47+
improve detailed routing. High values ease detailed routing
48+
but risk excessive detours and long global routing times,
49+
while low values reduce global routing failure but can
50+
complicate detailed routing.
51+
52+
The global routing running time normally reduces
53+
dramatically(entirely design specific, but going from hours to
54+
minutes has been observed) when the value is
55+
low(such as 0.10).
56+
57+
Sometimes, global routing will succeed with lower values and
58+
fail with higher values. Exploring results with different
59+
values can help shed light on the problem. Start with
60+
a too low value, such as 0.10, and bisect
61+
to value that works by doing multiple global routing runs.
62+
63+
As a last resort, `make global_route_issue` and using
64+
the tools/OpenROAD/etc/deltaDebug.py can be useful to debug
65+
global routing errors. If there is something specific that is
66+
impossible to route, such as a clock line over a macro, global
67+
routing will terminate with DRC errors routes that could
68+
have been routed were it not for the specific impossible routes.
69+
deltaDebug.py should weed out the possible routes and leave
70+
a minimal failing case that pinpoints the problem.
4671
stages:
4772
- place
4873
- grt

0 commit comments

Comments
 (0)