Replies: 1 comment 1 reply
-
I've converted this to an issue as it is not a discussion. Please file such directly in the future as it gives us more information. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am using my own custom technology files that I created.
In this kit, I must have a spacing of 2 micon (yes it's huge) between Via1 and Via2 layers.
(I'll add a .zip with the complete tech that you can run if you put it in flow/platform)
In my LEF describing the cells, I am pushing the information on where are the Via1 by using the OBS definition. Here is a short cut of a file :
In my tech LEF definition, I have the following statements for Via1 and Via2 statements :
and
The
SPACING 2 SAMENET LAYER Via1 ;
is the statement describing the distance between the two layers. I repeteaded this statement for the Via1 description in the hopes it fizes my problem but it didnt.Most of the time, the router does it's job to avoid putting Via2 close to Via1, but in some instance, it fails.


For example
This is unnacceptable (X:126.8 Y:299) :
And this is ok :
Overall, I have around 30 mistakes over my circuit, which is not much but still a bit bizzare.
Do you have any insight on how the .LEF are treated and what should I change to assure that they are spaced of 2um at all times?
In this .zip, I've replicated the OpenRoad folder tree and added my design plus my tech files.
flow.zip
Let me know if anything else is required.
Many thanks.
Beta Was this translation helpful? Give feedback.
All reactions