Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
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/Linux22.214.171.124-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?
after the installation of MMSIM 7.1, did you configured all packages? During this process veriloga and vhdlams libraries will be compiled and some links will be defined. Maybe this causes problem?
In reply to haikom:
I am not sure what you mean by configuring the packages? How do I do this configuration step after installation?
In reply to gokce:
InstallScape should prompt you automatically at the end of the installation - select all products it offers you, and go through answering the questions.
Otherwise hit the "configure" link on the main InstallScape page, pick the installation directory, select all the products it gives you the choice of, and answer the questions...
In reply to Andrew Beckett:
I have tried this for MMSIM-7.10.103 Hotfix version. When I select the installation directory /mmsim-7.1 for configuration, I get:
No Products available for configuration.
If I check if everything installed correctly, I see OK next to all Spectre products. So I cannot configure anything.
Er, sorry. For some reason I was mixing this up with another question, and was really talking in terms of IUS streams, which definitely do need configuring.
The one thing that you might have to do with MMSIM71 is to create a link called "tools" in the MMSIM71 installation, pointing to tools.lnx86 . In theory it's not needed, but I always have it there. Normally configuration creates this for most streams, but MMSIM71 does not need configuration, as you've found.
Thanks, for the reply, but I already have that tools->tools.lnx86 link. I believe the problem is that ahdl cannot find the C++/g++ compiler inside the spectre.
Maybe you aren't setting LD_LIBRARY_PATH to include lib folders from whichever stream(s) you're working with?
In reply to tkhan:
have a look at your environment variable PATH and enshure, that the path to gcc points to the correct directory in the correct MMSIM installation tree. Maybe this causes trouble.
I might have understood why the problem is caused, but I have no workaround. There is not a "lib" directory under:
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:
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.
I get this:
ncscGcc.ins: line 52: cd: ./tools./systemc: No such file or directory