Daniel Schultz
Daniel Schultz
@sergeiandreyev @KrzysztofHerman FYI bumping the PDK here to update the platform config to match with changed metal routing direction.
My fault. Copied the specify block wrongly from the stdcells. I honestly don't know if this correct since timings are just added with 0 delay. At least it shouldn't break...
There was an older issue related to M2 minimum area violations: https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/issues/1681
@maliberty I haven't seen this issue with the i2c-gpio-expander but I have another, bigger design that has 12 M2.d violations related to too small vias. How can I send someone...
@maliberty sorry, a little bit busy right now with other stuff. I can share the GDS. So, will open an issue in the next days. Thanks!
@maliberty April tape-out is over and I had to fix 28 M2 violations by hand. So, I'm ready to help getting this issue fixed. Do you need some more stuff...
@maliberty let me prepare you an ORFS branch with a slightly smaller design. My current design is 6mm2 and takes pretty long to layout.
@maliberty I pushed an example chip here which will generate M2.d errors: https://github.com/dnltz/OpenROAD-flow-scripts/pull/new/WIP/dnltz/elemrv-for-m2d
I also pushed a simple DRC `sg13g2_quick_m2d.lydrc` to only check this error (takes 30sec to run). Do you know how run DRC?
@maliberty is that what you were asking for? https://fileshare.phytec.com/index.php/s/e6CY8JeEi9d66BW