Stats

  • Locked Locked
  • Replies 11
  • Subscribers 125
  • Views 19947
  • 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.

VoTuanMinh

Hi all,

I am a new commer to Cadence, when I tried to simulate with Veriloga, I got the Error as follow:

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

ERROR (VACOMP-1008): Cannot compile ahdlcmi module library. Check the log file input.ahdlSimDB/1085_Minh_SAR_12bit_BST_Switch_veriloga_veriloga.va.BST_Switch.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 BST_Switch. Simulation should be terminated.

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

And here is the content of the "ahdlcmi.out"

ahdlcmicompile: Compiling ahdlcmi in input.ahdlSimDB/1085_Minh_SAR_12bit_BST_Switch_veriloga_veriloga.va.BST_Switch.ahdlcmi/Linux/ for Linux with optimize using gcc on Mon Jun  2 17:22:04 ICT 2014 [5.0]
ahdlcmicompile: Generating makefile
PATH:  /usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cdsgcc/gcc/4.1/install/bin:/usr/bin/Cadence/IC614-500-13/bin:/usr/bin/Cadence/IC614-500-13/tools/bin:/usr/bin/Cadence/IC614-500-13/oa_v22.04.073/bin:/usr/bin/Cadence/MMSIM11-10-228/tools/bin:/usr/bin/Cadence/IC614-500-13/share/cdsdoc/bin:/usr/bin/Cadence/IC614-500-13/share/bin:/usr/bin/Cadence/IC614-500-13/tools/spectre/bin:/usr/bin/Cadence/IC614-500-13/tools/dfII/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LD_LIBRARY_PATH:  /usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cdsgcc/gcc/4.1/install/lib:/usr/bin/Cadence/MMSIM11-10-228/tools/lib:/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/mdl/lib:/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/mmsim/lib:/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/inca/lib:/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/lib:/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/lib/SuSE:/usr/bin/Cadence/IC614-500-13/tools/lib:/usr/bin/Cadence/IC614-500-13/tools/lib/SuSE/SLES11:/usr/bin/Cadence/IC614-500-13/oa_v22.04.073/lib/linux_rhel40_32/opt:/usr/bin/Cadence/IC614-500-13/tools/QT/lib:/usr/bin/Cadence/IC614-500-13/tools/dfII/lib:/usr/bin/Cadence/IC614-500-13/tools/sev/lib:/usr/bin/Cadence/IC614-500-13/tools/inca/lib
Can't exec "mpstat": No such file or directory at /usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/ahdlcmi/bin/getCPUnum.pl line 41.
/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/ahdlcmi/bin/gnumake -j2 -f GNUmakefile
Can't exec "mpstat": No such file or directory at /usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/ahdlcmi/bin/getCPUnum.pl line 41.
Compiling C file BST_Switch_func.c (optimize) with -O0
/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cdsgcc/gcc/4.4/bin/gcc  -march=i686 -m32 -ffast-math -O0 -DSYSV -DSVR4 -D_REENTRANT -fPIC   -DconfigSPECTRE -I. -I/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/ahdlcmi/include -c BST_Switch_func.c -o obj/optimize/5.0/BST_Switch_func.o || rm -f -f obj/optimize/5.0/BST_Switch_func.o
Compiling C file BST_Switch_DcFuncDerLoad.c (optimize)
/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cdsgcc/gcc/4.4/bin/gcc  -march=i686 -m32 -ffast-math -O3 -DSYSV -DSVR4 -D_REENTRANT -fPIC   -DconfigSPECTRE -I. -I/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/ahdlcmi/include -c BST_Switch_DcFuncDerLoad.c -o obj/optimize/5.0/BST_Switch_DcFuncDerLoad.o || rm -f -f obj/optimize/5.0/BST_Switch_DcFuncDerLoad.o
/bin/sh: Illegal option -h
/bin/sh: Illegal option -h
rm -f -rf BST_Switch_func.c
rm -f -rf BST_Switch_DcFuncDerLoad.c
Compiling C file BST_Switch_DcFuncLoad.c (optimize)
/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cdsgcc/gcc/4.4/bin/gcc  -march=i686 -m32 -ffast-math -O3 -DSYSV -DSVR4 -D_REENTRANT -fPIC   -DconfigSPECTRE -I. -I/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/ahdlcmi/include -c BST_Switch_DcFuncLoad.c -o obj/optimize/5.0/BST_Switch_DcFuncLoad.o || rm -f -f obj/optimize/5.0/BST_Switch_DcFuncLoad.o
Compiling C file BST_Switch_TranFuncDerLoad.c (optimize)
/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cdsgcc/gcc/4.4/bin/gcc  -march=i686 -m32 -ffast-math -O3 -DSYSV -DSVR4 -D_REENTRANT -fPIC   -DconfigSPECTRE -I. -I/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/ahdlcmi/include -c BST_Switch_TranFuncDerLoad.c -o obj/optimize/5.0/BST_Switch_TranFuncDerLoad.o || rm -f -f obj/optimize/5.0/BST_Switch_TranFuncDerLoad.o
/bin/sh: Illegal option -h
/bin/sh: Illegal option -h
rm -f -rf BST_Switch_DcFuncLoad.c
rm -f -rf BST_Switch_TranFuncDerLoad.c
Compiling C file BST_Switch_TranFuncLoad.c (optimize)
/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cdsgcc/gcc/4.4/bin/gcc  -march=i686 -m32 -ffast-math -O3 -DSYSV -DSVR4 -D_REENTRANT -fPIC   -DconfigSPECTRE -I. -I/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/ahdlcmi/include -c BST_Switch_TranFuncLoad.c -o obj/optimize/5.0/BST_Switch_TranFuncLoad.o || rm -f -f obj/optimize/5.0/BST_Switch_TranFuncLoad.o
Compiling C file BST_Switch_cmi_c.c (optimize)
/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cdsgcc/gcc/4.4/bin/gcc  -march=i686 -m32 -ffast-math -O3 -DSYSV -DSVR4 -D_REENTRANT -fPIC   -DconfigSPECTRE -I. -I/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/spectre/ahdlcmi/include -I/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cmi/include -c BST_Switch_cmi_c.c -o obj/optimize/5.0/BST_Switch_cmi_c.o || rm -f -f obj/optimize/5.0/BST_Switch_cmi_c.o
/bin/sh: Illegal option -h
/bin/sh: Illegal option -h
rm -f -rf BST_Switch_TranFuncLoad.c
rm -f -rf BST_Switch_cmi_c.c
/usr/bin/Cadence/MMSIM11-10-228/tools.lnx86/cdsgcc/gcc/4.4/bin/gcc -shared -O3 -fPIC -o obj/optimize/5.0/libahdlcmi.so ./obj/optimize/5.0/BST_Switch_func.o ./obj/optimize/5.0/BST_Switch_DcFuncDerLoad.o ./obj/optimize/5.0/BST_Switch_DcFuncLoad.o ./obj/optimize/5.0/BST_Switch_TranFuncDerLoad.o ./obj/optimize/5.0/BST_Switch_TranFuncLoad.o ./obj/optimize/5.0/BST_Switch_cmi_c.o  -m32 -Wl,-rpath,/usr/lib -Wl,-rpath,/lib -s
/bin/sh: Illegal option -h
gnumake: *** [obj/optimize/5.0/libahdlcmi.so] Error 2

 

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

