https://open-source-silicon.dev logo
Title
s

Sean Cross

02/13/2023, 10:32 AM
@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.
v

Vijayan Krishnan

02/13/2023, 10:49 AM
@Sean Cross Have you tried with
GRT_OBS
for sram macros?
can you attach
drc.rpt
?
s

Sean Cross

02/13/2023, 10:51 AM
I haven't tried that. I'm not familiar with that setting. Let me try with klayout first, then get back to you.
@Amro Tork I've uploaded a WIP to https://github.com/xobs/caravel-minimax/ and I'm running it with
RUN_KLAYOUT=1
now.
It routes, at least...
t

Tim Edwards

02/13/2023, 2:45 PM
@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.
s

Sean Cross

02/13/2023, 2:52 PM
Got it, that makes sense. Thanks for the clarification, @Tim Edwards!
p

proppy

02/14/2023, 1:27 AM
>load the abstract view of the SRAM
@Tim Edwards is that as simple as
lef read path/to/gf-sram-ip-block.lef
?
t

Tim Edwards

02/14/2023, 2:44 AM
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.