https://open-source-silicon.dev logo
Join Slack
Powered by
Hi, I'm trying to install gf180mcu with open_pdks ...
# open_pdks
a
Hi, I'm trying to install gf180mcu with open_pdks but there's some unexpected behavior • Tool disable flags are not working (
--disable-xcircuit
, etc). this seems not so important but it would be nice to avoid unnecesary processing. • Using 
--with-gf180mcu-variants=D
make the 
sudo make install
step fail. Is possible to avoid installing all the variants? • I don't want to use all modules on gf180mcu, specifically 9t5v0, sram and osu-sc. It's possible or it will trigger an issue? This is the command I've tested.
Copy code
./configure --enable-klayout --enable-magic --enable-netgen --enable-xschem --enable-irsim=no --enable-openlane=no --enable-qflow=no --enable-xcircuit=no --disable-sky130-pdk --disable-primitive-sky130 --disable-io-sky130 --disable-sc-hs-sky130 --disable-sc-ms-sky130 --disable-sc-ls-sky130 --disable-sc-lp-sky130 --disable-sc-hd-sky130 --disable-sc-hdll-sky130 --disable-sc-hvl-sky130 --disable-alpha-sky130 --disable-xschem-sky130 --disable-klayout-sky130 --disable-precheck-sky130 --disable-sram-sky130 --disable-sram-space-sky130 --disable-reram-sky130 --disable-osu-t12-sky130 --disable-osu-t15-sky130 --disable-osu-t18-sky130 --enable-gf180mcu-pdk --with-gf180mcu-variants=D --enable-primitive-gf180mcu --enable-verification-gf180mcu --enable-io-gf180mcu --enable-sc-7t5v0-gf180mcu --disable-sc-9t5v0-gf180mcu --disable-sram-gf180mcu --disable-osu-sc-gf180mcu
In the case that all the variants should be compiled, they have dependencies between them? I can delete manually A B and C to stay only with D? I've been doing that on volare, I suppose it's the same here
v
yes.. use volare.. same data present here and easy to install
a
I'm using volare in my stable setup, but open_pdks almost always is a lot of commits ahead. I want to use open_pdks to see latests changes in case of finding bugs and problems related. I've saw that gf180mcuA uses 1GB while gf180mcuD only uses 90MB, so it seems that there's a lot of dependencies and shared content between them.
t
Yes, the gf180mcuA is the "base" PDK and the rest of the variants will make symbolic links back to it in the case of redundancies (of which there are a lot). So it's always going to be about 1GB for the first variant you install and 90MB overhead for any additional ones (more or less).
I probably have not been paying attention to whether the individual tool enables/disables work because they all have very low overhead compared to the PDK libraries. Feel free to post it as an issue to the github issue tracker for open_pdks.
Both PDKs should be disabled by default, and when any PDK is disabled, all of its component libraries are disabled; so 
--disable-sky130-pdk
is not needed, and neither are the individual libraries like 
--disable-sc-hd-sky130
, etc. For a single variant: What you want is
Copy code
./configure --enable-gf180mcu-pdk  --with-gf180mcu-variants=D --disable-sc-9t5v0-gf180mcu --disable-sram-gf180mcu
I am testing this now to see what happens on 
make install
.
@aquiles viza: I can duplicate the issue with the failure; 
make install
is apparently not paying attention to disabled variants.
13 Views
Open in Slack
PreviousNext
Powered by