Cadence IC 5.0.33 installation on Linux tutorial

[blue_moon]

cadence default bind

Hi everybody!

Because it was pretty hard for me to install Cadence the first time (thanks Edaboard, it helped A LOT) I made a small walkthrough for the installation. If anybody is interested, I can post it, upload it or give a link to my site (didn't do it now because I don't want people accusing me of promoting my site). Of course, any suggestions for improvements would be appreciated.

Thanks!

 

[qutang]

cadence tutorial config file

I just install ic5.0,I want to install 5033,can you post it?
thanks

 

[blue_moon]

cds_load_env

Well here goes, your contribution to make this better is welcomed, feel free to criticize me:

Cadence IC Linux Installation Tutorial v0.1 - 01.05.2005
--------------------------------------------------------

Disclaimer and terms of use
---------------------------
This tutorial is provided as is. The author of this tutorial shall not be
responsible for any errors or omissions or any results obtained from the use of
this information. The author of this tutorial reserves the right to change it
without notice. The trademarks found in this tutorial are the property of their
respective owners.
Copying and distributing this tutorial is welcomed and encouraged.

I. Introduction
---------------
I felt the need to write this tutorial after spending a whole week for my first
installation and two days for the second one, because the first time I didn't
wrote this tutorial. So I decided to write it so that at the next first
installation I would make everything run much faster, hopefully. Also, the fact
that I was unable to find a walkthrough for the installation made me decide to
write this tutorial, to make life easier for the people that are installing
Cadence IC for the first time. Please remember that this tutorial contains
what I've found after only two installations, so I will have to dig a lot
until this tutorial will be at least decent. But, if you don't have a clue
about what to do, I hope what I've written here will provide a few basic
starting steps. Any suggestions and corrections are welcomed and will be
included by the author in the next versions.

II. Operating system issues
---------------------------
The Cadence IC design package is provided by Cadence Design Systems:
http://www.cadence.com
A list of the officially supported computing platforms for all Cadence design
tools can be found at the Cadence site at:
http://www.cadence.com/support/computing/index.aspx . For Cadence IC the
supported Linux platforms at the time that this paper has been written are Red
Hat Linux 7.2 for IC 4.46L, 5.0.32, and 5.0.33 and Red Hat Enterprise Linux 2.1
for IC 4.1.41. Besides these, people have reported successful installations on
RH 7.3, RH 8.0, RH 9.0, FC 1, FC 2, RH Advanced Server, Debian, Suse and
Mandrake. From what I know, for Red Hat distributions above 7.3, it is
recommended that you would install Red Hat 7.2 or 7.3 and Cadence IC first and
after this upgrade to the newer version of linux. Other people just
decompressed a Cadence hierarchy from a previous installation after a
fresh installation of the operating system. My installation was based on Red
Hat 7.3 and so this is what we will talk about.

III. Installation
-------------------------------
This tutorial assumes that you have basic knowledge of linux commands. Teaching
you linux is not the purpose of this tutorial, for this there are enough
tutorials on the web. The following steps are required for installation:
1) Cadence strongly recommends not to install Cadence IC as root, instead you
should make a user just for running Cadence IC. This way you minimize the
chance of ruining your installation or the production hierarchies.
2) For this user you should set the shell to be or csh or tcsh, because it will
make your life a lot easier. Almost all of the examples for configuring the
environment are in the form of C shell commands, so if you set your shell to
bash or any other shell you will have to translate all the settings from C
shell to your shell.
3) Set the language to English, because setting it different could cause you
problems. Cadence won't recognize some international fonts.
4) The color depth of the display has to be set to 8 or 24 bit or Cadence IC
will not run. It´s as simple as that. Of course, you may have to dig for some
new drivers for your video card, if 8 bit or 24 bit is not supported.
5) You should check to see if you have enough space on your hard drive.
Cadence requiers around 2,5 GB of free space. Aditionally, if you want to copy
the installation CDs to your drive, you will need another 1,5 GB of free space.
Of course, you should keep in mind that the libraries will require additional
space.
6) Make a directory for installation, e.g. /usr/eda/cadence/ic5.0.33, we will
refer to this dir as <your_install_dir>. I made the cadence directory and also
made the ic5.0.33 directory because under the /cadence directory I was later
able to add other related directories for libraries, projects etc. You can
install different versions under different hierarchies. It is recommended that
if you already have a Cadence IC hierarchy to do the newer installation to a
different hierarchy. However, an upgrade for the current release will be
installed to the same directory.
7) Copy the installation CDs to some directories, like /usr/eda/kit/cd1,
...cd2, ...cd3. This will prevent the problems showed sometimes by KDE, by not
letting you to unmount or eject the CD during installation, of course, if you
use KDE.
8) Start the installation by running in the cd1 directory the installation
script SETUP.SH, like this ./SETUP.SH. When asked what products to install
choose Cadence Catalog and choose from there the products for which you have
licenses, enter the other information that your are asked e.g., path to the
installation files, installation directory etc. When asked for the next cd
choose Change mount point and give the paths to cd2 and cd3. After this
installation is done, install any upgrades USR or QSR that you have just like
you did above.
9) Go to the <your_install_dir> directory and make a symbolic link like this:
ln -s tools tools.lnx86

