Stats

  • Locked Locked
  • Replies 36
  • Subscribers 130
  • Views 29689
  • 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

VerilogA Problem in MMSIM-7.1

gokce

Hi,

 I am having a problem to simulate my verilogA files under MMSIM 7.1. They work fine under MMSIM-6.0. In spectreout, I get:

ERROR (VACOMP-1008): Cannot compile ahdlcmi module library. Check the log file input.ahdlSimDB/3821_soi12so_Test_Tapeout_Sept09_BinarySearch_veriloga_veriloga.va.BinSearch.ahdlcmi/Linux2.6.11.4-21.9-smp+gcc/ 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.

 In  ahdlcmi.out, I get:

/usr/cds/mmsim-7.1/tools.lnx86/systemc/gcc/4.1/bin/gcc  -march=i486 -ffast-math -O3 -DSYSV -DSVR4 -D_REENTRANT -fPIC   -DconfigSPECTRE -I. -I/usr/cds/mmsim-7.1/tools.lnx86/spectre/ahdlcmi/include -c BinSearch_DcFuncDerLoad.c -o obj/optimize/5.0/BinSearch_DcFuncDerLoad.o || rm -f -f obj/optimize/5.0/BinSearch_DcFuncDerLoad.o;
gcc: error trying to exec 'cc1': execvp: No such file or directory

I attached the log files. Does anyone have an idea?

 

Thanks,

Gokce

netlist.zip
  • gokce

     Hi,

    I might have understood why the problem is caused, but I have no workaround. There is not a "lib" directory under:

     /mmsim-7.1/tools/systemc/gcc/4.1/install

     This probably causes the problem "cc1 not found" issue. I realised that under an earlier version of MMSIM, I have a directory called lib here:

    /usr/cds/mmsim-6.0/tools/systemc/gcc/install

    In the ahdlcmi.out file that I get when trying to compile my veriloga module, it spits out the LD_LIBRARY_PATH:

    LD_LIBRARY_PATH:  /mmsim-7.1/tools.lnx86/systemc/gcc/4.1/install/lib (and other stuff following this)

    But, as I mentioned, no lib directory is found there. I am not sure why this directory is absent, but I will try reinstalling MMSIM-7.1. I suspect there is something missing in the installation package.

     

  • Andrew Beckett
    Can you try running:

    /tools/systemc/files/install/ncscGcc.ins

    Regards,

    Andrew.
  • gokce

     I get this:

    ncscGcc.ins: line 52: cd: ./tools./systemc: No such file or directory

  • Andrew Beckett
    It might need some env var setting. I'll have to check - probably tomorrow though.

    Regards,

    Andrew
  • aplumb
    If that's exactly the error message, check your tools link. I wouldn't expect to see a '.' after the 'tools' in './tools./systemc':

    ln -s tools.lnx86 tools

    ...not...
    ln -s tools.lnx86 tools.

    Andrew (P)
  • gokce

     I think my tools link is fine:

    /mmsim-7.1>cd tools

    /mmsim-7.1/tools>pwd

    /mmsim-7.1/tools.lnx86

     It is most likely the issue with the ncscGcc.ins. The line that gives the error is:

    cd $Proot/tools.$install_target/systemc

    I think $install_target is not defined anywhere, so it tries to login to "tools." rather than something like "tools.lnx86" .

    Gokce

  • aplumb
    Yeah, probably something 'uname' derived that's not working.
  • Andrew Beckett
    Actually $install_target would normally be set by installScape. I've not checked the rest of the script, but try doing:

    setenv install_target lnx86

    Before running the script.

    Regards,

    Andrew
  • gokce

     I set install_target as you suggested. I also needed to set Proot to mmsim-7.1. After doing this, the script worked, but I don't know what it has accomplished. It does return to command line in less than a second without printing out anything (no errors or progress reports).

  • Andrew Beckett
    OK, but did the missing lib dir get created, and does spectre now 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.