Hi @Stefan Schippers I got an error when simulating a bandgap as shown. Here, I want to describe what I did 1- I used bandgap_tb_tc.spice with bandgap_lvs.spice which is generated from the layout 2- I opened a terminal and wrote ngspice bandgap_tb_tc.spice and found the shown error. what does it mean this error to fix it, please? Thanks

@Ahmed Reda I couldn’t find any pnp models in the corner files for ngspice. There is

sky130A/libs.tech/ngspice/sky130_fd_pr__model__pnp.model.spice:.include "../../libs.ref/sky130_fd_pr/spice/sky130_fd_pr__pnp_05v5_W0p68L0p68.model.spice"
sky130A/libs.tech/ngspice/sky130_fd_pr__model__pnp.model.spice:.include "../../libs.ref/sky130_fd_pr/spice/sky130_fd_pr__pnp_05v5_W3p40L3p40.model.spice"

but these are discrete models that aren’t extracted from gds (but should be extractable from magic). Could you modify your extracted spice model to either

sky130_fd_pr__pnp_05v5_W0p68L0p68

or

sky130_fd_pr__pnp_05v5_W3p40L3p40

, include

sky130A/libs.tech/ngspice/sky130_fd_pr__model__pnp.model.spice

and see if that works? May need a change to the pdk.

Exactly, I have a bandgap test schematic and using

sky130_fd_pr__pnp_05v5_W3p40L3p40

. try to manually change the pnp model names in bandgap_lvs.spice. Also remove the

area=..

parameter, these pnp models are not parametric, they have a fixed layout (and setting area to 0 is nonsense either).

@Stefan Schippers @Mitch Bailey really Thank you for you suggestions. The error has been fixed. Is there another way to get extracted spice correctly instead of magic!