Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 22141
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Running Spectre in Command Line

IITBVLSI

I'm trying to learn how to run a simulation using command line. I'm using the following command:

spectre  /home/users/prasu/simulation/Counter/spectre/schematic/netlist/input.scs

The simulation completes successfully but I see no PSF directory generated.

At the end of this post, I have pasted input.log that the above command generates. Could someone please tell me what I am missing here? Thank you for your help.

PS: The intention of working in command line is to later use APS with distributed mode using the +aps +dp options. I haven't found a way to work this using Viruoso's GUI environment. Pointers to doing this using GUI would be really helpful too.

Cadence (R) Virtuoso (R) Spectre (R) Circuit Simulator
Version 12.1.0.272 32bit -- 25 Sep 2012
Copyright (C) 1989-2012 Cadence Design Systems, Inc. All rights reserved worldwide. Cadence, Virtuoso and Spectre are registered trademarks of Cadence Design Systems, Inc. All others are the property of their respective holders.

Protected by U.S. Patents:
5,610,847; 5,790,436; 5,812,431; 5,859,785; 5,949,992; 5,987,238;
6,088,523; 6,101,323; 6,151,698; 6,181,754; 6,260,176; 6,278,964;
6,349,272; 6,374,390; 6,493,849; 6,504,885; 6,618,837; 6,636,839;
6,778,025; 6,832,358; 6,851,097; 6,928,626; 7,024,652; 7,035,782;
7,085,700; 7,143,021; 7,493,240; 7,571,401.

Includes RSA BSAFE(R) Cryptographic or Security Protocol Software from RSA Security, Inc.

User: prasu Host: xxx.xxx.xxx.xxx HostID: xxxxxx PID: xxxx
Memory available: 780.1241 MB physical: 8.2824 GB
CPU Type: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
Processor PhysicalID CoreID Frequency
0 0 0 1600.0
1 0 1 1600.0
2 0 2 1600.0
3 0 3 1600.0


Simulating `/home/users/prasu/simulation/Counter/spectre/schematic/netlist/input.scs' on xxx.xxx.xxx.xxx at 4:31:26 PM, Sat Feb 28, 2015 (process id: 9825).
Current working directory: /home/users/prasu/DP.
Command line:
/cad/cadence/MMSIM121/tools.lnx86/spectre/bin/32bit/spectre \
/home/users/prasu/simulation/Counter/spectre/schematic/netlist/input.scs

Loading /cad/cadence/MMSIM121/tools.lnx86/cmi/lib/5.0/libinfineon_sh.so ...
Loading /cad/cadence/MMSIM121/tools.lnx86/cmi/lib/5.0/libphilips_sh.so ...
Loading /cad/cadence/MMSIM121/tools.lnx86/cmi/lib/5.0/libsparam_sh.so ...
Loading /cad/cadence/MMSIM121/tools.lnx86/cmi/lib/5.0/libstmodels_sh.so ...
Reading file: /home/users/prasu/simulation/Counter/spectre/schematic/netlist/input.scs
Reading file: /home/projects1/TSMC/PDK/TSMC65GP/models/spectre/CMN65GPLUS_1d8_lk_v1d2.scs
Reading file: /home/projects1/TSMC/PDK/TSMC65GP/models/spectre/mosCap_ahdl.va
Reading link: /cad/cadence/MMSIM121/tools.lnx86/spectre/etc/ahdl/discipline.h
Reading file: /cad/cadence/MMSIM121/tools.lnx86/spectre/etc/ahdl/disciplines.vams
Reading link: /cad/cadence/MMSIM121/tools.lnx86/spectre/etc/ahdl/constants.h
Reading file: /cad/cadence/MMSIM121/tools.lnx86/spectre/etc/ahdl/constants.vams

Time for NDB Parsing: CPU = 570.912 ms, elapsed = 1.17562 s.
Time accumulated: CPU = 570.912 ms, elapsed = 1.17562 s.
Peak resident memory used = 31.8 Mbytes.


Time for Elaboration: CPU = 50.993 ms, elapsed = 60.2849 ms.
Time accumulated: CPU = 621.905 ms, elapsed = 1.23601 s.
Peak resident memory used = 35.3 Mbytes.


Time for EDB Visiting: CPU = 4.999 ms, elapsed = 4.8089 ms.
Time accumulated: CPU = 626.904 ms, elapsed = 1.241 s.
Peak resident memory used = 37.1 Mbytes.


Notice from spectre during topology check.
Only one connection to node `net048'.


Circuit inventory:
nodes 136
bsim4 317
capacitor 106
vcvs 3
vsource 6


Time for parsing: CPU = 8.999 ms, elapsed = 11.5161 ms.
Time accumulated: CPU = 635.903 ms, elapsed = 1.25261 s.
Peak resident memory used = 38.8 Mbytes.


