Product Documentation
Spectre Circuit Simulator Reference
Product Version 23.1, September 2023

Circuit Information (info)

Description

The circuit information analysis outputs several types of information about the circuit and its components. You can use various filters to specify what information is output. You can create a listing of model, instance, temperature-dependent, input, output, and operating point parameters. You can also generate a summary of the minimum and maximum parameter values (by using extremes=yes or only). Finally,  you can request that Spectre provides a node-to-terminal map (by using what=terminals) or a terminal-to-node map (by using what=nodes).

The following are brief descriptions of the types of parameters you can request with the info statement:

Input parameters: Parameters that you specify in the netlist, such as the given length of a MOSFET or the saturation current of a bipolar transistor (use what=inst, models, input, or all)

Output parameters: Parameters that are computed by Spectre, such as temperature-dependent parameters and the effective length of a MOSFET after scaling (use what=output or all)

Operating-point parameters: Parameters that depend on the actual solution computed (use what=oppoint)

Initial condition file creation: write node voltages and source currents into a file which can be read by the transient analysis readic/readns statement.

Syntax

Name info parameter=value ...

Parameters

what

oppoint

The parameters that should be printed. Possible values are none, inst, models, input, output, nodes, all, terminals, oppoint, captab, parameters, primitives, subckts, assert, allparameters, netlist, options, dumpall, bridges, opens, customreplace, custominsert, customopen, faultparam, allcap, netcap, moscap, dhe and simstat.

where

logfile

Where the parameters should be printed. Asserts can only be written to rawfile. Possible values are nowhere, screen, file, logfile and rawfile.

file

%C:r.info.what

File name when where=file.

save

Signals to output. Possible values are all, lvl, allpub, lvlpub, selected, none and nooutput.

nestlvl

Levels of subcircuits to output.

extremes

yes

Print minimum and maximum values. Possible values are no, yes and only.

title

Analysis title.

descriptions

no

Print descriptions. Possible values are no and yes.

subckts

[...]

Customize for filtering out wanted subckts names from the netlist. Only support for output in logfile or file..

subckt_parameters

[...]

Customize for filtering out wanted subckt parameter names from the netlist. Only support for output in logfile or file..

Operating point parameters

oppoint

all

Operating point type when 'what=oppoint', all - operating point for devices, stacked devices, node voltages, and source currents. node - operating point for node voltages, and source currents. dev - operating point for devices. subckt - operating point for stacked devices. alldev - operating point for regular and stacked devices. stacked device parameter reporting requires Spectre option subcktoppoint=yes, and save statement for stacked device parameters of interest. Possible values are all, node, dev, subckt and alldev.

Initial condition file creation

optype

ic

Print Spectre format operating point file which can be read with readic/readns in transient statement. Time for writing operating point file needs to be defined in infotimes statement. Possible values are ic and nodeset.

Fault generation parameters

faultblock

Name of the fault block when fault list generation requested.

faultdev

[...]

Fault devices defined by primitive names, subckt names, or model names.

faultcustom

[...]

Custom fault subcircuit defined by subckt model name from the netlist.

faultres

[...]

Resistance value for bridges or opens (default 100 Ohm for bridges, 1G Ohm for opens).

faultcap

0

Capacitance value for open faults.

faultterminals

[...]

List of device terminals to be considered for fault generation (default is all terminals of faultdev).

faultstuckat

[...]

Supply node name(s) to generate stuck-at fault list when 'what=bridges'.

faultextract

no

Enables the generation of a layout-based fault list when DSPF files are included in the netlist. Set it to: 'no' to disable the generation of a layout-based fault list, only the schematic-based faults are generated, this is the default value; 'spf' to generate a list of faults that are compatible with a layout-based netlist; 'sch' to generate a list of faults that are compatible with a schematic-based netlist. Possible values are no, spf and sch.

faultcmin

1e-20

