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 SRAM macros causing illegal overlap #332

Open
bman12three4 opened this issue Nov 7, 2023 · 1 comment
Open

gf180mcu SRAM macros causing illegal overlap #332

bman12three4 opened this issue Nov 7, 2023 · 1 comment

Comments

@bman12three4
Copy link

Trying to insert a "gf180mcu_fd_ip_sram__sram128x8m8wm1" instance into my design causes an error in step 39: Magic Spice Export.

box 42812 93688 42868 93776
feedback add "Illegal overlap between obsv2 and metal2 (types do not connect)" medium
box 43484 93688 43540 93776
feedback add "Illegal overlap between obsv2 and metal2 (types do not connect)" medium
box 44380 93688 44436 93776
feedback add "Illegal overlap between obsv2 and metal2 (types do not connect)" medium

I also had to add /// sta-blackbox to the source file in libs.reg in order for it to synthesize.

tag: gfmpw-1b
pdk: gf180mcuD (gf180mcuC is not in the makefile)

@RTimothyEdwards
Copy link
Contributor

The vendor (GF) LEF file for the SRAM covers the entire macro with via1 and via2 obstruction, which is causing issues in magic; I noted last week that there is an issue in the magic code that is preventing me from simply ignoring the via1 and via2 obstruction layers. Instead I reworked the open_pdks makefile to create the SRAM LEF view from scratch, but that update has not been pushed yet. I will try to get that done today.

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