• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. RF Design
  3. ERROR (VACOMP-1008): Cannot compile ahdlcmi module libr...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 20420
  • 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 (VACOMP-1008): Cannot compile ahdlcmi module library

Shaa
Shaa over 11 years ago

Dear Friends,

I have faced to this problem, when I have added a VARICAP to my VCO circuit.

Error found by spectre during AHDL read-in.
    ERROR (VACOMP-1008): Cannot compile ahdlcmi module library. Check the log file input.ahdlSimDB//bsource.va.bsource_1.ahdlcmi/Linux/../ahdlcmi.out for details. If the compiler ran out of memory, use 'setenv CDS_CMI_COMPLEVEL 0', and try again. If the reason for the failure was a syntax error, contact your Cadence Customer Support representative with the netlist, log files, behavioral model files, and any other information that can help identify the problem.
    ERROR (SFE-91): Error when elaborating the instance bsource_1. Simulation should be terminated.

Does anybody know a solution for it? 

Thanks in advance

Shaa

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Given the error in the ahdlcmi.out file:

     /opt/spectre/MMSIM111/tools.lnx86/cdsgcc/gcc/bin/cdsgcc: line 264: /opt/spectre/MMSIM111/tools.lnx86/cdsgcc/gcc/4.4/install/bin/gcc: cannot execute binary file

    The error is likely to be that you are trying to run  a 64-bit executable on a 32-bit operating system. Current versions of MMSIM only support 64-bit OS (in general all of our supported releases require a 64-bit OS, even if running the application in 32-bit mode - this has been the case for a few years now). 

    See the Platform Support Roadmap, and also the  Supported Platforms Matrix. You'll see that MMSIM10.1 supported RHEL4 as a 32-bit OS, but MMSIM12.1 requires a 64-bit OS. MMSIM11.1 is not on the list, but if memory is correct, it was the first MMSIM release to require a 64-bit OS.

    If you do:

    file  /opt/spectre/MMSIM111/tools.lnx86/cdsgcc/gcc/4.4/install/bin/gcc

    it should say something like:

     ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, not stripped

    and if "uname -a" does not have "x86_64" in the supported list, you're on a 32-bit OS. You'll need to find a machine with a 64-bit OS, or if it's 64-bit hardware on your computer (quite likely unless the machine is really old), then upgrade to a supported 64-bit OS.

     Linux lnx-mymachine 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

    Kind Regards,

    Andrew.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Given the error in the ahdlcmi.out file:

     /opt/spectre/MMSIM111/tools.lnx86/cdsgcc/gcc/bin/cdsgcc: line 264: /opt/spectre/MMSIM111/tools.lnx86/cdsgcc/gcc/4.4/install/bin/gcc: cannot execute binary file

    The error is likely to be that you are trying to run  a 64-bit executable on a 32-bit operating system. Current versions of MMSIM only support 64-bit OS (in general all of our supported releases require a 64-bit OS, even if running the application in 32-bit mode - this has been the case for a few years now). 

    See the Platform Support Roadmap, and also the  Supported Platforms Matrix. You'll see that MMSIM10.1 supported RHEL4 as a 32-bit OS, but MMSIM12.1 requires a 64-bit OS. MMSIM11.1 is not on the list, but if memory is correct, it was the first MMSIM release to require a 64-bit OS.

    If you do:

    file  /opt/spectre/MMSIM111/tools.lnx86/cdsgcc/gcc/4.4/install/bin/gcc

    it should say something like:

     ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, not stripped

    and if "uname -a" does not have "x86_64" in the supported list, you're on a 32-bit OS. You'll need to find a machine with a 64-bit OS, or if it's 64-bit hardware on your computer (quite likely unless the machine is really old), then upgrade to a supported 64-bit OS.

     Linux lnx-mymachine 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

    Kind Regards,

    Andrew.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information