1SPI(5) File Formats SPI(5)
2
3
4
6 spi - Alliance parser and driver for Spice netlist.
7
8
9
11 The description of a netlist foo must be contained in a .SUBCKT of a
12 file named foo.spi. This description can include others .SUBCKT that
13 must be in the same file or files included with the command .INCLUDE in
14 the source file.
15
16 Recognized elements are :
17
18 Resistances
19
20 Capacitances
21
22 Instances
23
24 MOS transistors.
25
26 Others elements are not considered.
27
28 Nodes can be either numbered or nameed. It's possible to assign a name
29 to a node which is designated by a number with the directive
30
31 * NET number = name
32
33 in the .SUBCKT. The word NET can be replaced by positioning the envi‐
34 ronment variable MBK_SPI_NETNAME. Names are used to named the signals
35 and the connectors in the LOFIG.
36
37 On the .SUBCKT interface, nodes of the same name followed by a period
38 and a number are considered to be on the net, even if no connected in
39 the circuit. For example :
40
41 .SUBCKT nand2 in out out.1 out.2 vss vdd out.3
42
43 The nodes out, out.1, out.2 and out.3 are considered to be the same
44 signal of the Alliance LOFIG. This feature can be turned off if the
45 environment variable MBK_SPI_MERGE is set, and the period can be
46 replaced by another character with the environment variable
47 MBK_SPI_SEPAR.
48
49 No particular information is needed to build a LOFIG from a .SUBCKT,
50 the parser rebuild all signals, even they contains many resistances and
51 capacitances. If names are not provided, the parser will create then in
52 order to provide a valid lofig.
53
54
56 The driver creates a Spice netlist of the LOFIG passed as a parameter.
57 The file contain a single .SUBCKT representing the figure and commands
58 .INCLUDE with name of instances contained in the LOFIG. Nodes are num‐
59 ber named with the directive * NET, or strings, depending on
60 MBK_SPI_NAMEDNODES. A comment at the beginning of the file represents
61 the interface of the LOFIG. This comment is not used by the parser.
62
63 Environment variable considered are
64
65 MBK_SPI_MODEL
66
67 MBK_SPI_NETNAME
68
69 MBK_SPI_NAMEDNODES
70
71
73 The parser load all .SUBCKT in memory, even those in files included
74 with the command .INCLUDE until the required LOFIG is loaded. For each
75 .SUBCKT loaded, the parser build the equipotentials with both nodes of
76 resistances on the same net and both nodes of capacitances on differ‐
77 ents net unless more information is given. The RCN library is used to
78 handle resistances and capacitances.
79
80 As the LOWIRE can contain a resistance and a capacitance, the parser
81 groups a resistance and two capacitances in a single LOWIRE if the fol‐
82 lowing conditions are met :
83
84 The resistance is named 'name' and the two capacitances are
85 named 'name1' and 'name2'
86
87 The two capacitances must have the same value
88
89 The two capacitances must be between the net of the resistance
90 and VSS.
91
92 The driver supports this feature.
93
94 Environment variable considered are
95
96 MBK_SPI_MODEL
97
98 MBK_SPI_NETNAME
99
100 MBK_SPI_SEPAR
101
102 MBK_SPI_MERGE
103
104 MBK_SPI_FILE
105
106 MBK_SPI_VERBOSE
107
108 MBK_SPI_ONE_NODE_NORC
109
110 MBK_SPI_NO_AFF_UNK
111
112
114 MBK_SPI_MODEL
115
116 File name where transistors models are described. Syntax for file is :
117 MODELNAME N|P [FAST] [HVIO]
118 Blank lines are allowed, and line comment begin with a '#'.
119
120 MBK_SPI_NETNAME
121
122 Comment used to name the nodes. Default is NET.
123
124 MBK_SPI_SEPAR
125
126 Character used to separate a name from a node number on the interface
127 of the .SUBCKT. The parser considers nodes of the same name to be on
128 the same equipotential. Default is '.'.
129
130 MBK_SPI_NOMERGE
131
132 If this variable is set, the parser does not merge interface nodes of
133 the same name, but different number, on the same equipotential.
134
135 MBK_SPI_FILE
136
137 If this variable is set, the name of the files opened are displayed on
138 the error output.
139
140 MBK_SPI_VERBOSE
141
142 If this variable is set, display debug various information on the error
143 output.
144
145 MBK_SPI_ONE_NODE_NORC
146
147 If this variable is set, an RCN view is not created for a net contain‐
148 ing only one node.
149
150 MBK_SPI_NO_AFF_UNK
151
152 Default behaviour of Spice parser is to display an error message when
153 an unknown element is read in the input file. Setting this variable
154 prevent this display. Useful when file contain command for Spice simu‐
155 lator.
156
157 MBK_SPI_NAMEDNODES
158
159 When this environment variable is set, spice netlist's nodes are named
160 using one of the following convention, if signal name is set or no, or
161 if signal has an RCN view :
162
163 "SIGNAL NAME" $MBK_SEPAR "RCN NODE"
164
165 "SIGNAL NAME"
166
167 SIG "SIGNAL INDEX" $MBK_SEPAR "RCN NODE"
168
169 SIG "SIGNAL INDEX"
170
171 $MBK_SEPAR is a single character defined by a environment variable with
172 the same name.
173
174
176 This is an example of a file generated by the Spice driver.
177
178
179 * Spice description of gxor
180 * Spice driver version 700
181 * Date ( dd/mm/yyyy hh:mm:ss ): 29/03/1999 at 17:43:53
182
183 * INTERF a b s vdd vdd vdd vdd vss vss vss vss
184
185 .INCLUDE mx2_y.spi
186 .INCLUDE ndrvp_y.spi
187
188 .subckt gxor 24 42 49 52 53 61 54 63 64 71 72
189 * NET 1 = implicit
190 * NET 4 = auxsc1
191 * NET 13 = auxsc3
192 * NET 26 = a
193 * NET 40 = b
194 * NET 49 = s
195 * NET 52 = vdd
196 * NET 65 = vss
197 xauxsc1 64 65 53 55 33 35 2 8 ndrvp_y
198 xs 66 70 56 60 48 50 11 21 5 9 34 36 38 45 mx2_y
199 xauxsc3 70 71 60 61 41 46 18 22 ndrvp_y
200 R2_1 4 7 6
201 C2_11 4 63 6.9e-15
202 C2_12 7 63 6.9e-15
203 R2_2 3 2 0.15
204 C2_21 3 63 7.2e-16
205
206 [----- CUT -----]
207
208 C4_51 69 63 6.525e-15
209 C4_52 72 63 6.525e-15
210 R4_6 68 69 0.001
211 R4_7 68 67 0.001
212 .ends gxor
213
214
216 Alliance(1) MBK(1) Al(1) RCN(1) MBK_SEPAR(1)
217
218
220 Gregoire AVOT. Gregoire.AVOT@lip6.fr
221
222
223
224
225ASIM/LIP6 30 March 1999 SPI(5)