Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 3677
  • 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

ADE simulates, won't display results

Kaou
When I run a simulation from ADE L, it appears to complete; however, when it tries to display the results (or I try to open a results browser) I get the following output on the command window:

Loading viva.cxt 
Segmentation fault
ERROR (WIA-1118): Failed to launch Visualization & Analysis Tool because of a problem in the DFII
            installation hierarchy 'Exit Code = 219'. Contact Cadence Customer Support with the diagnostic
            information in the log file '/media/DATA/Cadence/ade_viva.log'.
INFO (WIA-1116): Writing diagnostic information.
INFO (WIA-1116): Writing diagnostic information.
ERROR (WIA-1100): Unable to establish connection with Visualization & Analysis Tool. For assistance,
            contact Cadence Customer Support with the diagnostic information in the log file '/media/DATA/Cadence/ade_viva.log'.
ERROR (WIA-1105): Failed to get the MPS handle.
ERROR (WIA-1105): Failed to get the MPS handle.
simulation completed successfully.
reading simulation data...
ERROR (WIA-1105): Failed to get the MPS handle.
      ...successful.
Loading hspiceD.cxt 
Loading UltraSim.cxt 
Loading AMSOSS.cxt 
Loading AMS.cxt 
ERROR (WIA-1105): Failed to get the MPS handle.
*WARNING* aaTriggerEvent2: error calling (lambda((_simID status) _sevAfterSimulationWrapper('sevSession1 status)) t (stdobj@0x121913d8 nil nil)) ("funcall" 0 t nil ("*Error* funcall: argument #1 should be a function object or name (type template = \"ug\")" nil)).

This started happening when I was trying to troubleshoot ADE GXL (similar issue to www.cadence.com/.../13377.aspx) and I installed libgdbm.so.2 to a folder in my path. ADE L used to work on this system, which is a Debian Wheezy installation using the NCSU CDK and now it won't. Any help in getting this issue resolved would be much appreciated.

  •  What version are you using? What does the "diagnostic information in the log file..." say? Did you do what it said and contact Customer Support?

    BTW, Debian is not a supported platform.

    Regards,

    Andrew.

  •  

    I am running Virtuoso version 6.1.3 05/19/2010 01:23 (cic612lnx) $ sub-version IC6.1.3.500.19 (32-bit addresses).

    The ade_viva.log  says ithe Visualization & Analysis Tool exited with exit code 219 after running checkwavescan Revision: 1.14.16.1.

    The only errors I could find in the log are:

    === 1st Error ===

    >>> Running sum (0xf76ee000):

    sum: (0xf76ee000): No such file or directory

     

    Configuration checks failed, status is: FAIL

    ------------------------------------------------------------------------------

    Your system is Linux, but apparently not RedHat or SuSE.

    Only these vendors are supported by Cadence at this time.

    breaksw: endsw not found.

    === 2nd Error ===

    >>> Running date:

    Thu Sep 13 20:07:20 EDT 2012

     

    output saved in /media/DATA/Cadence/ade_viva.log

     

    /usr/local/Cadence/tools/dfII/bin/viva[75]: .[882]: .: line 4: 20481: Memory fault

    /usr/local/Cadence/tools/dfII/bin/viva[75]: .[882]: .: line 5: 20482: Memory fault

    /usr/local/Cadence/tools/dfII/bin/viva[75]: .[882]: .: line 25: 20483: Memory fault

    /usr/local/Cadence/tools/dfII/bin/viva[75]: .[882]: .: line 65: 20484: Memory fault

    sub-version IC6.1.3.500.19

    === End Error ===

     

    I'm not the administrator for our university's Cadence installation, so I don't have access to Customer Support.

     

  • Running Virtuoso from the university servers gives me the following error:

    Loading viva.cxt 
    Could not create the Java virtual machine.
    ERROR (WIA-1118): Failed to launch Visualization & Analysis Tool because of a problem in the DFII
                installation hierarchy 'Exit Code = 81'. Contact Cadence Customer Support with the diagnostic
                information in the log file '/home/aonokenj/ade_viva.log'.
    ...
    ERROR (WIA-1105): Failed to get the MPS handle.
    *WARNING* aaTriggerEvent2: error calling (lambda((_simID status) _sevAfterSimulationWrapper('sevSession2 status)) t (stdobj@0x12e6e024 nil nil)) ("funcall" 0 t nil ("*Error* funcall: argument #1 should be a function object or name (type template = \"ug\")" nil)).

    Could this be an issue with my local machine's Java installation? I have seem past forum entries suggest that users switch to AWD instead of Wavescan, but this isn't even an option in 6.1x is it? How would I go about debugging this issue?
  • Hi,

    If checkSysConf is failing, you need to get your system administrator involved to upgrade patches/OS/etc. on your machine.

    A requirement of Cadence software running successfully is checkSysConf passing.  

    Also, you are using a pretty old version of IC tools.  Currently IC6.1.5 is the most recent release.

    Best regards,

    Tawna
  • This was indeed a problem on the local machine. I had recently updated Debian to the multiarch setup, and had copied some files around (including to the servers). As it turns out, a backup copy of `libc.so.6' got placed in one of the $PATH directories that Cadence was configured for. Removing the old `libc.so.6' has fixed the problem. As a side note, adding `libgdbm.so.2' to the $PATH and commenting out the `cd' and `ls' nprocedures in $NCSU_CDK/skill/misc/opusUnix.il fixed my original problem with getting ADE GXL to work.

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.