In the second version I’m using 2 SRAM versions from the dev branch: Git clone -b dev https://github.com/efabless/sky130_sram_macros.git sky130_sram_1kbyte_1rw1r_32x256_8 sky130_sram_2kbyte_1rw_32x512_8 Surprisingly, I get 670MB of Magic DRC errors. The problem is, that when generating the .xml Magic DRC report file, precheck stalls after 6 hours. I guess I must kill that bug, but the 670 MB worries me. Am I taking the golden SRAM files from the right place ? In case you care: https://github.com/cloudxcc/TestRun_dev

You won't be able to run DRC on SRAMs in Magic. It doesn't handle the core memory design rules. When I do this in OpenRAM, I replace the bitcells with a "maglef" file which has the layers that violate standard design rules removed.

Thank you for your reply. I guess the point I wanted to make is, that the SRAMs in the dev branch are labeled as “DRC clean”, but when I use them, I get 50 MB Magic DRC violations in average (step 7 of precheck). I just wanted this to be confirmed in case I’m doing something wrong, regardless of the Magic DRC check is bogus or not. Local precheck stalls at the end of step 7 when converting 670MB violation report into klayout xml file after 6 hours. So I’m basically stuck there.