Do we have to disable the magic drc check when using the SRAM macro?

The EF_SRAM_1024x32?

sky130_sram_2kbyte_1rw1r

You need to refresh your clone of the data. You cannot tape out any of the openRAMs with design rule errors. The ones in the repo should be fixed.

No the problem is "Magic DRC Check" for user_project_wrapper runs forever when I include the SRAM macro, it seems like a popular issue and it is been suggested to disable the magic drc check in other forum posts. That's why I am wondering?

The way Efabless platform precheck handles this is to substitute the abstract (LEF) view of the SRAM for the detailed version when running DRC.

@Tim Edwards Can you explain to me how I can do this locally?

First off, make sure you're using an SRAM block from the

sky130_sram_macros

PDK library; the name for the block you're using is

sky130_sram_2kbyte_1rw1r_32x512_8

(maybe this is the block you're using and you didn't include the suffix?). The PDK library has a magic-compatible abstract view in

sky130A/libs.ref/sky130_sram_macros/maglef/sky130_sram_2kbyte_1rw1r_32x512_8

. In magic, you would load the design containing the SRAM, then do

cellname filepath sky130_sram_2kbyte_1rw1r_32x512_8 $PDK_ROOT/sky130A/libs.ref/sky130_sram_macros/maglef; flush sky130_sram_2kbyte_1rw1r_32x512_8

. This will substitute the SRAM abstract view, and then the DRC should ignore the SRAM and give you only errors that exist outside the SRAM block.

@Tim Edwards this was what I wanted to talk to you about the other day. I created a PR on some repo that I thought you owned but I couldn’t find it when I went back to look. I’ll update this one if I haven’t yet done so.

@David Lindley: Gotcha. That repository was https://github.com/efabless/sky130_sram_macros and I can see the pull request from you. I will take care of it.

Cool! Thanks!

@David Lindley: Sorry I didn't take care of that earlier (like 3+ months ago when it was posted). Either I'm not getting emails for that repository or I was just too swamped with things in July. I have merged the pull request and am now running the open_pdks compile to confirm.

I kept meaning to ask you about it but it kept slipping my mind. Thanks Tim.

@Tim Edwards I am using the sky130_sram_2kbyte_1rw1r_32x512_8 SRAM macro found inside the user_caravel_project/dependencies/pdks/..../sky130_sram_macros folder. But there is no maglef directory in there. Also I'm not quite sure how to execute the steps you mentioned above since I just run make user_project_wrapper and let that perform the magic drc check.

@Jazoolee Ahamed: That is the correct path if the PDK was installed in the project dependencies. Normally that comes from volare, and normally the maglef/ directory is part of the distribution. But you redacted the interesting part of the path which gives the volare git commit hash. What is the full path for

user_caravel_project/dependencies/pdks/..../sky130_sram_macros

?

I am getting this error for the online precheck, what can I do?