@User: You should not use the "raw" techfile in magic/sky130.tech. If you have the latest version of

open_pdks

and you want only the magic techfile, then do

cd sky130

and

make tools-a

, then use

sky130/sky130A/libs.tech/magic/sky130A.tech

. (With the most recent

open_pdks

version, it is I think necessary to do

./configure

first from the top-level directory; there are two "mandatory" things to set during configure, although they are not needed for the command as I wrote it above, and can be set to any throw-away value.) Also note that

open_pdks

installs a file

sky130A.magicrc

which is better to use, since it has a few additional setup items. So

magic -rcfile sky130A.magicrc

is generally preferred to

magic -T sky130A.tech

. What I usually do is to copy the

sky130A.magicrc

file to the directory where I'm doing layout, as

.magicrc

. Then all I need to do to start magic is just

magic

, and it will automatically read

.magicrc

, which will automatically load the right tech file.

Thank you for the guidance, @Tim Edwards. I was also using the "raw" techfile in magic/sky130.tech. Though I am stumped at

run_magic_spice_export

when I run this step in openlane I get an error which says your _*component_xyz*_ could not be read and that you might not have read the LEF file of it. Similarly, if I do

drc check

after loading the design in magic it gives a similar error of not being able to read

run_magic_spice_export

is a script in openlane, so you would need to raise the issue in the #openlane channel because I don't know what's in the script. However, the fact that the path has "home" without a leading "/" suggests that magic is out of date; that error was corrected in 8.3.54 (September 5).

Thank you, I would look into it

@Wajeh ul hasan: First, which version of magic? I do agressive development with both the techfile and the tool, and sometimes have to add things to the techfile format which break magic, so make sure you have the most recent from the repository. If that doesn't fix the problem, then you will need to run under the debugger; which means running (for a typical install)

gdb /usr/local/lib/magic/tcl/magicexec

and then getting a backtrace after it segfaults.

Thanks, by updating the magic to 8.3 solved the issue