The top cell name is different, causing an error. How should I fix this?
I tried the following here, but it didn't work.
1. Set the top cell name to "top".
2. Set the top cell name to match the file name.
Setting the top cell name to "$$$CONTEXT_INFO$$$" executed it. It is currently running.
Noritsuna Imamura
The top cell name is different, causing an error. How should I fix this?
I tried the following here, but it didn't work.
1. Set the top cell name to "top".
2. Set the top cell name to match the file name.
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...
Does this flow re-run DRCs? I have an issue right now that my design is flagged by both klayout and magic but the issues are all inside the (9t) foundry cells, and we think the DRCs are spurious. I haven't submitted yet, was just wondering.
KLayout violations The clock gating cell icgtp_1 is flagged with the following by klayout: CO.6a : (i) Metal1 (< 0.34um) end-of-line overlap contact (Applies to all < 0.34µm wide metal lines,...
Thanks. For this run are we happy to manually waive DRCs inside of foundry cells? Hoping there will be time to straighten things out after the first shuttle
The online platform runs the precheck: https://github.com/wafer-space/gf180mcu-precheck
This includes a number of smaller checks, but also KLayout and magic DRC.
@LukeW in your case we might need to do a manual submission, since the online precheck will fail.
Ok thanks, I'll make sure to go through my DRCs again before submission and check it is just the known ones in the foundry cells, and will attach my DRC logs in case you want to check against the precheck output. Also let me know if you want my GDS a little earlier than the deadline