We will be using information related to AMI 0.50 (C5N) process.
If using a SunBlade100 in Holmes 387, login directly to the machine [opelu, onaga, uku, uhu, mahimahi, manini] for the fastest XWindows response, or perform a remote login to quantum (the main CAD server) for the fastest processors. These machines are shared resources, so if you find that one seems slow, check to see if someone else is using it remotely, and if so, switch to another machine that has lower usage.
This lab is only available M-F 8-4:30 or when a lab monitor is on duty, currently M-F until 9 pm and Saturday 11-3.
This lab is open as posted on the www.eng.hawaii.edu website, including Saturdays. On Saturdays, the *front* door (the one facing the courtyard) to the POST building should be open. If it is not, you can call security to request it be opened between 8-4:30.
xhost + fish.eng.hawaii.edu
hostname
Save the name that is returned for below
ssh fish -l yourspectrausername -X
setenv DISPLAY hostnamefromabove:0.0Note that you won't have the full desktop from Solaris, but each of the windows will pop up individually on the local machine. The desktop will be for the local machine.
c:\cygwin\usr\X11R6\bin\startxwin.bat
Login in remotely to quantum using your spectra name and password with a command like:.
ssh -Y -l username servernameFor example: ssh -Y -l john quantum.eng.hawaii.edu
Start Menu > Hummingbird > Exceed > XDMCP Broadcast
Login in remotely to a "fish" (opelu, onaga, uku, uhu, mahimahi, or manini or quantum) that is in H387 using your spectra name and password.
You may also run XWindows passively, and connect to the Sun machine with a Secure Shell Client terminal set to tunnel X11. Follow the instructions for Linux workstation for setting the DISPLAY environment variable. When you issue a command line (such as icde) that requires an XWindow, it should open automatically.
Custom IC Bundle
to be continued ... feel free to browse the /quantum/cds200X directories in the meantime to find the products you need.
You can also print to the POST208 or other printers by first printing to a PostScript file, then transferring the file to the MSWindows machine or your wiliki account.
This command sets up your binary search path and other environment variables to use the Cadence tools
If you will be using Cadence design software alot, I recommend you add the following to the .cshrc file in your home directory:
(Your .cshrc is interpreted automatically every time you login to a machine or start a new shell. The "if (-r ...)" condition ensures that you are logged into a machine that has the software available. If you do not copy the Cadence design software lines to your .cshrc, you will need to run the source command each time you want to run Cadence products.)
At this point I recommend you try one of the tutorials:
Generic Process Design Kit:
NCSU Cadence Design Kit Libraries: Version 1.5: Version 1.3: The libraries loaded when you start your Cadence tool are defined in the cds.lib file.
Cadence design software gives preference to the cds.lib in your working directory
(such as in the comptut dir used for the Composer tutorial). If none
is found there, it will look for one in your home dir. If none is found
there, it may pull the NCSU cds.lib.
You can control what libs are loaded by making your own cds.lib file
in your home or working dir.
Mine looks like this:
The first time you use the NCSU kit in a particular
project directory, it needs to add its own cds.lib entries
and .cdsinit specifications to your own.
So the FIRST time you want to use the NCSU kit in a project directory, run:
Documentation for the kit is at:
http://www.eda.ncsu.edu/wiki/NCSU_CDK_documentation
Other helpful information may also be found at the NCSU website.
Not all users will want to load the NCSU Design Kit with every instance Cadence tool usage. It can interfere with various aspects of the Analog Environment if you are trying to use other kits or certain processes. Thus, I do not recommend putting the above "source ncsurc" line in your .cshrc unless you will always use the NCSU kit or remember to take it out if you start to work on other projects.
Version 1.3 of the NCSU Kit has been used in recent years' classes is located in /quantum/cds/IC50/local/ncsu_cdk.
You should first source cadencerc or your own preferred means of setting the path and environment variables for Cadence tool usage, then:
To use the older version of NCSU CDK:
You can access older (Version 1.3) NCSU documentation here:
/quantum/cds/IC50/local/ncsu_cdk/local/doc
See also the troubleshooting guide.
---------------------------------------------------------------------
Software Versions
The Cadence software products are updately frequently. Not all versions are licensed under our University Program participation. We have installed many versions throughout the time of our participation. You are welcome to use whichever version you choose by customization of your own .cshrc file. Instructions on this web page will lead you to use the latest version. You can always find the most current version of a product by browsing to the /quantum/cds directory, and looking for product code or name (e.g., IC for IC bundle, Assura for Assura).
The instance of a product code found in /quantum/cds will be a link to the most recent licensed version.
For example, for the IC bundle:
IC -> ../cds2005/IC5141
Software products and versions available:
---------------------------------------------------------------------
Printing
Plotting from design environment is available to the printer in Holmes 387.
UNIX PRINTING: Be sure you have enough paper in the printer for your whole print job BEFORE you send it to the printer.
If you don't, the job may start with someone else's paper, and if there is not enough paper, the job restarts again from the beginning until it has enough paper to complete. If you want to cancel a job, you must log in to spectra and type "lprm".
Getting started after logging in
After the Common Desktop Enviroment starts:
Open a terminal window (right-click the desktop, choose Hosts > This Host)
Setting your shell environment to use Cadence design software
source /usr/local/misc/cadencerc
This command should complete without errors (it has no visible output).
if (-r /quantum/cds/IC) source /usr/local/misc/cadencerc
---------------------------------------------------------------------
Start the Documentation for Cadence design software
type:
cdsdoc &
Tutorials
Some commands for starting Cadence design software programs:
(The & symbol returns the shell window to your control after the Cadence program is started.)
icde &
icds &
icms &
msfb &
icfb &
layoutPlus &
pacific &
---------------------------------------------------------------------
Some Paths to some Libraries
/quantum/cds/IC/tools/dfII/etc/cdslib/basic
/quantum/cds/IC/tools/dfII/etc/cdslib/sheets/US_8ths
/quantum/cds/IC/tools/dfII/etc/cdslib/artist/analogLib
/quantum/cds/IC/tools/dfII/samples/cdslib/sample
/quantum/cds/IC50/share/gpdk/gpdk447
/quantum/cds/MOSIS/NCSU_CDK/rel/lib/NCSU_Analog_Parts
/quantum/cds/MOSIS/NCSU_CDK/rel/lib/NCSU_Digital_Parts
/quantum/cds/MOSIS/NCSU_CDK/rel/lib/NCSU_Sheets_8ths
and many more ...
/quantum/cds/IC50/local/ncsu_cdk/local/lib/NCSU_Analog_Parts
/quantum/cds/IC50/local/ncsu_cdk/local/lib/NCSU_Digital_Parts
/quantum/cds/IC50/local/ncsu_cdk/local/lib/NCSU_Sheets_8ths
and many more ...
A few words about libraries ...
INCLUDE /quantum/cds/IC50/local/ncsu_cdk/local/cdssetup/cds.lib
INCLUDE /users3/other/akers3/comptut/cds.lib
DEFINE testlib /users3/other/akers3/testlib
DEFINE testlib2 ~akers3/ncsutest/testlib2
NCSU Cadence Design Kit
The most recent installation (Version 1.5) of the NCSU Kit is located in:
/quantum/cds/MOSIS/NCSU_CDK/rel
source /quantum/cds/MOSIS/NCSU_CDK/ncsu_userinit
Then, and every subsequent time you work on that project:
source /usr/local/misc/cadencerc
source /quantum/cds/MOSIS/NCSU_CDK/ncsurc
to set up your shell environment to use the Cadence tools and Kit.
if (-r /quantum/cds/IC) source /quantum/cds/IC50/local/ncsurc
before invoking the Cadence tools (note: the above command works the same whether you are using IC50 or IC5033 or IC5141).
(This link only works if you started the browser from Netscape on quantum.)
Cadence is a trademark of Cadence Design Systems, Inc., 555 River Oaks Parkway, San Jose,
CA 95134.
Page created and maintained by:
June Akers
University of Hawaii
Department of Electrical Engineering
consult@spectra.eng.hawaii.edu
http://ee.hawaii.edu/~akers