Hi, is there a release checklist for the things to take into account before doing a submission? From what I see, I need to:
1) Pass the gf180mcu-precheck
2) Make sure the QR code is correct (what info should it contain?)
3) Are there naming conventions to follow?
4) Are there special ways in which we should save the output file?
5) Are there non DRC check we would need to run (e.g: zero size polygons)?
For the IHP tapeout, there was an issue with different guidelines, maybe something similar could be made?
I'm asking because I will do an analog tapeout and thus will not use the librelane flow. I will also have to modify the padring dimension and bond the chips myself.
Hi @Clyde Laforge!
All of these checks should be handled by the precheck. The precheck runs both the magic and KLayout DRC setup, offgrid and angle checks, density checks etc. We might need to add a zero size polygon check.
You only need to include the QR-Code cell in your design. During the precheck, its content will be replaced with the correct ID for your design.
Currently, there is no check on the file and top-level cell naming, but we might require both to be named the same. I will also add a check for the die size, since for the first run all designs will be the same size.
But other than that you are free to do what you want. You can create the GDS with LibreLane or any other software. Just make sure to pass the precheck.
If anything is not caught by the precheck and flagged by the foundry, we will make sure to improve the precheck.
Likewise, if you manage to break the precheck, please let us know so we can improve it :)
Thanks Uri! I'm torn between just reporting an error on zero size polygons (with a report), so the problem is fixed upstream/in the design. Or to delete these shapes as done in the script. I think I prefer to modify the original layout as little as possible.
Summary
Implements automated manufacturability checking for GDS design files using the gf180mcu-precheck tool in Docker containers. This includes export compliance certification requirements and co...
1
10:00 p.m.
But I'm currently fighting with the download pathway
Summary
This PR implements a comprehensive content extraction pipeline for processing GDS and OASIS files from various sources, including support for compressed archives and GitHub Actions artifact...
1
1
2
1
1