10.06.2016 Views

eldo_user

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Eldo Netlist Setup<br />

Subcircuits<br />

Specifying Noise in Subcircuits<br />

By default, devices present noise contributions when a noise analysis is specified. The<br />

NONOISE parameter on a device model or instance can be specified so that no noise model will<br />

be used for the device when performing a noise analysis. The specification of noise on a device<br />

or subcircuit instance overrides any specification in the model definition (.MODEL statement).<br />

Noise can also be controlled at the subcircuit level in the following ways to specify that devices<br />

present no noise contribution to the noise analysis:<br />

• On the subcircuit definition (.SUBCKT statement) specify the (NONOISE) parameter.<br />

This parameter must be specified before the PARAM: or PAR=VAL specifications, if<br />

any.<br />

• On the subcircuit instance (X statement) specify the (NONOISE) or NOISE=0<br />

parameter. This parameter must be specified after the PARAM: or PAR=VAL<br />

specifications, if any.<br />

Local specification takes precedence. The specification of noise in the subcircuit overrides any<br />

specification in the parent subcircuit instance. In the following example:<br />

.subckt top1 in out (nonoise)<br />

Xinv1 in out inv wn=17u noise=1<br />

.ends<br />

XTOP in out top1 (nonoise)<br />

A noise analysis will run even though (NONOISE) is specified in the XTOP instance; this is<br />

because NOISE=1 is specified inside the subcircuit definition of top1.<br />

(INLINE) Keyword Example<br />

The following example illustrates how the (INLINE) keyword can be specified on the<br />

.SUBCKT instance, so that Eldo will not print the full hierarchical name of the device which has<br />

the same name as the .SUBCKT.<br />

X1 ... MFOO<br />

X2 ... MFOO<br />

.SUBCKT MFOO ... (INLINE)<br />

M1 ...<br />

MFOO<br />

M2<br />

...<br />

.ENDS<br />

In the OP table, it will not be X1.MFOO and X2.MFOO which appear, but simply X1 and X2.<br />

The other names, X1.M1, X2.M1, X1.M2 and X2.M2, will be printed out unaffected.<br />

DSCGLOB Option Example<br />

Nodes which appear in subcircuit definitions have priority over the nodes defined with<br />

.GLOBAL statements. Option DSCGLOB can be used to change this behavior. For example:<br />

Eldo® User's Manual, 15.3 129

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!