IV. Environment setup
-----------------------
For the simplicity of this tutorial we'll make two conventions that you will
understand towards the end. From here on we will use extensively these
variables:
$CDS_INST_DIR=<your_install_dir> and
$CDS_INSTALL_DIR=<your_install_dir>/tools/dfII
Please make sure where you use one and where you use the other, it's easy to
put one instead of the other. You'll say that the naming convention isn't the
best I could have chosen, but, as you will see, these names were already chosen
by the people at Cadence, so let's leave it like it is, just be careful how you
use them. By the way, dfII means Design Framework II.

Several types of files are used to set the Cadence IC environment:

1) CUSTOMIZATION FILES
The following customization files are delivered by default with the
installation:
$CDS_INSTALL_DIR/samples/local/cdsinit - site customization
$CDS_INSTALL_DIR/cdsuser/.cdsinit - user customization

2) ENVIRONMENT VARIABLES
Schematic, Layout and Graphic environment variable defaults are found in:
$CDS_INSTALL_DIR/etc/tools/layout/.cdsenv
$CDS_INSTALL_DIR/etc/tools/schematic/.cdsenv
$CDS_INSTALL_DIR/etc/tools/graphic/.cdsenv
These environments can also be customized in the user's ./cdsenv and ~/.cdsenv
files. A .cdsenv file can be created by using CIW->options->save defaults.

3) BIND KEY DEFINITION FILES
The following bind key definition files are delivered by default with the
installation:
$CDS_INSTALL_DIR/samples/local/leBindKeys.il - layout editor
$CDS_INSTALL_DIR/samples/local/schBindKeys.il - schematic editor

4) CONFIGURATION FILES
The following configuration files are delivered with the installation:
aaConfig.il - analog
dciConfig.il - Cadence to Synopsys Interface
metConfig.il - Designing with Composer using metric measurements
sysConfig.il - systems
uiConfig.il - user interface
These configuration files are used to initialize parameters and forms.

The administrator of the Cadence installation (installation referred in the
Cadence documentation as the design site) will find after installation
examples of default settings for the site in the $CDS_INSTALL_DIR/samples/local
directory. Your settings for your design site should find themselves in the
$CDS_INSTALL_DIR/local directory. This directory is not sent as part of the
software. If it exists after installation you would find an empty directory.
The site administrator must create this directory if it doesn't exists and put
in it the configuration files that he feels that are necessary.
$CDS_INSTALL_DIR/local is the site customization directory. Whenever software
is upgraded the Cadence installation process retains the site administration
directory if it exists.
The site administrator should install the "site" files as follows:
Copy $CDS_INSTALL_DIR/samples/local/cdsinit
to $CDS_INSTALL_DIR/local/.cdsinit
and modify the file. Don't forget the dot(.) in front of the name for the
second file. Directions on how to modify the file are found inside of it,
actually, as you'll see after reading this tutorial, a part of it was written
after carefully reading all the explanations in this file.
The $CDS_INSTALL_DIR/local/.cdsinit file represents your design site's startup
file. At startup, Cadence IC looks first for this file and executes it. This
site customization file can transfer the control to the user by executing the
user customization file.
The order in which Cadence IC looks at startup for the .cdsinit file is:
1) $CDS_INSTALL_DIR/local/.cdsinit - .cdsinit in the site customization
directory
2) ./.cdsinit - .cdsinit in the working directory
3) ~/.cdsinit - .cdsinit in the home directory for the current user.
Cadence stops at the first .cdsinit file found. However the design site's
.cdsinit file can check if a .cdsinit file exists in the working and home
directory and execute it. If .cdsinit does not exist in the user's working
directory then the .cdsinit in the home directory is executed, of course also
if it exists. This file will load all the application configuration files and
application bind key files. It also sets the default Skill libraries and
devices libraries search path (which may be overridden by the user
customization file).
So, the $CDS_INSTALL_DIR/local/.cdsinit file provides the site customization
for all the users, but each user can customize the design environment further
through the use of the ./.cdsinit and ~/.cdsinit files.

