Hi i got error regarding the Model i unable to resolve it Please help me screenshot attached could you tell me from when i got colour meaning of wire after simulation @Stefan Schippers @Eric

My guess: Library is included incorrectly

@Arman Avetisyan can you guide me how to solve it

Show the "tt corners" and tell me where your pdk is installed

tt corners : screenshot i am using xschem via docker image

which docker image

I am using iic-osic-tools docker image i attached two files .out and .spice

can you post the output of the command: ls /foss/pdk/sky130A/libs.tech/ngspice/

docker image version : latest (specific not mentioned )

It seems its broken. Try using sky130 libraries corner.sym. Does that one work?

@Arman Avetisyan thank you for your reply could you please tell me how to use sky130 libraries corner.sym

@Ashutosh Kumar

pfet_01v8_lvt

minimum channel length is 0.35.

@Stefan Schippers thank you so much for your reply but how i know the constrain of the such devices while generating netlist colour of some wire changes how i know what's its meaning . thank you again :)

@Ashutosh Kumar After doing a netlist do View->Show ERC info window. Coloured nets are usually warnings. Press Shift-k to clear all colors, then press the netlist button then read the ERC (Electrical Rule Check) dialog box to see the warnings. Some can be ignored, some might reveal a problem in the circuit.

great @Stefan Schippers is possible to extract the output result in .csv format thank you again :)

@Ashutosh Kumar Yes it is possible, but this is not really a feature of xschem, it's just a matter of choosing the right corner (mc, or tt_mm for mismatch or other similar) and writing a loop of N simulations that ngspice will execute. Xschem has the ability to read multi-dataset raw files and show waveforms directly, The

xschem_sky130

libraries have a couple of examples (

tb_bandgap.sch

,

test_comparator.sch

) that perform mismatch simulations. Mismatch is just like Montecarlo where every single transistor gets different process parameters (mobility, threshold and others). Montecarlo usually involves global process variations across simulation runs.

@Stefan Schippers thank you once again for your reply

@Ashutosh Kumar for CSV see this thread.

@Stefan Schippers thank you :)