open-source-silicon.dev

Hi there, does anyone know why some symbols like launcher.sym, lab_pin.sym, etc are missing while opening the test schematic of gf180mcu pdk

ok so may be someone from efabless may answer. It's probably a configuration issue.
What do you get if you run xschem from the terminal and at the xschem prompt type:
`foreach i $pathlist {puts $i}`

IMG_20230121_154535.jpg

Its working if I create a softlink to xschem_library/devices in my pdk directory

yes this is a configuration issue, there is a `/usr/local/share/xschem/xschem_library` path. This means that lab_pin.sym in a schematic will be placed with a reference name as `devices/lab_pin.sym`, since concatenating the path and `devices/lab_pin.sym` gives the true filename. However if the objects in the test schematic do not have `devices/` before the symbol name you need to change the path to `/usr/local/share/xschem/xschem_library/devices`.
Creating a link does also work since the current directory will be searched. However its better to fix the path in the xschemrc.

Schematic does have devices/ prefixed in their reference name

But ig its checking only within the second directory

then please check if `/usr/local/share/xschem/xschem_library/device`s does exists and symbols are present there...

IMG_20230121_155838.jpg

it joins devices/ in reference name with pdk/.../gf180mcu_tests rather than pdk/.../xschem(which is in the path) to give the true filename

try to do `ls /usr/local/share/xschem/xschem_library/devices` at the xschem prompt. is the directory accessible from xschem?

ok this is the reason. xschem is probably running in a sandboxed container. You need to be able to access /usr/local/share/xschem from within the container.
But i am not using containers, so I hope some efabless guys kick in...

try to put the issue in <#C03R1GRP9LG|gf180mcu> I think most of the people now use this pdk through volare.