Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 16165
  • 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 simulations (sometimes) fail when started through analog environment

IronRing

 This has been a widespread problem at my University for some time now.  Sometimes everything works fine with simulations.  Other times (apparently at random) Spectre simulations will not work when started through the Analog Environment.  When it starts to fail, it generally will continue to do so for a long period and restarting Cadence does not help.  If I try again the next day sometimes it will work, other times it won't.  When it fails to run, the spectre.out window displays a message similar to "Simulation failed.  See output.log file for more information."  However, this file is not created.

 When this happens we use a workaround to run simulations: Using the console, we browse to the simulation/Design_Name/spectre/schematic directory and run the Spectre command from the command line, using the command that has been set up in ADE.  This always works, and the results can be loaded into ADE and analyzed as usual.  The problem with this workaround, other than being a hassle, is that there is no way to run parametric simulations (as far as I can figure out).

Versions being used are:
ICFB/ADE 5.10.41.500.5.128
Spectre 6.2.1.390

Our servers are Sun machines.The problem seems to be independent of design kits, and will even appear for the simplest circuits (eg. a voltage source, resistor and ground from analogLib).

Any ideas would be greatly appreciated.

 

Parents

  • Hi,

    This is a well known problem. The problem is due to missing OS patches. You have to run checkSysConf on problematic machines and get those patches installed/upgraded.

    %>  checkSysConf  MMSIM7.1

     

    This will check for OS patches and report the missing ones. Pass the report to IT and get them installed. That should fix the problem.

     

    Regards,

    Ramkumar

Reply

  • Hi,

    This is a well known problem. The problem is due to missing OS patches. You have to run checkSysConf on problematic machines and get those patches installed/upgraded.

    %>  checkSysConf  MMSIM7.1

     

    This will check for OS patches and report the missing ones. Pass the report to IT and get them installed. That should fix the problem.

     

    Regards,

    Ramkumar

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.