Hi all,
I'm constantly having problems when doing netlist extraction with magic on gds files created with klayout.
The
.zip
file contains the temperature sensor developed on Chipalooza, and it compares the extraction of the gds and a flattened version generated with a python script.
To flatten the gds, I'm using a klayout python script that removes the labels on the child cells (labels and pins), and then both gds are compared with netgen. Most of the results are written on
extract.sh
. Please read that file.
After the analysis I have some questions:
About the problem
- Is the separation of the vias on different cells (
vias_gen*
,
via_dev*
) the cause of the problems?
- A lot of duplicated stdcells are generated. Is this a problem? How can I avoid this?
About tool usage and capabilities
- How to properly extract layouts made with klayout? It's seems to be required to flatten the design before loading it on magic.
- PEX netlists only match after removing parasitics. Is possible that magic gives different parasitics for the same design?
- There's a way to "merge" an instance of a cell with it's parent when when reading a gds on magic? Avoiding the flattening of the parent
- Removing the labels from child cells before flatten the
TOP
cell could cause an error?
About debugging
- How can we debug extraction inconsistencies on magic? I'm aware of the
feedback
command. That's the only alternative?
- Can we get
feedback
extraction information per cell?
- Is there a way to store in a gds an
error layer
with a message? I want to turn feedback report into a gds.
@Tim Edwards @Mitch Bailey @Amro Tork