Stats

  • Locked Locked
  • Replies 36
  • Subscribers 130
  • Views 29723
  • 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
Parents
  • Andrew Beckett

    Ted,

    The fact that it works with one kit but not another doesn't prove that much - the difference may be down to something in bsource models or Verilog-A which is different between the two sets of models (the C compilation is used for bsource/VerilogA code). I'd be surprised if its a path issue (although to be honest I didn't really look very hard since the versions involved were so archaic and the OS was relatively new.

    Looking at the error you got from trying to re-run the installer, it appears that it has failed to identify the platform (hence the "tools./systemc" bit in the message - it should be tools.lnx86/systemc) although gcc must be installed somehow otherwise it wouldn't work with either kit (and I'm sure the TSMC kits are using bsource models at least).

    You could try MMSIM14.1 (that's fine to use with IC5141). I would expect that the processes you're using also have IC61X PDKs available too (as far as I know all the TSMC 65nm and 90nm PDKs do nowadays, although you might have to explicitly request them). That said, you may not want to change from CDB to OA in the middle of a project since it needs a data migration... but regardless of this, you should be able to use the latest MMSIM version with IC5141 (I do this frequently).

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    Ted,

    The fact that it works with one kit but not another doesn't prove that much - the difference may be down to something in bsource models or Verilog-A which is different between the two sets of models (the C compilation is used for bsource/VerilogA code). I'd be surprised if its a path issue (although to be honest I didn't really look very hard since the versions involved were so archaic and the OS was relatively new.

    Looking at the error you got from trying to re-run the installer, it appears that it has failed to identify the platform (hence the "tools./systemc" bit in the message - it should be tools.lnx86/systemc) although gcc must be installed somehow otherwise it wouldn't work with either kit (and I'm sure the TSMC kits are using bsource models at least).

    You could try MMSIM14.1 (that's fine to use with IC5141). I would expect that the processes you're using also have IC61X PDKs available too (as far as I know all the TSMC 65nm and 90nm PDKs do nowadays, although you might have to explicitly request them). That said, you may not want to change from CDB to OA in the middle of a project since it needs a data migration... but regardless of this, you should be able to use the latest MMSIM version with IC5141 (I do this frequently).

    Regards,

    Andrew.

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.