Stats

  • Locked Locked
  • Replies 7
  • Subscribers 64
  • Views 16319
  • 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

Internal IUS error

archive

Hi Cadence,
   I am making my system verilog code to be compatible with IUS.
   I have comipled whole code successfully with IUS tool.
   But when i am running the same code ,i am getting this run time error:

irun: 05.83-p003: (c) Copyright 1995-2006 Cadence Design Systems, Inc.
file: ../tests/system/ei_ahb_slave_simple_transfer/test.sv
                Caching library 'worklib' ....... Done
        Elaborating the design hierarchy:
        Top level design units:
                top
ncelab: *F,INTERR: INTERNAL ERROR
-----------------------------------------------------------------
The tool has encountered an unexpected condition and must exit.
Contact Cadence Design Systems customer support about this
problem and provide enough information to help us reproduce it,
including the logfile that contains this error message.
  TOOL: ncelab  05.83-p003
  HOSTNAME: localhost.localdomain
  OPERATING SYSTEM: Linux 2.4.21-37.ELsmp #1 SMP Wed Sep 7 13:28:55 EDT 2005 i686
  MESSAGE: sv_seghandler - trapno -1
-----------------------------------------------------------------
irun: *E,ELBERR: Error during elaboration (status 255), exiting.

This error is not giving any information that why it's giving this error (like file name or the line number).
So i'm not getting because of which syntax or logical or because of any other reason
this error is coming.

Please provide more information about this error.
Let me know in case of any concern you have,

--
Thanks,
Piyush Kapadiya



Originally posted in cdnusers.org by Piyushk

  • Hi Piyush,
          The only relevant options you seem to have are:

    1. Contact support@cadence.com with a sample testcase
    2. Try their latest patch (if yours is not the latest)
    3. Try and comment-out some portions of your code, do a trial-and-error approach to narrow down the issue.

    Sometimes ncelab -messages help - that prints some additional information.

    Regards
    Ajeetha, CVC
    www.noveldv.com


    Originally posted in cdnusers.org by ajeetha

  • Yeah, an internal error is almost never your fault. Contacting Cadence support is your best bet.


    Originally posted in cdnusers.org by TAM

  • I have been doing a lot of SV testing in NCSIM. I did managed to crash the tool when I did an Array of instance where I had packed arrays as the ports and signals connected to the ports. The culprit dealt with my use of .* and the by switch to .name or .name(name) I was able to work around the issue.


    Originally posted in cdnusers.org by bryan

  • I checked the LRM and this doesn't appear to be illegal. I also checked the Cadence docs, and didn't find any references to this construct being unsupported. I would suggets trying the recently released 6.1 version. If no luck with 6.1, I would suggest making a small test case and sending to your local Cadence AE or Cadence Customer support. It appears to be an case which
    is not supported and should be. ~jm


    Originally posted in cdnusers.org by Jim McGrath

  • Hi Support Team,
    I have atteched sample code of my project for your reference.
    Please refer this sample code.
    Give me update for Internal error.

    Let me know in case of any concern.

    --
    Thanks
    Piyush Kapadiya






    Originally posted in cdnusers.org by Piyushk
    testcase.sv.tar

  • Hi Supoort Team,
      I am waiting for previous  issue of  Internal IUS error.
      I had already provide you the sample code for the above mentioned issue.
     
    I am attaching the same code again with this mail.

    Please provide updates for that.
     
    Let me know in case of any concern or any information require from my side.

    --
    Thanks
    Piyush Kapadiya
    eInfochips
    Ahemedbad


    Originally posted in cdnusers.org by Piyushk
    testcase.tar.gz

  • Hi Piyush.

    If you need a fast response, you should submit bug reports direct to support@cadence.com, or to your local AE, or through the support web site at http://sourcelink.cadence.com/. That would ensure that your problem is properly logged in the support system and is given the right priority.

    Just posting to a public forum doesn't guarantee that Cadence customer support will see the problem...

    Regards,
    Steve.


    Originally posted in cdnusers.org by stephenh

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.