Defines the minimum capacitance value an extracted parasitic capacitor must have to be identified as a bridge defect during the generation of faults.

faultrmin

0.001

Defines the minimum resistance value an extracted parasitic resistor must have to be identified as an open defect during the generation of faults.

subckt

[...]

Faults are generated for all instances of the specified subcircuits.

inst

[...]

Faults are generated for the specified subcircuit instances.

xsubckt

[...]

All instances of the specified subcircuits are excluded from fault generation.

xinst

[...]

All specified subcircuit instances are excluded from fault generation.

faultlevel

Defines the hierarchical level of the design to be considered during the fault list generation. By default, Spectre generates faults in subcircuits at all levels of the design.

faultlayer

[...]

Layer numbers on which layout-based faults are to be identified. Set this option to 0 to identify faults on all layers including the connectivity between layers. Set it to a set of layer numbers, [x y ...], to identify faults on those layers, or set it to a range, [(x,y)], to identify faults for all layers in the range, excluding the connectivity between layers in both cases.

faultmaxcount

100,000

Upper bound for number of faults to be generated before collapsing.

faultrule

none

Comply with IEEE 2427 requirements for fault list generation. Possible values are none and 2427.

faultuniverse

Name of the file to save the defect universe details after fault list generation.

faultcollapse

yes

If yes, only one fault will be included into the fault list for each set of equivalent faults having the same topology. Possible values are no and yes.

weight_expr

Expression to define fault weighting function.

weight_factor

1.

Value to define weighting factor for given block in the fault list.

faultduplicate

yes

If no, the equivalent faults will be excluded from the fault list. In addition, the duplicated faults will be excluded when several info analyses are specified for fault generation. Possible values are no and yes.

faultactivethresh

0

The minimum activity ratio of the circuit element to identify the related faults as potentially undetectable. The value is calculated as the ratio of time points when the element was active to the total number of time points.

faultparam

[...]

Parameter names to generate fault list when 'what=faultparam'.

faultvalues

[...]

Parameter values for fault generation when 'what=faultparam'.

faultpercentage

[...]

Percentage in parameter value deviation for fault generation when 'what=faultparam'.

faultfile

File name containing parameter values when 'what=faultparam'.

faultstart

[...]

Parameter initial values for fault generation when 'what=faultparam'.

faultstep

[...]

Step size to sweep parameter values for fault generation when 'what=faultparam'.

faultstop

[...]

Parameter's final value for fault generation when 'what=faultparam'.

Design hierarchy extraction parameters for Midas Safety Platform

dheminarea

0 μm2

Lower bound of area value for device to be considered during design hierarchy extraction.

dhesubckt

[...]

Design hierarchy is generated for all instances of the specified subcircuits.

dheinst

[...]

Design hierarchy is generated for the specified subcircuit instances.

dhexsubckt

[...]

All instances of the specified subcircuits are excluded from the design hierarchy.

dhexinst

[...]

The specified subcircuit instances are excluded from the design hierarchy.

dheparams

Name of the file that provides the rules to calculate area for subcircuits when 'what=dhe'.

Captab parameters

detail

node

How detailed should the capacitance table be. Possible values are node, nodetoground and nodetonode.

sort

name

How to sort the capacitance table. Possible values are name and value.

filter

If set to "rc" nodes within RC net will be dropped. Possible values are none and rc.

threshold

0 F

Threshold value for printing capacitances (ignore capacitances smaller than this value).

skip_ground

Whether capt skip ground or not. Possible values are yes and no.

node

[...]

Nodes for which captab analyses will performed.

intrinsic_cap_merge

no

Merge the internal captab node to external node. Possible values are no and yes.

Example initial condition file creation

tran1 tran stop=10n infotimes=[3n 4n] infonames=[myinfo1 myinfo2]

myinfo1 info what=oppoint optype=ic where=file file='3n.ic'

myinfo2 info what=oppoint optype=nodeset where=file file='4n.ic'


Return to top
 ⠀
X