-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing metal fill in power ring and IO cells #5114
Comments
Adding the DIE_AREA as parameter to |
You can put large files in gdrive (or equivalent) and provide a link here. |
It would be helpful to see what those layers look like in the OR gui. Perhaps the IOs are marked as OBS. |
By default we only fill the core area. If you want to fill the die area you can use the -area flag. |
-area looks to be operating in dbu rather than microns. I'll fix that but you can scale the area to see if it helps. |
What's the difference between dbu and microns? Edit: Found it https://openroad.readthedocs.io/en/latest/contrib/DatabaseMath.html |
https://fileshare.phytec.com/index.php/s/4G7nFdTPLpNTRpc Can you download that? |
Units addressed in #5115 - for IHP the conversion factor is 1000 |
It comes from the LEF. Filling inside the cell would be dangerous as without the OBS we would likely see it all as empty space to be filled. |
There are three ways to generate fill: openroad, magic and klayout.
|
OR doesn't do FEOL fill so you'll likely need a second tool to handle that in any case. In the longer term I think it makes sense to fill the core with OR, once it is timing aware, and then fill the periphery with a pure GDS tool. That thinking is why the default is the core area. |
Slightly off-topic, but using this design as an example: The current design finish stage using klayout with klayout.tcl calling def2stream.py can be replaced by strm2gds or strm2oas. The one thing strm2oas can't do is to add a searing reference to the def DESIGN. q1) Is there a specific reason to have 551894 instance and net names as properties in the gds ? q2) it seem geometry and fill in the sealring is overlapping the bondpads, is this intentional ? q3) nor2b_1 and nor2b_2 are the only cells with a boundary layer 235, is this intentional ? q4) The following two entries in the .map file are ignored by strm2oas and should be commented out.
klayout ElemRV.txt
|
Describe the bug
OpenROAD can add metal fill correctly to the core area but is missing the area where the power ring and IO cells are located. See screenshots for more details.
The current design doesn't meet the ihp-sg13g2 DRC checks regarding some min density rules of 35%.
Expected Behavior
I was expecting the entire DIE area, not only the CORE area, gets filled with metal.
Environment
To Reproduce
External Link
Relevant log output
No response
Screenshots
Metal2 fill
Metal3 fill
Additional Context
No response
The text was updated successfully, but these errors were encountered: