search

google / skywater-pdk

Open source process design kit for usage with SkyWater Technology Foundry's 130nm node.
https://skywater-pdk.rtfd.io
Apache License 2.0
3k stars 394 forks source link

Missing techfiles #47

Open kkiningh opened 4 years ago

kkiningh commented 4 years ago

I'm trying to use the pdk with Synopsys tools (DC/ICC2), but I don't see a vendor or interconnect techfile (.tf and .itf respectively) which is needed for place and route and parasitics extraction. Will those be added later or is there another way I can obtain them?

mithro commented 4 years ago

@kkiningh I don't believe anyone has used the PDK with th Synopsys tooling.

Is a .tf / .itf file the same as a "tech lef" file (.tlef)? If so, I will be publishing them shortly too.

kkiningh commented 4 years ago

I think the .tf can be generated from the .tlef but I'll have to look into how to do it.

mithro commented 4 years ago

Initial .tlef files where added in https://github.com/google/skywater-pdk/commit/4cbdbb5a735a8acd53c6247eb2bc23b9245329f8

mithro commented 4 years ago

@kkiningh - See also https://github.com/google/skywater-pdk/issues/62

20Mhz commented 4 years ago

I believe by tf you mean Milkyway tech file, information may overlap with TECH tlef. For parasitics you will still be missing the ITF file, needed to generate TLUplus used as parasitic lookup tables. Maybe you can try Wire Load Model to start with.

kkiningh commented 4 years ago

@20Mhz, yeah that's correct. I believe Milkyway supports a way to create a Milkyway library from a tlef and then exporting a techfile, although I've never tried it. You're right that the itf (from which the tluplus file can be generated) will still be missing.

@mithro I'm super busy for the next couple days, but I'll try to get around to trying to do this and report back soon.

20Mhz commented 4 years ago

I believe LEF does not have enough info to automatically generate a mw tech. A fair work around could be to get an OpenAccess db and use Custom Compiler exporting capability to produce a mw tech as a starting point. -- EDIT: I was able to read in LEF and output tf in Milkyway, just had to set a dummy lib, haven't tested the file yet

mithro commented 4 years ago

FYI - Full technology LEF files for the standard cells where merged in https://github.com/google/skywater-pdk/pull/68

rovinski commented 4 years ago

@mithro tech LEF is generally "good enough" for use in place-and-route tools for older nodes, e.g. 130nm. However, generally for timing signoff, designers would want to run a signoff-quality parasitic extraction which includes coupling capacitance. .itf, .qrcTechfile, etc. These checks are important for final power signoff, signal integrity signoff, and timing signoff.

20Mhz commented 4 years ago

I'm now blocked by missing tech to GDS mapping.

mithro commented 4 years ago

FYI - There is a spreadsheet at https://docs.google.com/spreadsheets/d/176OcP2h_TT_pDP2-zBLijlgFUP38LVgMQPlDtpLcrsk/edit which includes a lot of information about the layers.

@RTimothyEdwards has a bunch of useful resources at https://github.com/RTimothyEdwards/open_pdks (which will be eventually merged into this repository).

MohamedAliYounis commented 2 years ago

@mithro could you please tell me how to get .lib files from .lib.json?