How To Install Cadence Virtuoso In Ubuntu

Setting up Cadence for the Linux Machines

Steps to Follow for Setting up Cadence

Overview

Download Installscape

Setup Main Cadence Directory

Download and Setup All Cadence Tools

Download and Setup NCSU Design Kit

Permission Changes to Make Things Work

Other Changes

Overview

This tutorial explains the process that the BYU ECE section followed when installing the Cadence software during the summer of 2004. Therefore, if this tutorial is used significantly later than 2004, there may be differences, due to changes in software. The Cadence installation process was completed with Linux using Debian (version#?).

Download Installscape

The outset stride in the installation process is to download the software that speeds up downloading all of the Cadency tools. This tool will likewise permit testing and configuring of each tool later on download. Outset, become to http://downloads.cadency.com/. You lot will exist prompted to enter a username and password. In order to have a username and password you must be signed up with Cadence to access to this site, and then most likely, if you lot are wondering why yous don't have a password, you probably shouldn't be reading this tutorial.

Side by side, later entering username and password, yous will be brought to the main folio where there should exist a link to install "Installscape 3.0". Follow the necessary links and install the software probably under the /usr/local directory or where ever is desirable. After installation is consummate, you are now set up to download the Cadency tools. The first fourth dimension when you are prompted about saving or opening the Cadency tool you lot are downloading, you lot volition need to select "Open it with" and follow the hierarchy to the directory where you installed Installscape. In other words, open each Cadence installation file with .iscape.

Setup Main Cadence Directory

Follow the steps listed to create the directory that all of the Cadence tools will be installed under.

Logon as root.
Create directory in desired place (perchance /usr/local/) and telephone call this directory "cadence".
Prepare the owner of the directory using the "chown" command. Ex: chown owner1 /usr/local/cadence, where owner1 is the owner.
Go out root.

Download and Setup All Cadence Tools

The following releases of Cadence tool packages demand to exist installed on the Linux machines:

Any other tools can be installed that are included in the license. After logging into the "downloads.cadence.com" website, select the platform that your computer is running on. Select a tool bundle (start with IC5033 or the latest version that the license covers) from the list and you volition be brought to a webpage that will listing base downloads, updates, and hot fixes for that tool package. The most current version of each of these files needs to be selected for download in the order of base, update, and hot fix. Some tools will not have all three. If in that location is simply a base of operations download and a hot gear up, download the base first.

For each download, select Download by Installscape. When you lot are prompted on opening or saving the file, choose to open it with Installscape, as described before in this tutorial.

Utilise the same login and password that you used to enter the Cadence website.

Select Install without Saving an Archive.

If yous have a list that contains all of the Cadence tools covered under the license (Product_List.txt), then choose to select the list and browse through the directories to find information technology.

It doesn't matter where the enshroud directory is since information technology is temporary.

Next, choose the install directory. Make a new directory inside the "cadence" directory and name information technology the name of the tool package you are installing. If you are installing IC5033, then name the directory within the cadence directory, "IC5033".

Next, a list with the different tools covered by license are checked. Make sure that any "Softshare License" and any "Release Data for Organization Admins" tools are checked before proceeding.

After the download is consummate, in the Sorcerer View, select Test and ensure that the download completed without whatsoever errors. Then, select Configure and configure the license.

Then, exit the Magician View, and follow the same procedure for whatever updates or hot fixes (in order). Only install the nigh recent updates and hot fixes. Install them in the same directory as you installed the base.

Afterwards finishing this process, logout of the Cadence website.

Next, to brand the process easier, some symbolic links demand to be created. In the cadency directory, create a link for IC5033 (or whatever the latest version is) called "ic". For ICC111, name it "icc". For the others, practise the same. The main reason for doing this is so when in that location is a new release of a tool parcel, the link can linked to the new parcel and any path references to the tool package will automatically know where to look. It boils down to 1 change needed instead of several.

In each tool parcel directory, there is a tools.lnx86 directory. For each parcel, create a symbolic link called "tools" in the same directory as tools.lnx86.

A couple of lines of code need to be added to your "fustigate" or "cshrc" file to properly link paths of the Cadence tools. Add the following:

export LM_LICENSE_FILE= (put here where your license server or file is located)
export CDS_LIC_FILE = (put here where your license server or file is located)
export LD_LIBRARY_PATH = (library paths of ic and ldv ic/tools/lib, ldv/tools/lib, spr/tools/lib, soc/tools/lib)
consign CDS_SITE = (location of NCSU design kit installation directory - .../NCSU/local)
export CDS_Netlisting_Mode=Analog
export USE_NCSU_CDK
consign CDS = (NCSU design kit directory .../NCSU/local/cdssetup)
export PATH=$PATH:(all cadency tool directories that are required are listed below)

.../ic/tools/bin
.../ic/tools/dfII/bin
.../ic/tools/concice/bin
.../ic/tools/dracula/bin
.../ic/tools/plot/bin
.../ldv/tools/bin
.../spr/tools/bin
.../soc/tools/bin
.../icc/tools/iccraft/bin

As tools are upgraded in the future, make sure right paths are included in surround variables.

Download and Setup NCSU Blueprint Kit

The NCSU Design Kit is a kit used widely by many universities for Cadence. The kit provides many standard cells. It also configures convenient settings for the Cadence tools (i.e. hotkeys). To obtain the pattern kit, visit the NCSU (North Carolina State University) website to obtain permission here.

Subsequently filling your contact information and selecting the latest version of the kit, select "Submit Form". You lot will afterward receive an electronic mail with a link to the gzipped tar file, NCSU_CDK.one.4.tar.gz. Download and untar this file in a desired directory. A practiced place to put it may be in your cadence directory under a new directory entitled "NCSU". Access the directory and unzip/tar the file.

tar -xvvzf NCSU_CDK.i.four.tar.gz

In your NCSU directory, a local directory should have been created. Now admission, this local directory. Access the bin directory. Now, the NCSU design kit needs to be properly installed configured. This can be washed by running the script "install.pl".

perl install.pl

The script will inquire several questions, in which you should respond with the following answers:

Where is the IC tools root directory (e.k. /ncsu/cadence/ic445)?

/usr/local/cadency/ic (or wherever you put the symbolic link "ic")

You lot should have untarred the NCSU CDK tarfile in the directory in which you lot want it to reside. (If y'all take not, please do so earlier continuing.) Where is that directory?

/usr/local/cadence/NCSU

If yous employ HSPICE enter the following, or < return > to skip. Where is the HSPICE root directory?:

< return >

            A "local" directory already exists at "/usr/local/cadence/ic/tools.lnx86/dfII/local" This directory probably contains your site's customizations. I tin can move the existing directory to "local.bak" and make "/usr/local/cadence/ic/tools.lnx86/dfII/local" a link to /usr/local/cadence/NCSU/local.  If you practise not want me to do this, I tin add code to your setup files so that the NCSU CDK customizations will be used merely when the environment variable "USE_NCSU_CDK" is set up.  Practise you want me to movement your existing local/ directory? [y]

For the question regarding HSpice, if you do employ HSpice, enter the location of the HSpice root directory. The same applies to the terminal question near using the NCSU CDK customizations. If you exercise want to give the user a pick, so select "n" and respond the applicable questions that will follow.

The next thing you need to practise is to add a line in your "bash" or "cshrc" file so that the correct paths can exist linked for the NCSU CDK. Add the following:

consign CDS_SITE=/usr/local/cadence/NCSU/local/ (or wherever your NCSU/local directory is located)

Permission Changes to Make Things Work

If a user tries to offset the Cadence tools and is non the "owner" of the cadence directory, and so there volition be errors. Therefore, the permissions on a few files need to exist changed in social club to eliminate these errors. The post-obit files demand to have their permissions changed to the respective value shown:

~/cadency/NCSU/local/cdssetup/cdsenv 644 ~/cadence/NCSU/local/skill/misc/netlist_proc.il 644 ~/cadence/NCSU/local/skill/misc/delChangeBox.il 444 ~/cadence/NCSU/local/lib 777 (apply the chmod -R choice to change all directories and files within the "lib" directory) ~/cadence/NCSU/local/models/spectre (make it then all files in each directory of /spectre have 644 access, all folders should have 755)

Other Changes

Some issues accept arisen during the installation process either due to Debian or other reasons. If these problems occur, follow the suggested solution. If the solution doesn't work and further assist is needed, contact Cadence. Cadence'southward back up staff was extremely helpful to BYU during the installation process in solving various bug.

1. A message occurs when starting "icfb" in the beat window well-nigh xmesg not working because "wish" is not installed. A bulletin would display about new versions of the software, simply will not if "wish" is not installed. To eliminate this bulletin from showing upwards each time, access the cdsinit file located under ~/cadence/NCSU/local/cdssetup and make the post-obit changes:

At approximately line 171, there is a comment stating "---- Impress "new version" message ----". Under this annotate there is a variable definition for "xmesg". Annotate this line out. In the if-argument, remove anything referring to xmesg. so that the new line reads:

if( getShellEnvVar( "SKIP_CDS_DIALOG" ) == nil && isFile( newusermesg ) system( strcat( " newusermesg "&") ) )

This solution is but a simple quick fix to the message occuring when starting the Cadence tools. It may be a expert idea to copy the if statement, comment it out, and make changes to the original. This will enable you to go back to the original settings if "wish" is later installed and you want this feature to be available, merely information technology is nowhere near to crucial for Cadence operating properly.

ii. When a config file is created, Cadence freezes and is unable to open Bureaucracy Editor. This trouble is a coffee problem that is Debian-version specific. Therefore, one of the old Debian coffee library files needs to be installed in guild to fix this trouble. This file can be institute out the following url:

http://packages.debian.org/stable/oldlibs/libstdc++2.ix-glibc2.1

The file is "libstdc++2.ix-glibc2.ane-2.91.deb".

When the file is opened, "kpackage", a Konqueror tool, should open it and install it. You may need to log in as root to complete this process.

iii. In that location are bug when trying to open up documentation. The issues involve opening the web browser to read the documentation. The Linux SPICE machines have mozilla installed, only cadency looks for netscape. When a mozilla browser is already open, and then the documentation will open up in the browser window. If a mozilla browser isn't open, an error message will be given. To workaround this trouble, follow the steps listed:

type at the prompt: which mozilla (brand note of the directory returned)
blazon at the prompt: which cdsdoc (brand annotation of this directory)
go to the directory that contains cdsdoc
Create a link called 'netscape' to the mozilla executable: ln -s /mozilla netscape

Trouble solved!