Harald Pretl
04/16/2023, 1:10 PMsim_pinnumber
seems to do the trick, Iāll try thatā¦Mitch Bailey
04/16/2023, 3:38 PMHarald Pretl
04/16/2023, 5:34 PMxschem
symbol to the extracted netlist port order using the sim_pinnumber
property.Stefan Schippers
04/16/2023, 6:43 PMformat="@name @pinlist @symname"
you can set the netlist rule as follows (assuming a symbol with 3 pins, A, B, Z):
format="@name @@Z @@A @@B @symname"
The first rule relies on the creation order of the pins (first drawn goes first) This order of course can be changed as explained in the tutorial, but explicitly naming the pin order (using the @@x syntax) is probably the simplest method to match a aymbol with an existing netlist.Harald Pretl
04/16/2023, 7:42 PMIain Waugh
04/16/2023, 10:45 PMStefan Schippers
04/17/2023, 8:46 AMformat
(or, better, lvs_format
, specifically for lvs matching) netlisting rule, but to make this flow robust some convention must be adopted (what netlistfile to look into etc).Harald Pretl
04/18/2023, 10:54 AMxschem
symbol file and the extracted netlist could parse the extracted netlist, and based on the pinorder in the extracted spice netlist adjust the sim_pinnumber
property of an already existing (handdrawn) symbol. While doing it can check for matching of the pins between these two entities (spice and sym) and report and error.
An autocreation of symbol from spice netlist I think is not that important, as usually one starts with a symbol plus something behind for first simulation, and later replace it by an extracted netlist.