Skip to content
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

LEF/DEF import mixes up layers #700

Closed
antonblanchard opened this issue Jan 1, 2021 · 3 comments
Closed

LEF/DEF import mixes up layers #700

antonblanchard opened this issue Jan 1, 2021 · 3 comments

Comments

@antonblanchard
Copy link

The following test case shows the met4 layer as cldntm.mask: klayout-def-layer-issue.tar.gz

It looks like klayout is truncating the layer numbers and met4 71 is getting mapped to cldntm.mask 11. If I remove cldntm.mask from the layer properties file, met4 is shown correctly.

@klayoutmatthias
Copy link
Collaborator

@antonblanchard Thanks for the test case.

I actually don't see any layer mapping from LEF/DEF to GDS layers inside the tech file. The layer numbers are auto-assigned and 11 is simple the next available layer.

To fix this, the tech file needs a LEF/DEF reader layer mapping. This will tell the reader how to translate a layer name/purpose combination from LEF/DEF into GDS layer/datatype.

I have attached an enhanced version of the .lyt file, but that's only halfway done. I just included the metal and via layers as far as I could identify them. I assume you took that from somewhere so maybe you can feedback this enhancement request there.

The LEF/DEF input layer map is found in the technology manager under "Reader Options", "Layer Mapping" at the bottom of the LEF/DEF tab.

sky130A.zip

Matthias

@antonblanchard
Copy link
Author

@klayoutmatthias thank you for the detailed response, the issue makes sense to me now.

The file came from open_pdks, which has since been updated to use https://github.com/laurentc2/SKY130_for_KLayout/ . There are some LEF/DEF to GDS layer mappings, but it is incomplete. I'll raise an issue there about it.

@klayoutmatthias
Copy link
Collaborator

I think this is not a KLayout bug, so I'll close this topic for now.

Thanks,

Matthias

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants