jplian
08/03/2022, 2:00 AMMitch Bailey
08/03/2022, 2:29 AMopen_pdks
kept the skywater_pdk
repo around so it was easy to check the installed version of the pdk there with git describe
. However, with the current volare installation, I could not find what skywater_pdk
commit was used.
There is a json file pdks/volare/sky130/versions/41c0908b47130d5675ff8484255b43f66463a7d6/sky130A/.config/nodeinfo.json
, but the information there wasn't too helpful in regards to skywater_pdk
. Is there any way to tell which commit of skywater_pdk
was used to build the pdk?
{
"foundry": "SW",
"foundry-name": "SkyWater",
"node": "sky130A",
"feature-size": "130nm",
"status": "active",
"description": "Skywater 0.13um CMOS, local interconntect + high-resistance poly + 5 metal layer backend stack + MiM caps + redistribution layer 1",
"options": [
"METAL5",
"MIM",
"REDISTRIBUTION"
],
"stdcells": {
"sky130_fd_sc_hd": "@:libraries/sky130_fd_sc_hd/latest",
"sky130_fd_sc_hdll": "unknown",
"sky130_fd_sc_hs": "unknown",
"sky130_fd_sc_hvl": "@:libraries/sky130_fd_sc_hvl/latest",
"sky130_fd_sc_lp": "unknown",
"sky130_fd_sc_ls": "unknown",
"sky130_fd_sc_ms": "unknown",
"sky130_osu_sc_t12": "unknown",
"sky130_osu_sc_t15": "unknown",
"sky130_osu_sc_t18": "unknown"
},
"iocells": {
"sky130_fd_io": "@:libraries/sky130_fd_io/latest"
},
"primitive": {
"sky130_fd_pr": "@:libraries/sky130_fd_pr/latest"
},
"memory": {
"sky130_sram_macros": "c2333394e0b0b9d9d71185678a8d8087715d5e3b"
},
"other": {
"sky130_ml_xx_hd": "6eb3b0718552b034f1bf1870285ff135e3fb2dcb"
},
"build": {
"open_pdks": "1.0.309",
"magic": "8.3.277"
},
"commit": {
"open_pdks": "41c0908b47130d5675ff8484255b43f66463a7d6",
"magic": ""
}
}
Tim Edwards
08/03/2022, 12:34 PMskywater-pdk
itself, although the open_pdks installer uses nothing from the skywater-pdk
repository; the only content is from the submodules themselves, which is why they are called out individually. I only clone the top level repository because it requires running make timing
from the top level (possibly make timing
can be run within the submodules; I have not checked that possibility). But I do not know where this @:libraries/...
content comes from. Every entry should be followed by a commit hash except for the entries in build
, which are version numbers/git tags. The JSON file you posted, though, it outdated, because there is supposed to be another section at the bottom called reference
, which doesn't make any difference here, but I thought that Donn had merged that into Volare, so I'm wondering if the file above is up-to-date.Linen is a search-engine friendly community platform. We offer integrations with existing Slack/Discord communities and make those conversations Google-searchable.
Powered by