************************************************
Transient Analysis `tran': time = (0 s -> 80 ns)
************************************************

Notice from spectre during IC analysis, during transient analysis `tran'.
There are 10 IC nodes defined.
Notice from spectre during IC analysis, during transient analysis `tran'.
Initial condition computed for node QOUT9 is in error by 434.662 uV.
Initial condition computed for node QOUT8 is in error by 434.662 uV.
Initial condition computed for node QOUT7 is in error by 434.662 uV.
Initial condition computed for node QOUT6 is in error by 434.662 uV.
Initial condition computed for node QOUT5 is in error by 434.662 uV.
Further occurrences of this notice will be suppressed.

Important parameter values:
start = 0 s
outputstart = 0 s
stop = 80 ns
step = 80 ps
maxstep = 800 ps
ic = all
useprevic = no
skipdc = no
reltol = 100e-06
abstol(V) = 1 uV
abstol(I) = 1 pA
temp = 27 C
tnom = 27 C
tempeffects = all
errpreset = conservative
method = gear2only
lteratio = 10
relref = alllocal
cmin = 0 F
gmin = 1 pS


Warning from spectre at time = 452.779 ps during transient analysis `tran'.
WARNING (SPECTRE-16780): LTE tolerance was temporarily relaxed to step over a discontinuity in the signal: I0.M35:int_s.
Warning from spectre at time = 652.776 ps during transient analysis `tran'.
WARNING (SPECTRE-16780): LTE tolerance was temporarily relaxed to step over a discontinuity in the signal: I0.M35:int_s.
Warning from spectre at time = 1.05277 ns during transient analysis `tran'.
WARNING (SPECTRE-16780): LTE tolerance was temporarily relaxed to step over a discontinuity in the signal: I0.M35:int_s.

tran: time = 1.406 ns (1.76 %), step = 317.5 fs (397 u%)

Warning from spectre at time = 1.85278 ns during transient analysis `tran'.
WARNING (SPECTRE-16780): LTE tolerance was temporarily relaxed to step over a discontinuity in the signal: I0.M35:int_s.

tran: time = 2 ns (2.5 %), step = 3.618 ps (4.52 m%)

Warning from spectre at time = 3.25278 ns during transient analysis `tran'.
WARNING (SPECTRE-16780): LTE tolerance was temporarily relaxed to step over a discontinuity in the signal: I0.M35:int_s.
Further occurrences of this warning will be suppressed.

