[an error occurred while processing this directive] |
We have a lot of software from Cadence - over 8GB worth on the Solaris platform. The most popular applications in use here at U of M include:
Note: to run Cadence software on a non-CAEN EECS department machine, the machine must be part of the software subscription program.
Under /usr/caen/bin (which should be in your search path) are wrapper scripts for the most popular Cadence applications. These scripts set the proper environment variables for you and launch the application. Available applications include:
First, identify which package it is that you're interested in and determine the install directory. Then add the following lines to your .cshrc or to a small set-up file that you intend to source prior to running the application, replacing instdir with the correct path.
ic*, dsmse, psd, ams and ldv Packages
setenv CDS instdir setenv CDS_INSTALL_DIR $CDS/tools/dfII setenv LD_LIBRARY_PATH "/usr/openwin/lib:/usr/dt/:/usr/dt/lib:$CDS/tools/lib:$CDS/tools/verilog/lib:/usr/X11/lib:/usr/lib:/usr/X11R5/lib:$CDS/tools/leapfrog/lib" setenv SHLIB_PATH /usr/lib:/lib:/usr/lib/X11:$CDS/tools/lib:$CDS/tools/verilog/lib:$CDS/tools/leapfrog/lib setenv CDS_LIC_FILE $CDS/share/license/license.dat setenv CDS_Netlisting_Mode Analog setenv PATH "$CDS/tools/bin:$CDS/tools/dfII/bin:$CDS/tools/leapfrog/bin:$CDS/tools/dracula/bin:$CDS/tools/dsm/bin:$CDS/tools/specctra/bin:$CDS/tools/pcb/bin:${PATH}" setenv CLS_CDSD_COMPATIBILITY_LOCKING NO setenv DD_DONT_DO_OS_LOCKS SETNote: If there are subpackages under $CDS/tools that you need in addition to dfII, leapfrog, etc., add them to the PATH setting above. Similarly, you can remove packages you don't need (e.g. remove leapfrog, dracula and specctra if just setting up silicon ensemble).
You may have to set NC_INST_DIR to $CDS_INSTALL_DIR for AMS.
Note: If running verilog on Red Hat 9, set LD_ASSUME_KERNEL as follows to get around the GLIBC_2.0 error:.
setenv LD_ASSUME_KERNEL 2.4.1Cadence Chip-assembly router/Virtuoso Custom Router (aka IC Craftsman) Package
setenv CDS instdir setenv CDS_LIC_FILE $CDS/share/license/license.dat setenv PATH "$CDS/tools/bin:$CDS/tools/iccraft/bin:$CDS/tools/iccraft/gds_if/bin:$CDS/tools/iccraft/lefdef_if/bin:${PATH}"SPR (Ambit) Package
setenv CDS_LIC_FILE instdir/license.dat setenv PATH "instdir/BuildGates/current/bin:${PATH}"Assura Package
setenv ASSURAHOME instdir setenv CDS_LIC_FILE $ASSURAHOME/share/license/license.dat setenv PATH "$ASSURAHOME/tools/bin:$ASSURAHOME/tools/assura/bin:${PATH}"SEV Package (VoltageStorm, Fire & Ice)
setenv SIMPLEX_HOME instdir setenv LM_LICENSE_FILE $SIMPLEX_HOME/share/license/license.dat setenv PATH "$SIMPLEX_HOME/bin:${PATH}"TSI (SignalStorm/Celtic/Pacific) Package
setenv TSIHOME instdir setenv CDS_LIC_FILE $TSIHOME/share/license/license.dat set path=($TSIHOME/tools/bin $path) setenv TCL_LIBRARY $TSIHOME/tools/sndc/lib/sndc/tcllibVSDE Package
Note: setup environment for ic package and add the following:
setenv ACV_ROOT instdir/tools/acv set path=($ACV_ROOT/bin $path) setenv LD_ASSUME_KERNEL 2.4.1 (Linux only)SNA Package
source instdir/tools/seismic/CSHRC50 setenv CDS_LIC_FILE instdir/share/license/license.datNeoCell Package
setenv CDS_LIC_FILE instdir/share/license/license.dat set path=(instdir/tools/NeoCell/bin $path)Note: you will also have to set up your environment to run the IC package.
ic, dsmse, psd, ams, tsi and ldv Packages
On caen, run cdsdoc-ldv, cdsdoc-ic, cdsdoc-soc, cdsdoc-icc or cdsdoc-dsm at a unix prompt. For tsi and ams, use cdsdoc after configuring your environment.
SPR (Ambit) Package
Run "ac_shell -visual" at a unix prompt, then select Help->Documentation from the menu in the gui that comes up. Note that you may need to have netscape up in order for this to work. There is a small tutorial with an associated technology file described in this documentation.
NeoCell Package
You'll find pdf docs under instdir/tools/NeoCell/docs
SEV and SNA Packages
You'll find pdf docs under instdir/docs or instdir/doc.
Note:The Cadence University Program requires that members upgrade to the latest version of the software each year. While older versions may still be on the system, they may not be fully licensed.