• 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. Spectre failed to complete the simulation with Error ID...

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 124
  • Views 6255
  • 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

Spectre failed to complete the simulation with Error ID=5011

shbmsra12
shbmsra12 over 3 years ago

Hello,

I am running a post layout simulation by providing a SPICE post layout netlist (in a config view). I am running my simulation with  spectre version 15.1.0.257 (64-bit).

The job is running for a very short duration (2-5ns), while the total run time is 80ns. when I looked into job log I see following error:

 *Error* Error ID = 5011
 *Error* Error Msg = Simulator failed to complete the simulation.

 The simulator could have crashed or
 intentionally returned to indicate an error.
 Check the
 simulator log file for more information. Common causes:
1. Simulator may have crashed during exit even after reporting  success in log file.
2. Abrupt automatic simulator termination (e.g., SIGKILL) because the simulator process has exceeded resource limits, which can be specified in  the distribution system or by the kernel itself (e.g., the Linux OOMKiller).
3. Manual termination of the simulator process. ./runSimulation can be manually run in  this directory to check the issue.

PS: Its a relatively big design with few verilogA modules in it. I am only replacing a part of design (macro) with its respective spice post layout netlist. The simulation is running fine with Schematic design.

Kindly help me resolve this issue.

Best Regards,
Shubham

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    Not really enough information to go on (you didn't say which IC version you're running from, whether it's ADE L, XL, Explorer, Assembler). Also you're running a version of Spectre from over 6 years ago - is there a good reason why you have to use something that old?

    Did the simulator log give more details - that's more likely to give a clue as to the reason for the simulator exiting early.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • shbmsra12
    shbmsra12 over 3 years ago in reply to Andrew Beckett

    Hi Andrew,
    Thanks for quick reply.
    Here are the details you have asked:
    IC version: IC617
    I am running an ADE-XL environment. We have university owned tools, So we don't have any reason  for using the old version, But since you advised, I'll talk to the concern person regarding updating the tools. Could you please suggest how it can get updated or quick fix to the issue.
    The simulator only gave reasons I have mentioned above:

     *Error* Error ID = 5011
     *Error* Error Msg = Simulator failed to complete the simulation.

     The simulator could have crashed or
     intentionally returned to indicate an error.
     Check the simulator log file for more information. Common causes:
    1. Simulator may have crashed during exit even after reporting  success in log file.
    2. Abrupt automatic simulator termination (e.g., SIGKILL) because the simulator process has exceeded resource limits, which can be specified in  the distribution system or by the kernel itself (e.g., the Linux OOMKiller).
    3. Manual termination of the simulator process. ./runSimulation can be manually run in  this directory to check the issue.


    Also, I see few times virtuoso pops-up notification for low memory. 

    Please let me know if you need any more info in order to understand the issue better.

    Regards,
    Shubham

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to shbmsra12

    Shubham,

    You mentioned that it is running for 2ns - if so, you're presumably looking at a spectre log file somewhere (otherwise how would you know that it ran for 2ns?). That's what I want to see rather than a message in the CIW.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 3 years ago in reply to Andrew Beckett

    Dear Shubham,

    Just to add to Andrew's comments and questions if I may, you indicated a few items that relate to your error directly:

    shbmsra12 said:
    I am running a post layout simulation by providing a SPICE post layout netlist (in a config view).
    shbmsra12 said:
    The job is running for a very short duration (2-5ns), while the total run time is 80ns.

    shbmsra12 said:
    Also, I see few times virtuoso pops-up notification for low memory. 

    Your error indicates :

    shbmsra12 said:
    2. Abrupt automatic simulator termination (e.g., SIGKILL) because the simulator process has exceeded resource limits, which can be specified in  the distribution system or by the kernel itself (e.g., the Linux OOMKiller).

    It certainly seems a possibility that your simulation job requires more resources than you have provided for it to run successfully. The combination of using an extracted view and that it terminates prematurely, and that you observe "pop-up" dialog boxes indicating a low memory status suggest this to me. 

    1. Have you tried running on a distributed machine where you can increase the memory allocation and use multiple cores?

    2. Are you using spectre APS to run the simulation?

    3. Did you examine the job resources following the termination?

    4. Are you sure the format being written is psf and not a SPICE format? If so, you might check the On-line support article regarding this error at:

    support.cadence.com/.../ArticleAttachmentPortal

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • shbmsra12
    shbmsra12 over 3 years ago in reply to Andrew Beckett

    Hi Andrew,
    I don't see any error in the spectre log. Here is list of warnings I see there:
    Warning from spectre during hierarchy flattening.
    WARNING (SFE-3012): The shorted instance I71.I100.cc_82619 is removed.
    WARNING (SFE-3013): The dangling instance I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%CLKQ_MUX.r372 is removed.
    WARNING (SFE-3013): The dangling instance I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%CLKQB_MUX.r377 is removed.
    WARNING (SFE-3013): The dangling instance I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%CLKIB_MUX.r362 is removed.
    WARNING (SFE-3013): The dangling instance I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%CLKI_MUX.r355 is removed.
    WARNING (SFE-3015): The dangling node I71.net59 is removed.
    WARNING (SFE-3015): The dangling node I71.net60 is removed.
    WARNING (SFE-3015): The dangling node I71.net63 is removed.
    WARNING (SFE-3015): The dangling node I71.net64 is removed.

    WARNING (SPECTRE-17101): The value 'psf' specified for the 'checklimitdest' option will no longer be supported in future releases. Use 'spectre -h' to see other recommended values for the 'checklimitdest' option.

    Starting APS DC ...


    Warning from spectre during hierarchy flattening.
    WARNING (SPECTRE-17101): The value 'psf' specified for the 'checklimitdest' option will no longer be supported in future releases. Use 'spectre -h' to see other recommended values for the 'checklimitdest' option.
    Notice from spectre during hierarchy flattening.

    WARNING (SPECTRE-8286): Ignoring invalid item `I71.net59' in save statement.
    Node is dangling or part of a dangling chain.
    WARNING (SPECTRE-8286): Ignoring invalid item `I71.net60' in save statement.
    Node is dangling or part of a dangling chain.
    WARNING (SPECTRE-8286): Ignoring invalid item `I71.net63' in save statement.
    Node is dangling or part of a dangling chain.
    WARNING (SPECTRE-8286): Ignoring invalid item `I71.net64' in save statement.
    Node is dangling or part of a dangling chain.
    WARNING (SPECTRE-294): The number of signals saved (143048) is too high and may slow down the initialization process. Remove the unnecessary signals to speed up the initialization.
    WARNING (SPECTRE-294): The number of signals saved (143048) is too high and may slow down the initialization process. Remove the unnecessary signals to speed up the initialization.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I160:outMag_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I160:outPhase_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I163:outMag_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I163:outPhase_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I165:outMag_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    Further occurrences of this warning will be suppressed.
    WARNING (SPECTRE-16255): Initial condition of 13.3577 kV between nodes net067 and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    WARNING (SPECTRE-16255): Initial condition of 25.8144e-24 V between nodes I71.CK_SYN and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    WARNING (SPECTRE-16255): Initial condition of -25.6155e-27 V between nodes I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%GND.8539 and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    WARNING (SPECTRE-16255): Initial condition of -25.6155e-27 V between nodes I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%GND.8585 and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    WARNING (SPECTRE-16255): Initial condition of -22.5807e-27 V between nodes I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%GND.14596 and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    Further occurrences of this warning will be suppressed.

    Only place where error mentioned is:
    step is rejected by error on signal: I165:idt0 = 207.788 mV 0 V 0 V

    But the simulations kept on going on and stopped after few nano second as mentioned earlier. Also, It stopped while still performing transient analysis (no error or warning displayed when job stopped running) in GUI it simply shows job completed.

    Please let me know if you need any further information.

    Thanks and regards,
    Shubham

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • shbmsra12
    shbmsra12 over 3 years ago in reply to Andrew Beckett

    Hi Andrew,
    I don't see any error in the spectre log. Here is list of warnings I see there:
    Warning from spectre during hierarchy flattening.
    WARNING (SFE-3012): The shorted instance I71.I100.cc_82619 is removed.
    WARNING (SFE-3013): The dangling instance I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%CLKQ_MUX.r372 is removed.
    WARNING (SFE-3013): The dangling instance I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%CLKQB_MUX.r377 is removed.
    WARNING (SFE-3013): The dangling instance I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%CLKIB_MUX.r362 is removed.
    WARNING (SFE-3013): The dangling instance I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%CLKI_MUX.r355 is removed.
    WARNING (SFE-3015): The dangling node I71.net59 is removed.
    WARNING (SFE-3015): The dangling node I71.net60 is removed.
    WARNING (SFE-3015): The dangling node I71.net63 is removed.
    WARNING (SFE-3015): The dangling node I71.net64 is removed.

    WARNING (SPECTRE-17101): The value 'psf' specified for the 'checklimitdest' option will no longer be supported in future releases. Use 'spectre -h' to see other recommended values for the 'checklimitdest' option.

    Starting APS DC ...


    Warning from spectre during hierarchy flattening.
    WARNING (SPECTRE-17101): The value 'psf' specified for the 'checklimitdest' option will no longer be supported in future releases. Use 'spectre -h' to see other recommended values for the 'checklimitdest' option.
    Notice from spectre during hierarchy flattening.

    WARNING (SPECTRE-8286): Ignoring invalid item `I71.net59' in save statement.
    Node is dangling or part of a dangling chain.
    WARNING (SPECTRE-8286): Ignoring invalid item `I71.net60' in save statement.
    Node is dangling or part of a dangling chain.
    WARNING (SPECTRE-8286): Ignoring invalid item `I71.net63' in save statement.
    Node is dangling or part of a dangling chain.
    WARNING (SPECTRE-8286): Ignoring invalid item `I71.net64' in save statement.
    Node is dangling or part of a dangling chain.
    WARNING (SPECTRE-294): The number of signals saved (143048) is too high and may slow down the initialization process. Remove the unnecessary signals to speed up the initialization.
    WARNING (SPECTRE-294): The number of signals saved (143048) is too high and may slow down the initialization process. Remove the unnecessary signals to speed up the initialization.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I160:outMag_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I160:outPhase_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I163:outMag_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I163:outPhase_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    WARNING (SPECTRE-16686): Initial condition of 0 A on node I165:outMag_flow converted into initial guess (nodeset). Initial conditions will only be accepted for inductor currents.
    Further occurrences of this warning will be suppressed.
    WARNING (SPECTRE-16255): Initial condition of 13.3577 kV between nodes net067 and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    WARNING (SPECTRE-16255): Initial condition of 25.8144e-24 V between nodes I71.CK_SYN and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    WARNING (SPECTRE-16255): Initial condition of -25.6155e-27 V between nodes I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%GND.8539 and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    WARNING (SPECTRE-16255): Initial condition of -25.6155e-27 V between nodes I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%GND.8585 and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    WARNING (SPECTRE-16255): Initial condition of -22.5807e-27 V between nodes I71.I100.x_PM_MUX_V2_W_PREDRIVER_FINAL%GND.14596 and 0 converted into initial guess (nodeset) because there is no capacitive path to ground. Check the initial condition setting and rerun the simulation.
    Further occurrences of this warning will be suppressed.

    Only place where error mentioned is:
    step is rejected by error on signal: I165:idt0 = 207.788 mV 0 V 0 V

    But the simulations kept on going on and stopped after few nano second as mentioned earlier. Also, It stopped while still performing transient analysis (no error or warning displayed when job stopped running) in GUI it simply shows job completed.

    Please let me know if you need any further information.

    Thanks and regards,
    Shubham

    • 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