Mustafa Ahmad
10/19/2021, 3:46 PMRana Muhammad Shahid Jamil
10/19/2021, 4:16 PMMustafa Ahmad
10/19/2021, 4:17 PMRana Muhammad Shahid Jamil
10/19/2021, 4:20 PMStefan Schippers
10/19/2021, 11:55 PMX1
, X2
or similar, so unless you explicitly change it it should work.Mitch Bailey
10/20/2021, 12:10 AMStefan Schippers
10/20/2021, 12:16 AM*
prefix to comment out the device (This is an extreme case and very bad practice!)
Enforcing 'X' on all symbols may not be ok for everyone, for example PCB designers often use U1, U2, U3 for pcb components. They don't simulate the design. They use xschem to export the netlist to a pcb editor, so they have all the components and ratlines representing the connections, and the usual U1, U2... naming.
Xschem has however the ability to enforce a 'X' if you define the symbol format string as format=@spiceprefix@name.....
See for example a MOS symbol in xschem_sky130.
The usage of spiceprefix attribute can be enabled or disabled in the Simulation menu.
The spiceprefix method is expecially useful if you need to generate 2 different netlists for simulation and for LVS. Simulation pdk often wraps MOS devices into subcircuits so you need the 'X' in front of all MOS instances, while for comparing a schematic netlist to layout you just need these devices with the usual 'M' prefix.Mitch Bailey
10/20/2021, 12:57 AM