@Stefan Schippers Hey Stefan, I was wondering if we could add an option to netlist type called lvs-spice, with a different switch on symbols than spiceprefix? Could we do that easily?

We can, however tell me exactly what you need to do, will look into that

I need to make the generated for spice simulation different from the netlist generated for LVS purposes, here are 2 main changes that need to happen as starts for that: • Netlist devices as X sub circuits for all devices as needed by simulation models for simulation, but netlist same device as M, L, R, C, etc.. for LVS. • Need to define which parameters need to go to the LVS net list and which goes to the simulation netlist and if there are any equations for any parameters, they need to be evaluated for LVS net list.

The first option seems already implemented. The Xschem SImulation menu has the entry "`use spiceprefix attribute`". All devices that use this attribute (for example all sky130 mosfets) will be netlisted as X-subcircuits if the spiceprefix (usually set to 'X') is used in the symbol and the option to use it is enabled in the SImulation menu. I need to understand if there is a different requirement for this specific issue.

@Stefan Schippers That’s perfect

The second is probably more tricky, I think a lvs netlisting rule should be added, a new

lvs_format

attribute could define the format of the netlist line of the component for LVS. If the

Simulation -> LVS netlist

is enabled this attribute should be used (if existing) instead of the default

format

attribute that generates the spice netlist for the component.

@Stefan Schippers Totally agree with your ideas

Most of this is already implemented. Xschem has a '`xschem set format xxxx`' command that defines the '`format`' attribute used for netlisting. If I do :

xschem set format lvs_format

at the xschem prompt before generating a netlist a

lvs_format

will be used as the netlisting rule instead of the default '`format`' (or

verilog_format

is using verilog or

vhdl_format

if using VHDL). If such an attribute is not found in the symbol then the fallback default is used (

format

for spice). WIll investigate the issue of computing expressions and outputting the result in the lvs netlist...

Hi @Stefan Schippers, Please find the example CDL and simulation netlists attached.

Thank you will look and do some tests!

@Stefan Schippers That’s great

The netlist for LVS is set by enabling

Simulation->LVS netlist

For gf180mcu the set of symbol is yet to be done. I started doing that work, but stopped since got no feedback and no answer to any simple questions.

@Stefan Schippers Which questions do you have? What it me who didn't answer?

@Amro Tork I did an initial commit of symbols to another gf180 related github repo, then it was pulled into gf180mcu, I was told that symbols and all primitives could be renamed due to syntax conventions, so I asked what to do. If all symbols are going to be renamed I prefer to start directly with the new names. I asked what to do but got no answer, so i am in standby on this. The xschem symbols that are therein are an initial and untested commit. I can go through all of these and verify if simulation works and soon after also verify compatibility with LVS. Just give me a name of one person I can ask some details. I know many people are extremely busy or super involved with openlane integration...