I read some Solved threads in this forum and tried to solve but I couldn't. (For e.x add "-64" in UsrOptionField)

Could anyone here please help me to solve this problem?

Thank you so much in advance.

 

Minh

Parents
  • Andrew Beckett

    Minh,

    First of all, Ubuntu is not a supported OS distribution - so really you should use something that is supported (Red Hat Enterprise, SuSE Enterprise). 

    Failing that, you might be able to fix this by changing the link of /bin/sh to bash. This will require root access. First of all, check that "ls -l /bin/bash" exists, then:

    cd /bin
    rm sh
    ln -s bash sh

    I'm not 100% sure that this will fix your compilation problem, but I hope so...

    I tried going the other way, but I have a newer version of MMSIM on my laptop (I could check when I'm in the office), and that doesn't seem to have a problem with the wrong shell being used. So another alternative might be to install MMSIM13.1

    Regards,

    Andrew.

  • qamar
    in reply to Andrew Beckett

    Hi Andrew

    I am also having the same issue. I tried the

    rm sh

    command but I got reply permission denied. 

    Regards

    Qamar.

  • Andrew Beckett
    in reply to qamar

    Qamar,

    You'd have to do this as root (or using sudo) - but I would suggest you do it very carefully. If you didn't know that you needed to be root to make this change, it would be wise to defer to somebody who has sufficient IT skills?

    Regards,

    Andrew.

  • qamar
    in reply to Andrew Beckett

    Hi Andrew

    Thanks for your reply. I will try this option if this option is possible for them. I have noticed one thing if I use elements from Analog Lib (ideal resistor) instead of Foundry Lib (rpolyh) then there is no error and it is working perfectly fine for me. I am a new user of the Ubuntu environment. Don't know how to add that Foundry Lib information into it. Thanks in advance for your time in this regard.

    Best Regards

    Qamar

  • Andrew Beckett
    in reply to qamar

    Qamar,

    I'm not really sure what you're asking about with "Don't know how to add that Foundry Lib information into it". The issue you're having is with the models - it's not to do with which symbol library you use.

    Regards,

    Andrew.

Reply
  • Andrew Beckett
    in reply to qamar

    Qamar,

    I'm not really sure what you're asking about with "Don't know how to add that Foundry Lib information into it". The issue you're having is with the models - it's not to do with which symbol library you use.

    Regards,

    Andrew.

Children
  • qamar
    in reply to Andrew Beckett

    Hi Andrew

    Thanks for your reply and sorry for the misunderstanding. I would like to say that if I am using standard cells provided by cadence then my ocean script is working. But if I am using cells provided by our process foundry then it is giving me that error. 

    * My ocean script is working for both cases if I call my ocean script from the Virtuoso CIW window. But if I call the ocean script from the terminal window then it is working only with standard cells (for process foundry cells it is giving me the error).

    Best Regards

    Qamar

  • Andrew Beckett
    in reply to qamar

    I don't see why it should make any difference whether you are using the OCEAN script from the CIW or from the terminal window (although perhaps it depends what you mean by that - normally running the "ocean" command is just running virtuoso without the graphical environment, so I'm not sure what you are doing here).

    Perhaps you should contact customer support rather than relying on my guessing what's wrong with your setup?

    Regards,

    Andrew.

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.