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

GF180MCU lef and tlef metal layers name mismatch and missing SITE definition #274

Closed
kareefardi opened this issue Aug 31, 2022 · 7 comments

Comments

@kareefardi
Copy link
Contributor

Not quite sure that this repo is the right place for this issue. gf180mcuC/libs.ref/gf180mcu_fd_sc_mcu7t5v0/lef/gf180mcu_fd_sc_mcu7t5v0.lef has uppercase metal layer names while gf180mcuC/libs.ref/gf180mcu_fd_sc_mcu7t5v0/techlef/gf180mcu_fd_sc_mcu7t5v0.tlef has Pascal case metal layer names (METAL1 vs Metal1). Furthermore, there are no SITE definitions in the techlef - nor the cells lef. Attached are build logs.
build_gf180mcu-2022-08-31-04-33-01.tar.gz

@kareefardi kareefardi changed the title GF180MCU lef and tlef metal layers name mismatch and missing SITE GF180MCU lef and tlef metal layers name mismatch and missing SITE definition Aug 31, 2022
@RTimothyEdwards
Copy link
Owner

This is an error in the Google repository and should be logged as an issue at either https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_sc_mcu7t5v0 or at https://github.com/google/globalfoundries-pdk-libs-gf180mcu. I expect Tim and Proppy would prefer if you just fix the technology LEF files and generate a pull request.

Note that this error also applies to the mcu9t5v0 standard cell library.

@mithro
Copy link
Contributor

mithro commented Aug 31, 2022

Please start with logging the issue.

The fastest solution will be for you to send a fix pull request but maybe someone from MABrains can help fix it too? @atorkmabrains

@kareefardi
Copy link
Contributor Author

I logged both issues and created PRs for the metal layer names miss-match issue. I am working through the CLA for the PRs.

@kareefardi
Copy link
Contributor Author

I have signed an individual CLA. I think someone needs to re-trigger the CI.

@atorkmabrains
Copy link

@kareefardi How can we help you?

@kareefardi
Copy link
Contributor Author

Fixed in google's repos

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

4 participants