Also, the administrator can copy from the $CDS_INSTALL_DIR/samples/local
directory into $CDS_INSTALL_DIR/local directory the default bind key definition
files supplied for different applications and modify them for his needs. The
relevant bind key definitions files must be loaded if you want bind keys
defined for that application. These files are loaded by the
$CDS_INSTALL_DIR/local/.cdsinit file and are the defaults for all users. Each
user can also have its own bind key files and load them to override the
defaults through either the ./.cdsinit or ~/.cdsinit files.
The bind key definition files are not automatically loaded. The search order
for the bind key definition files is:
.
~
$CDS_INSTALL_DIR/local
$CDS_INSTALL_DIR/samples/local
Normally, it should be allowed to the users to copy files from the
$CDS_INSTALL_DIR/local/ directory. This way, they would have a model after
which they can do their own customization files.

The configuration files ( the ones with the .il extension ) are not
automatically loaded. The search order for the configuration files is:
.
~
$CDS_INSTALL_DIR/local

In the $CDS_INSTALL_DIR/cdsuser the administrator will find after installation
a .cshrc file. This is the default configuration file for the C shell. This
file should be copied to the ~ directory of each user and modified according to
the following directions. Add the lines listed below to the .cshrc. Also read
careful the instructions found inside this file. Some of the variables are case
sensitive, so be careful.

#Cadence paths
setenv CDSDIR <your_install_dir>
setenv CDS_ROOT <your_install_dir>
setenv CDS_INST_DIR <your_install_dir>
setenv CDS_INSTALL_DIR <your_install_dir>/tools/dfII
set path = ( $path $CDSDIR $CDS_ROOT/tools/bin $CDS_ROOT/tools/spectre/bin )
set path = ( $path $CDS_INSTALL_DIR/bin )
#A bug in IC5.0.33
setenv CDS_Netlisting_Mode "Analog"
#License server port and address setup
setenv LM_LICENSE_FILE port@licenseserver

The first 5 lines set the paths to your installation and to the directory where
the binary files are. The CDS_Netlisting_Mode variable must be set to Analog,
otherwise some strange errors will appear. For example, if you will use a
source that is of type pulse, the generated netlist for simulation will not
contain the type=pulse setting and this will cause an error. The last line
sets the port and IP address of the license server. In my case, I installed
Cadence on a workstation, however, if you make a installation of the license
server, you need to start the daemons for licensing. I will update this
tutorial as soon as I will make my first installation of this kind.

Also there are a few more files where you can do environment configuration.
These are:
- .cdsenv has a similar search order to .cdsinit - although there is a UNIX
environment variable $CDS_LOAD_ENV which controls where it looks (see
documentation for more detail). This file is a file of Cadence "environment"
variables.
- .Xdefaults and .xresources
In order for any window placements to work correctly the following X resource
must be set in the .Xdefaults or .xresources file pertaining to your hardware
platform:
Mwm*clientAutoPlace: False
After setting the resource you must read in the resource file with the command
xrdb <resource_filename>
and restart the Motif window manager.
- .simrc - simulation/netlisting startup - similar locations to .cdsinit. For
simulation setup one would copy the .simrc file from the
$CDS_INSTALL_DIR/cdsuser to the . or ~ directory.
- cdsLibMgr.il - customisation of library manager - similar locations to
.cdsinit, actual filename may be changed in .cdsenv
- display.drf - display resources file - found using Cadence Search File
mechanism ("setup.loc"), covered in Cadence Application Infrastructure (CAI)
guide
- cds.lib - found using Cadence Search File mechanism, this file stores the
libraries available for a certain project. Typically you would have a cds.lib
file in you ~ directory which loads the standard libraries from your
manufacturers and a cds.lib file in your . directory which should also contain
your local defined libraries for the current project.
- cdsinfo.tag - found using Cadence Search File mechanism (see CAI guide for
more details)
- .oceanrc - like .cdsinit, but for "ocean" executable
- hdl.var - used by digital simulation tools
- ams.env - like .cdsenv - used by AMS Designer

There are more - these are just those I found during my installation and
reading on the net.


V.Further documentation
---------------------
If you need to find out more about Cadence IC or have a problem for which this
tutorial unfortunately was unhelpful, you can try on the internet:

https://www.edaboard.com - very nice forum, it helped me a lot at my
first installation
http://news-reader.org/comp.cad.cadence/ - another nice forum

 

[eins99]

cadence ic tutorial

Plus this one, then everything is so good about this IC installation.

 

[Sergiu_Q]

label:^none

how can we set Aptivia?
for Aptivia we need to make a simbolik link (exactly how we did with cadence)....but how we will do this link ?

 

[m233565]

cadence tutorial for linux

Hi,..

How to get the cadence installer??

 

[mohamed.hagag]

Re: cadence tutorial for linux

Hi,..

How to get the cadence installer??

iam sorry i have this problem


- - - Updated - - -

iam sorry but i have this problem