Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 22160
  • 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 (ADE-3036): Errors encountered during simulation. The simulator run log has not been generated.

conrel

I have just installed IC616, INCISIVE151,MMSIM151, and other tools. but while running a simple inverter transient analysis, i am getting following errors. kindly let me know the possible reasons and the solution.

*INFO* (icLic-25) License Analog_Design_Environment_GXL ("95220") was used to run ADE L.

Loading msgHandler.cxt

Loading AMSOSS.cxt

Loading AMS.cxt

Delete psf data in /home/rajesh/simulation/inv/spectre/schematic/psf.

generate netlist...

Loading seCore.cxt

Begin Incremental Netlisting May 16 20:25:32 2017

WARNING (OSSHNL-145): Incremental netlisting is not possible since the netlist in this run directory

was generated using a previous IHNL version which is incompatible with the

current IHNL version. Therefore re-netlisting the entire design using the

current IHNL version.

End netlisting May 16 20:25:32 2017

Loading monte.cxt

Netlisting Statistics:

Number of components: 3

Elapsed time: 1.0s (3.00/s)

Errors: 0 Warnings: 0

...successful.

compose simulator input file...

...successful.

start simulator if needed...

...successful.

Loading paraplot.cxt

ERROR (ADE-3036): Errors encountered during simulation. The simulator run log has not been generated.

Possible cause could be an invalid command line option for the version of the simulator

you are running. Choose Setup->Environment and verify that the command line options

specified in the userCmdLineOption field are supported for the simulator.

Alternatively, run the simulator standalone using the runSimulation file in the netlist

directory to know the exact cause of the error.

  • Andrew Beckett

    Rajesh Yadav said:

    Alternatively, run the simulator standalone using the runSimulation file in the netlist

    directory to know the exact cause of the error.

    Did you try this suggestion? It may well be that something is wrong with the shared libraries or something like that which means that the simulator can't start...

    Andrew.

  • conrel
    Thanks Andrew, I have run the spectre standalone and this is showing the following errors

    [rajesh@iitgn netlist]$ csh
    [rajesh@iitgn netlist]$ source ~/cshrc_new_version
    [rajesh@iitgn netlist]$ spectre input.scs
    Fatal error in MPI_Init: Other MPI error, error stack:
    MPIR_Init_thread(420)..............:
    MPID_Init(180).....................: channel initialization failed
    MPIDI_CH3_Init(38).................:
    MPID_nem_init(244).................:
    MPID_nem_tcp_init(108).............:
    MPID_nem_tcp_get_business_card(354):
    MPID_nem_tcp_init(313).............: gethostbyname failed, iitgn (errno 1)
  • Andrew Beckett

    This article on the support site explains this problem. The issue is that the host name on the machine can't be resolved - you should check that /etc/hosts has the machine name properly defined (the article explains this a bit more).

    Andrew.

  • conrel
    Thank you Andrew, issue resolved it was just conflict of hostname . But I have one doubt that how to set virtuoso -64 default? In my case if i am invoking virtuoso by typing $ virtuoso & it tries to open virtuoso 32 bit and ends up with library error, but $ virtuoso -64 working fine.
    So is there any way to setup virtuoso 64 default?
  • Andrew Beckett

    Yes. If you had been using IC617, then there is no 32-bit virtuoso anymore, but in IC616 you can use:

    setenv CDS_AUTO_64BIT virtuoso

    or

    setenv CDS_AUTO_64BIT ALL

    (of course, use the appropriate means to set the env var for whatever shell you're using). The first means that just virtuoso will be forced to be 64 bit, whereas the second means that all tools will be 64 bit (including spectre and so on).

    Of course, set this before you start virtuoso.

    Regards,

    Andrew.

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.