Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 16770
  • 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

cannot run simvision

bdatta

 I have verilog-XL simulator from the IUS5.8 release and Allegro from the SPB16.01 release.  I can run Allegro but when I try to run verilog-XL it fails when it tries to start simvision and gives the following strange error message:

Cadence/tools/verilog/tools/bin/64bit/simvision: line 62 Cadence/tools/verilog/tools/bin/64bit/simvision.exe: cannot execute binary file

Cadence/tools/verilog/tools/bin/64bit/simvision: line 62 Cadence/tools/verilog/tools/bin/64bit/simvision.exe: success

simvision proccess terminated before connection could be established

 

Allegro is installed in 'Cadence' directory and the IUS5.8(verilog-XL) is installed in the Cadence/tools/verilog directory
Parents

  • Hi.

    I'm not familiar with Allegro, but I wonder if it has some binaries that have the same name as Verilog-XL does?
    Whenever I have to debug application problems, the first thing I do is start a new xterm and clean the PATH and LD_LIBRARY_PATH variables to remove everything except the very basic Unix directories like /usr/bin and /bin.
    After doing this, set the absolute minimum set of variables to configure Verilog-XL, in this case:
    > setenv PATH Cadence/tools/verilog/tools/bin:$PATH
    > setenv LD_LIBRARY_PATH Cadence/tools/verilog/tools/lib:$LD_LIBRARY_PATH

    Now try running a few components of the simulator to see if it's working:
    > ncsim -version   (check the tool is on the PATH)
    > cdnshelp   (opens the help GUI)
    > checkSysConf IUS5.8      (tests that your OS is compatible with the simulator)
    > simvision

    If simvision still fails to start after cleaning your environment as above,check the results of the checkSysConf command to be sure there are no failures in the compatibility with your OS. If you're still stuck, please email support@cadence.com and one of the support staff will ensure your problem gets resolved.

    By the way, you said Allegro is installed in the "Cadence" directory - do you mean that IUS is installed inside the Allegro installation?
    That would be a bad thing to do - each product expects to have a clean and separate installation area.
    Best would be something like:

    Cadence/Allegro/16.01/
    Cadence/Verilog/5.8/

    Good luck :-)

    Steve.

Reply

  • Hi.

    I'm not familiar with Allegro, but I wonder if it has some binaries that have the same name as Verilog-XL does?
    Whenever I have to debug application problems, the first thing I do is start a new xterm and clean the PATH and LD_LIBRARY_PATH variables to remove everything except the very basic Unix directories like /usr/bin and /bin.
    After doing this, set the absolute minimum set of variables to configure Verilog-XL, in this case:
    > setenv PATH Cadence/tools/verilog/tools/bin:$PATH
    > setenv LD_LIBRARY_PATH Cadence/tools/verilog/tools/lib:$LD_LIBRARY_PATH

    Now try running a few components of the simulator to see if it's working:
    > ncsim -version   (check the tool is on the PATH)
    > cdnshelp   (opens the help GUI)
    > checkSysConf IUS5.8      (tests that your OS is compatible with the simulator)
    > simvision

    If simvision still fails to start after cleaning your environment as above,check the results of the checkSysConf command to be sure there are no failures in the compatibility with your OS. If you're still stuck, please email support@cadence.com and one of the support staff will ensure your problem gets resolved.

    By the way, you said Allegro is installed in the "Cadence" directory - do you mean that IUS is installed inside the Allegro installation?
    That would be a bad thing to do - each product expects to have a clean and separate installation area.
    Best would be something like:

    Cadence/Allegro/16.01/
    Cadence/Verilog/5.8/

    Good luck :-)

    Steve.

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.