• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. error in AMS simulation

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 18328
  • 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

error in AMS simulation

Clidre
Clidre over 7 years ago

Hello, I'm stuck with an error in my simulation that prevents me to see any results.

I have a system with one digital block (Verilog) and several analog blocks. I'm using the extracted views (with Calibre Pex) for my analog blocks. I use Cadence Virtuoso 6.1.7 and AMS Unified Netlister with irun. I would like to run a parametric simulation for a few values of the input digital codes of my Verilog block. For each code I run a dc simulation and then a transient.

Unfortunately, I get a red message: sim err  for each simulation. The netlist seems ok. I looked at irun.log and Job Log.

- irun.log shows an error in transient. I copy here what I get.

******************
DC Analysis `dcOp'
******************
Important parameter values:
reltol = 1e-03
abstol(V) = 1 uV
abstol(I) = 1 pA
temp = 27 C
tnom = 27 C
tempeffects = all
gmindc = 1 pS
rabsshort = 1 mOhm
Convergence achieved in 2 iterations.
Total time required for dc analysis `dcOp': CPU = 163.873 s (2m 43.9s),
elapsed = 51.1972 s.
Time accumulated: CPU = 17.907 ks (4h 58m 27s), elapsed = 8.22368 ks (2h 17m
4s).
Peak resident memory used = 24.5 Gbytes.


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

Notice from spectre during IC analysis, during transient analysis `tran'.
There are 2 IC nodes defined.

Finding DC approximate solution failed. Try again with try_fast_op set to no.
Trying `homotopy = gmin' for initial conditions.

Trying `homotopy = source' for initial conditions.

- Job Log gives me this error message:

INFO (ADEXL-1654): Simulator 'ams' doesn't provide simulation failure
\o information at the analysis level. So 'SkipFailedAnalyses' for option
\o 'evalOutputsOnSimFailure' wouldn't work for this simulator.
\o
\o *Error* Error ID = 5011
\o *Error* Error Msg = Simulator failed to complete the simulation.
\o
\o The simulator process returned a non-zero exit code 137,
\o indicating failure.
\o The simulator could have crashed or
\o intentionally returned to indicate an error.
\o Check the
\o simulator log file for more information. Common causes:
\o 1.
\o Simulator may have crashed during exit even after reporting
\o success in log file.
\o 2. Abrupt automatic simulator
\o termination (e.g., SIGKILL) because the simulator process
\o has
\o exceeded resource limits, which can be specified in
\o the distribution system or
\o by the kernel itself (e.g.,
\o the Linux OOMKiller).
\o 3. Manual termination of the
\o simulator process.
\o ./runSimulation can be manually run in
\o this directory to check the issue.

Both these messages are quite generic and I could not identify the cause of my error. I managed to run the same simulation with schematic views for my analog blocks, but I get these errors when I switch the view to the extracted ones. Could you please suggest me where to look to understand the problem? I need to check my extracted system

Thanks a lot

  • Cancel
Parents
  • Clidre
    Clidre over 7 years ago

    Thanks Andrew. Unfortunately I can't contact directly the customer support. However, I have other details that maybe can help to find a quick solution or at least can trigger an idea I can try. What I posted before was the result I got using the Calibre view. Instead, if I run the same simulation and I use directly the extracted netlist (selected in the config file with Set Cell View -> Specify SPICE Source File.. ), I get the following error, maybe less generic than the one I posted this morning:

    ncsim: *E,SYERROR (/tmp/TB_Top/adexl_allSCH_/results/data/Interactive.2/1/TB_analog:1/netlist/netlist.vams,42103|21): Vector net cannot be connected to a Spice/Spectre instance by port name.

    Error found by spectre during circuit read-in.

       ERROR (SPECTRE-357): AMS Analog Elaboration has exited with error.

           Simulation will terminate.

    I hope you can help me. I suspect it can be due to the different brackets [ ] and <>  in the vector notation for the AMS netlist and the extracted netlist, respectively, but I have no idea how to fix this...

    Thanks a lot!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Clidre
    Clidre over 7 years ago

    Thanks Andrew. Unfortunately I can't contact directly the customer support. However, I have other details that maybe can help to find a quick solution or at least can trigger an idea I can try. What I posted before was the result I got using the Calibre view. Instead, if I run the same simulation and I use directly the extracted netlist (selected in the config file with Set Cell View -> Specify SPICE Source File.. ), I get the following error, maybe less generic than the one I posted this morning:

    ncsim: *E,SYERROR (/tmp/TB_Top/adexl_allSCH_/results/data/Interactive.2/1/TB_analog:1/netlist/netlist.vams,42103|21): Vector net cannot be connected to a Spice/Spectre instance by port name.

    Error found by spectre during circuit read-in.

       ERROR (SPECTRE-357): AMS Analog Elaboration has exited with error.

           Simulation will terminate.

    I hope you can help me. I suspect it can be due to the different brackets [ ] and <>  in the vector notation for the AMS netlist and the extracted netlist, respectively, but I have no idea how to fix this...

    Thanks a lot!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information