tran: time = 3.54 ns (4.43 %), step = 556.6 fs (696 u%)
tran: time = 5.066 ns (6.33 %), step = 438.6 fs (548 u%)
tran: time = 6 ns (7.5 %), step = 780.7 fs (976 u%)
tran: time = 7.407 ns (9.26 %), step = 254.5 fs (318 u%)
tran: time = 8.81 ns (11 %), step = 546.6 fs (683 u%)
tran: time = 10 ns (12.5 %), step = 654.2 fs (818 u%)
tran: time = 11.36 ns (14.2 %), step = 154.4 fs (193 u%)
tran: time = 12.76 ns (16 %), step = 223.5 fs (279 u%)
tran: time = 14 ns (17.5 %), step = 392.6 fs (491 u%)
tran: time = 15.4 ns (19.3 %), step = 1.049 ps (1.31 m%)
tran: time = 16.77 ns (21 %), step = 343.6 fs (429 u%)
tran: time = 18 ns (22.5 %), step = 785.1 fs (981 u%)
tran: time = 19.39 ns (24.2 %), step = 956.4 fs (1.2 m%)
tran: time = 20.75 ns (25.9 %), step = 146.2 fs (183 u%)
tran: time = 22 ns (27.5 %), step = 46.25 fs (57.8 u%)
tran: time = 23.38 ns (29.2 %), step = 690.4 fs (863 u%)
tran: time = 24.76 ns (31 %), step = 140.7 fs (176 u%)
tran: time = 26 ns (32.5 %), step = 39.63 fs (49.5 u%)
tran: time = 27.37 ns (34.2 %), step = 202.9 fs (254 u%)
tran: time = 28.76 ns (36 %), step = 338.2 fs (423 u%)
tran: time = 30 ns (37.5 %), step = 676.1 fs (845 u%)
tran: time = 31.37 ns (39.2 %), step = 822.2 fs (1.03 m%)
tran: time = 32.77 ns (41 %), step = 462.9 fs (579 u%)
tran: time = 34 ns (42.5 %), step = 392.7 fs (491 u%)
tran: time = 35.41 ns (44.3 %), step = 245.1 fs (306 u%)
tran: time = 36.81 ns (46 %), step = 56.43 fs (70.5 u%)
tran: time = 38 ns (47.5 %), step = 687.3 fs (859 u%)
tran: time = 39.4 ns (49.3 %), step = 544 fs (680 u%)
tran: time = 40.79 ns (51 %), step = 574.4 fs (718 u%)
tran: time = 42 ns (52.5 %), step = 534.8 fs (668 u%)
tran: time = 43.36 ns (54.2 %), step = 319.9 fs (400 u%)
tran: time = 44.76 ns (56 %), step = 183.3 fs (229 u%)
tran: time = 46 ns (57.5 %), step = 547.9 fs (685 u%)
tran: time = 47.4 ns (59.3 %), step = 47.47 fs (59.3 u%)
tran: time = 48.79 ns (61 %), step = 541.6 fs (677 u%)
tran: time = 50 ns (62.5 %), step = 393.6 fs (492 u%)
tran: time = 51.38 ns (64.2 %), step = 753.5 fs (942 u%)
tran: time = 52.76 ns (66 %), step = 159.8 fs (200 u%)
tran: time = 54 ns (67.5 %), step = 742.3 fs (928 u%)
tran: time = 55.37 ns (69.2 %), step = 468.8 fs (586 u%)
tran: time = 56.76 ns (70.9 %), step = 284.4 fs (355 u%)
tran: time = 58 ns (72.5 %), step = 699.8 fs (875 u%)
tran: time = 59.39 ns (74.2 %), step = 667.1 fs (834 u%)
tran: time = 60.77 ns (76 %), step = 420 fs (525 u%)
tran: time = 62 ns (77.5 %), step = 670.9 fs (839 u%)
tran: time = 63.41 ns (79.3 %), step = 469.6 fs (587 u%)
tran: time = 64.82 ns (81 %), step = 389.3 fs (487 u%)
tran: time = 66 ns (82.5 %), step = 403.9 fs (505 u%)
tran: time = 67.4 ns (84.3 %), step = 54.46 fs (68.1 u%)
tran: time = 68.79 ns (86 %), step = 962.4 fs (1.2 m%)
tran: time = 70 ns (87.5 %), step = 621.1 fs (776 u%)
tran: time = 71.4 ns (89.3 %), step = 595.5 fs (744 u%)
tran: time = 72.81 ns (91 %), step = 191.3 fs (239 u%)
tran: time = 74 ns (92.5 %), step = 690.6 fs (863 u%)
tran: time = 75.4 ns (94.3 %), step = 1.102 ps (1.38 m%)
tran: time = 76.81 ns (96 %), step = 610.9 fs (764 u%)
tran: time = 78 ns (97.5 %), step = 795.7 fs (995 u%)
tran: time = 79.41 ns (99.3 %), step = 453.3 fs (567 u%)
Number of accepted tran steps = 173174
Initial condition solution time: CPU = 20.997 ms, elapsed = 21.246 ms.
Intrinsic tran analysis time: CPU = 571.959 s, elapsed = 572.872 s.
Total time required for tran analysis `tran': CPU = 571.995 s (9m 32.0s), elapsed = 573.063 s (9m 33.1s).
Time accumulated: CPU = 572.687 s (9m 32.7s), elapsed = 575.103 s (9m 35.1s).
Peak resident memory used = 43.1 Mbytes.


Notice from spectre.
5 notices suppressed.
3 warnings suppressed.

finalTimeOP: writing operating point information to rawfile.
modelParameter: writing model parameter values to rawfile.
element: writing instance parameter values to rawfile.
outputParameter: writing output parameter values to rawfile.
designParamVals: writing netlist parameters to rawfile.
primitives: writing primitives to rawfile.
subckts: writing subcircuits to rawfile.

Aggregate audit (4:41:01 PM, Sat Feb 28, 2015):
Time used: CPU = 573 s (9m 32.8s), elapsed = 575 s (9m 35.4s), util. = 99.6%.
Time spent in licensing: elapsed = 111 ms.
Peak memory used = 43.1 Mbytes.
Simulation started at: 4:31:26 PM, Sat Feb 28, 2015, ended at: 4:41:01 PM, Sat Feb 28, 2015, with elapsed time (wall clock): 575 s (9m 35.4s).
spectre completes with 0 errors, 8 warnings, and 14 notices.

  • By default, spectre will save the results in a directory called '%C:r.raw' which is the input file, with the suffix removed, and ".raw" added. So if the input file is input.scs, the output directory will be input.raw . Commonly ADE runs spectre with the argument -raw ../psf to put the results in a directory called psf one up from the netlist directory.

    For the +aps and +dp option, you can get some info from doing "spectre +aps -h", but more in the Spectre Reference or Spectre User Guide.
    Or you may wish to contact customer support for some guidance on how to set up the distributed mode.

    Regards,

    Andrew.

  • Dear Andrew

    Thanks a lot for the instant reply. I found the input.raw file within netlist folder after running the spectre using command line and plotted the waveforms by opening it using "viva". Now, I would like to know

    1). Is the input.raw file is same as psf  i.e. can we extract all information from input.raw which psf has?

    2). Does Input.scs file (required for simulation using command line) generate only after running the simulation in ADE (GUI)? or is there any other mean?

    Thanks & Regards

    1. Yes, it's the same - just a different directory name. When running from ADE, there may be also an additional "variables" database that gets written which are the ADE variables, but spectre writes those out as well. So should be equivalent
    2. You can generate the netlist with OCEAN using the createNetlist() function.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.