open-source-silicon.dev

<@U017X0NM2E7> when I do openlane I see it uses sca130hd library but I have been using scs130ms library. Why does openlane choose to use scs130hd library  high density

<@U053UFMPKDW> I think there’s a `STD_CELL_LIBRARY` variable. Check your `openlane/&lt;cell&gt;/runs/&lt;timestamp&gt;/config.tcl` file for the full set of variables used.

<@U053UFMPKDW> I'm not sure but I believe the `hd` library is maintained to a much greater degree than any other variant of the sky130 library. I've only ever seen customers use `hd`

By the way, the *<https://skywater-pdk.readthedocs.io/en/main/contents/libraries.html#library-naming|convention for naming sky130 cells>* is `sky130_fd_sc_...` not `scs130...` -- what you're seeing might be Cadence recognizing the cells differently (or at least the correct cells, but just with a different naming convention). I don't know Cadence or how it handles the PDKs, but I'm aware that there's a closed Cadence S130 PDK (which is very similar but not exactly the same) and a Cadence-specific open-source sky130 that is (from what I understand) quite a lot older than the one required by SkyWater through our sky130 fabrication. That may not be relevant at all to you, but I thought I would point it out anyway in case it explains what you're seeing.

In any case, our default OpenLane installation (which, in Caravel and Caravan is automatic and includes the PDK if you installed via "make setup") should already use the correct open source sky130 PDK, logged by `openlane/&lt;cell&gt;/runs/&lt;timestamp&gt;/config.tcl` (as Mitch said) to help you confirm.