@Amro Tork It's a bit all over the place right now. Let me package it up and share a link. It's using magic for DRC.

@Sean Cross Have you tried with

GRT_OBS

for sram macros?

I haven't tried that. I'm not familiar with that setting. Let me try with klayout first, then get back to you.

@Sean Cross: As with sky130, I did not implement special layers for the GF180MCU SRAM so that I could implement the various rule exceptions in the SRAM blocks, so there are numerous spacing violations when you run magic's DRC on a design with SRAM. Your choices are either to run DRC with klayout or to do what we did with the sky130 process before we had the klayout deck, which is to load the abstract view of the SRAM before reading the design GDS so that the DRC sees the abstract view of the SRAM and not the full layout.

Got it, that makes sense. Thanks for the clarification, @Tim Edwards!

>load the abstract view of the SRAM

@Tim Edwards is that as simple as

lef read path/to/gf-sram-ip-block.lef

?

Only slightly more complicated. You need to (1) Read the technology LEF; (2) read the SRAM LEF; (3) Run the

gds noduplicates true

command to make sure that the abstract view doesn't get overwritten by the GDS, and then (4) read the GDS. If you read the "maglef" view in the PDK, then it's just (1) Read the maglef file; (2) Run

gds noduplicates true

; (3) Read the GDS.