Stats

  • Locked Locked
  • Replies 13
  • Subscribers 66
  • Views 21191
  • 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

lnternal error / Elaboration error ius81

Eder

 Hi,

When using ius, i'm getting this strange error

file: ./INCA_libs/irun.lnx86.08.10.nc/svpplib/tb.sv
                Caching library 'worklib' ....... Done
        Elaborating the design hierarchy:            
        Top level design units:                      
                tb                                   
        Building instance overlay tables: .................... Done
        Enabling instrumentation for coverage types: functional   
        Generating native compiled code:                          
                worklib.tb:sv <0x7a91fa59>                        
ncvlog_cg: *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: ncvlog_cg       08.10-s008
  HOSTNAME: linux-pzu3
  OPERATING SYSTEM: Linux 2.6.27.21-0.1-default #1 SMP 2009-03-31 14:50:44 +0200 x86_64
  MESSAGE: gq_cab_to_tab - not a CAB
-----------------------------------------------------------------
ncelab: *E,CUVCGF: Code generation for worklib.tb:sv <0x7a91fa59> failed.
ncelab: *F,CGFAIL: Code generation failed for one or more modules.
irun: *E,ELBERR: Error during elaboration (status 2), exiting.

 

I wonder if somebody could even get me some advices about that, or any hints do find the origins of this error. 

 

Parents

  • In the past, someone had defined a covergroup with something like this:

        real xyz;
        covergroup abc;
            coverpoint ( xyz )...

    and that caused the crash similar to the one you've seen.

    In your ealier message, you said "I was mistakenly passing the top-level module to the -covdut switch". When you changed the list modules that you were covering, it is possible that this particular covergroup is no longer included in the coverage database and thus the crash didn't occur. If you change the list of modules again and they now include a troublesome covergroup, the crash can reappear.

    I just tried it out and I see that, for the latest versions of the software, the tool correct prints out an error message pointing to this particular problem if it appears in the source code. I'd recommend that you try updating the version if at all possible. If the problem remains, then it is a new one and sending a testcase to Cadence would be helpful. Or you could try to figure out which module you've just added by your new coverage command and try to see if any of its covergroups have unusual characteristics.

Reply

  • In the past, someone had defined a covergroup with something like this:

        real xyz;
        covergroup abc;
            coverpoint ( xyz )...

    and that caused the crash similar to the one you've seen.

    In your ealier message, you said "I was mistakenly passing the top-level module to the -covdut switch". When you changed the list modules that you were covering, it is possible that this particular covergroup is no longer included in the coverage database and thus the crash didn't occur. If you change the list of modules again and they now include a troublesome covergroup, the crash can reappear.

    I just tried it out and I see that, for the latest versions of the software, the tool correct prints out an error message pointing to this particular problem if it appears in the source code. I'd recommend that you try updating the version if at all possible. If the problem remains, then it is a new one and sending a testcase to Cadence would be helpful. Or you could try to figure out which module you've just added by your new coverage command and try to see if any of its covergroups have unusual characteristics.

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.