Harald Pretl04/16/2023, 1:10 PM
seems to do the trick, I’ll try that…
Mitch Bailey04/16/2023, 3:38 PM
Harald Pretl04/16/2023, 5:34 PM
symbol to the extracted netlist port order using the
you can set the netlist rule as follows (assuming a symbol with 3 pins, A, B, Z):
format="@name @pinlist @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.
format="@name @@Z @@A @@B @symname"
Harald Pretl04/16/2023, 7:42 PM
Iain Waugh04/16/2023, 10:45 PM
Stefan Schippers04/17/2023, 8:46 AM
, specifically for lvs matching) netlisting rule, but to make this flow robust some convention must be adopted (what netlistfile to look into etc).
Harald Pretl04/18/2023, 10:54 AM
symbol file and the extracted netlist could parse the extracted netlist, and based on the pinorder in the extracted spice netlist adjust the
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.