open-source-silicon.dev

<https://github.com/The-OpenROAD-Project/OpenLane/issues/2030|#2030 Metal Spacing violation between interconnect and macro (sky130)>
Issue created by <https://github.com/Dolu1990|Dolu1990>
*Description*

Hi,

Got Detailed Routing step failing on multiple "violation type: Metal Spacing".  
They all seem of the same nature, comming from the interaction between the power network and the routed connection to openram macro pin.

Here are some screen shot to illustrate.  
Failing one :  
<https://user-images.githubusercontent.com/4832082/279002177-6f02e448-8ba7-4ea0-bb83-73c251eb76cc.png|image>

Location of one violation (bbox in blue) :  
violation type: Metal Spacing  
srcs: inst:GSharePlugin_logic_mem_counter net:net162  
bbox = ( 2175.18, 1227.87 ) - ( 2177.33, 1228.15 ) on Layer met4  
<https://user-images.githubusercontent.com/4832082/279002740-c52702fe-bff4-4813-b600-8c4aca161ee1.png|image>

Seems to me, that the presence of the power network (the chunky strips comming from the top) push the pin connection to go too close to the macro, generating the violation.

Note that were there is no power strip, the connection to the macro doesn't generate any violation. Happy connections :  
<https://user-images.githubusercontent.com/4832082/279004716-2100f53b-aee2-442b-ac77-3f95fd598415.png|image>

*Expected Behavior*

Routing not going as close to the macro to avoid the violation, but i know very little about asic design.  
Or maybe there would be a config to avoid the power strip going that close to the macro ?

*Environment report*

```
OpenLane Container (903a86a):/openlane$ python3 ./env.py issue-survey
open_pdks dd7771c384ed36b91a25e9f8b314355fc26561be
WARNING: issue-survey appears to be running inside the OpenLane
container.

This makes it difficult to rule out issues with your
environment.

Unless instructed specifically to do so, please run this command
outside the OpenLane container.
---

Kernel: Linux v5.15.0-84-generic
Distribution: centos 7
Python: v3.6.8 (OK)
OpenLane Git Version: 903a86ab59095207f3a096aeff8c8b8af899497c
pip: INSTALLED
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

903a86a 2023-10-09T07:48:41+03:00 Update OpenROAD (#2009) - Kareem Farid -  (grafted, HEAD -&gt; master, origin/master, origin/HEAD)
---
Git Remotes

origin	<https://github.com/The-OpenROAD-Project/OpenLane.git> (fetch)
origin	<https://github.com/The-OpenROAD-Project/OpenLane.git> (push)
```

*Reproduction material*

Manualy packaged :  
<https://github.com/The-OpenROAD-Project/OpenLane/files/13203518/issue.zip|issue.zip>

let's me know if you would like anything else.

*Relevant log output*

```
[INFO]: Running Detailed Routing (log: designs/nax/runs/run_4/logs/routing/27-detailed.log)...
[ERROR]: There are violations in the design after detailed routing.
[ERROR]: Total Number of violations is 18
[ERROR]: Step 27 (routing) failed with error:
-code 1 -level 0 -errorcode NONE -errorinfo {
    while executing
"throw_error"
    (procedure "quit_on_tr_drc" line 7)
    invoked from within
"quit_on_tr_drc"
    (procedure "detailed_routing_tritonroute" line 19)
    invoked from within
"detailed_routing_tritonroute {*}$args"
    (procedure "detailed_routing" line 2)
    invoked from within
"detailed_routing"
    (procedure "run_routing" line 32)
    invoked from within
"run_routing"
    (procedure "run_routing_step" line 7)
    invoked from within
"run_routing_step"} -errorline 1
[INFO]: Saving current set of views in 'designs/nax/runs/run_4/results/final'...
[INFO]: Generating final set of reports...
[INFO]: Created manufacturability report at 'designs/nax/runs/run_4/reports/manufacturability.rpt'.
[INFO]: Created metrics report at 'designs/nax/runs/run_4/reports/metrics.csv'.
[INFO]: Saving runtime environment...
[ERROR]: Flow failed.
[INFO]: The failure may have been because of the following warnings:
```
<https://github.com/The-OpenROAD-Project/OpenLane|The-OpenROAD-Project/OpenLane>