gadfort
commented
3 months ago @ubfx If the models from google are buggy and the ones from open_pdks have already been patched, you could use those. As long as they have a LICENSE / attribution (README) associated with them it should be okay (just need to double check the licenses, but I think its fine). The main thing for the attribution is just to indicate the repo and commit ID they came from + any modifications (if any).
I suppose they should go in /lambdapdk/sky130/libs/sky130hd/verilog/.
Hi everyone,
since siliconcompiler has now "officially" moved to lambdapdk, I would like to raise the topic of Verilog models here. We're currently working on some Open Hardware for which we are building a siliconcompiler based reference flow including RTL and gate level simulation steps for SKY130. However, simulation in general and especially back-annotated GLS still seems to be a bit of a blind spot in the Open Source flows. One reason is probably the faulty Verilog models in the upstream google repo and that they are missing in the siliconcompiler provided PDK (now lambdapdk).
I have created a discussion in the siliconcompiler forums on the topic. Long story short: I would like to contribute to sc/lambdapdk the necessary components to get annotated GLS working "out of the box" for SKY130. As a first step, I'm looking for an accepted way to get the necessary Verilog models (potentially from efabless or our own, patched version of the upstream google models) into lambdapdk.