-
Notifications
You must be signed in to change notification settings - Fork 85
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
Magic extraction fails due to li1 pin and li1 obstruction overlaps #209
Comments
I also notice that we are using decap cells for almost all our fill. Just wanted to confirm that that is expected. |
I'm not sure when this happened, or why. The code that magic runs to generate the LEF views should be consistent in its policy (the original SkyWater cells are very inconsistent) in either putting both the local interconnect and metal1 on the power rails into the pin list, or just the metal1. For reasons I can't ascertain (yet), the buf_1 and buf_2 cells (possibly others) are including local interconnect in the power rails pin lists. I'll investigate. |
If you use all decap, make sure you use |
@antonblanchard : I have tracked this down to a minor difference in labeling between seven of the cells in the HD library (including buf_1 and buf_2) and all the others, plus an error in magic when dealing with labels during "lef write" when using the options applied by the open_pdks installation for the SkyWater standard cell libraries. I fixed the error in magic. Therefore if magic gets updated to version |
@RTimothyEdwards Thanks! I confirmed that this does fix the issue for me. |
I'm seeing many warnings when doing LEF/DEF level extraction:
Many of them are between
sky130_fd_sc_hd__buf_2
andsky130_fd_sc_hd__decap_12
. Looking atsky130_fd_sc_hd__decap_12.lef
, the li1 layer is made up entirely of an obstruction not a pin, which explains why we are seeing the errors. The original lef in the upstream PDK shows the li1 layer as a pin.The text was updated successfully, but these errors were encountered: