Professional Documents
Culture Documents
Installation of The NCSU Design Kit: Electrical Engineering Department
Installation of The NCSU Design Kit: Electrical Engineering Department
Installationof the
NCSUDesignKit
David W. Parent
Assistant Professor
Electrical Engineering, SJSU
One Washington Square
San Jose, CA 95192-0084
Phone 408.924.3963 Fax 408.924.2925
Table of Contents
INSTALLING THE NCSU DESIGN KIT (EASY METHOD):............................................................................................... 5
Getting the NCSU Design Kit: ............................................................................................................................................................ 5
Finding a Home for the Kit:............................................................................................................................................................. 5
Using the Kit: ...................................................................................................................................................................................... 6
INSTALLING THE NCSU DESIGN KIT FROM THE NCSU SITE:................................................................................... 12
1)
Getting the NCSU Design Kit from the NCSU Site: ............................................................................................................. 12
NCSU CDK Installation Instructions ................................................................................................................................................ 19
Installation instructions ..................................................................................................................................................................... 20
Installing the kit................................................................................................................................................................................. 20
Verifying Installation................................................................................................................................................................. 21
.cshrc file used at SJSU ..................................................................................................................................................................... 23
LIST OF FIGURES:
Figure 1: NCSU Kit Down load Site. .......................................................................................................................................................................... 12
Figure 3: Download Page............................................................................................................................................................................................... 13
Figure 4: Web Form to Receive Kit............................................................................................................................................................................. 13
Figure 5: Temporary Page............................................................................................................................................................................................. 14
Figure 6: http://www.cadence.ncsu.edu/................................................................................................................................................................... 14
Figure 7: Download Page............................................................................................................................................................................................... 15
Figure 8: UNIX Command for Installing the Kit...................................................................................................................................................... 16
Figure 9: Untarred Data. ............................................................................................................................................................................................... 16
Figure 10: Starting Netscape......................................................................................................................................................................................... 17
Figure 12: Open Page.................................................................................................................................................................................................... 17
Figure 13: Choose File. ................................................................................................................................................................................................. 18
Figure 14: File Browser. ................................................................................................................................................................................................. 18
Figure 15: Open Page.................................................................................................................................................................................................... 18
Figure 16: Design Kit's Main Page............................................................................................................................................................................... 19
Acknowledgements:
This tutorial is based on the NCSU design kit. For more information, see
http://www.ece.ncsu.edu/cadence/CDK.html. Note: The Kit from NCSU is extremely helpful
in teaching IC design, this document just explains how to install it a little easier than NCSUs
method.
Chapter
Edit install.pl to reflect were the perl binary is located on your system.
Run the script:
% install.pl
Answer the questions that the script asks. It should work with out a hitch.
In your dfII directory type:
% chmod -R 555 local
This will set your permissions correctly.
#######################################################
#######################
#
#
#
#######################################################
########################
set base_dir
= "/apps/cadence"
set info_dir
= "${base_dir}/.info"
= "/bin/cat"
= "/bin/uname"
setenv CLS_CDSD_COMPATIBILITY_LOCKING NO
# this next one sets a path to our wrapper script; the script
# removes this PATH component to unmask the real executable
#
# note that we have to do this explicitly, rather than using prepend,
# because the "add" that got us here already added $CDS/bin, and we want
# it at the front of PATH (prepend won't add it if it's already there)
#---- Start clsbd ----------------------------------------------------# clsbd should always be running when we start cadence tools
# note that "bar" is a simple suid root program that starts clsbd (the
# theory is that if it's running as root, a userland process is less
# likely to take it down, and it won't be killed when the user logs out.
# we want this cuz clsbd needs to be running on all workstations that
# run cadence tools so it can respond to queries about locks. see
# chapter 11 of "Cadence Application Infrastructure User Guide" for more
# info on cls.)
#---- Display the Cadence options after the xhost message ------------if ( -f ${locker_desc} ) ${cat} ${locker_desc}
if ( ! -f /etc/rc.conf.d/rpc/enable ) then
${base_dir}/bin/startrpcbind
endif
endif
endif #---- End of Cadence Setup -------------------------------------unset base_dir info_dir locker_desc cat uname
11
Chapter
12
13
Figure 5: http://www.cadence.ncsu.edu/
You will receive an email message detailing how to down load the kit:
Hello David W. Parent,
You have recently registered to download one or more components of the NCSU CDK. This message simply verifies that the email
address you submitted is valid. Please follow the link below to continue with the download.
http://www.cadence.ncsu.edu/get_NCSU_CDK.php?id=364&name=David%20W.%20Parent&a=827133649
Thank you,
NCSU Cadence Download Manager
14
Follow the link specified in the email and a down load page will appear as in Figure 6.
15
When the tar command is finished, the output should look like Figure 8.
Use the ls command to make sure a directory called local has been created. Use the command
cd local to enter into this directory.
16
Use the pwd command to show where you have installed the local directory and then start
Netscape (Figure 9).
When Netscape comes up, go to File ... Open page (Figure 10).
A pop up will appear (Figure 11). Click on Choose File...., and a file browser will appear (Figure
12).
17
Click on README.html and the click OK. The Open Page Dialog Box should then be filled out
(Figure 13). Click on Open in Navigator to view page.
18
Installation Instructions
Verifying Installation
19
Installation instructions
These instructions assume you already have the Cadence tool set (e.g. IC 4.4.5) installed
and operational. At NCSU we run Cadence (basically IC 4.4.5 and LDV 3.0) on Sun
workstations under Solaris 2.6. Our kit has not been tested on other platforms, but there
should not be any platform dependent operations in the kit.
You should now have a local/ sub-directory with the unpacked kit. We'll refer to this
directory as $cdk_dir from here on.
The kit uses the analog netlister in concert with the CDF data on the
components to create all netlists, including netlists for LVS, so make
sure the environment variable CDS_Netlisting_Mode is set to Analog.
Note: At NCSU we use symbolic links under the top level of the Cadence tree for
each tool stream installed. For example, suppose the ic445 tools are installed at
/path/cadence/ic445. We have a symbolic link called ic that points to the
ic445 stream release. The command ls -l /path/cadence/ic would show:
/path/cadence/ic -> /path/cadence/ic445
This makes it easier to upgrade to a newer version of each tools stream. You
install the upgrade with a new stream name (e.g. ic446), and when it is tested just
point the ic link at the new tree. Users always go through /path/cadence/ic to
access the tools in this stream. It also solves the problem where some tools, like
Verilog (in the ldv stream), store information containing the absolute path. In the
case of Verilog this is the executable path/name. If the path changes, as it may if
you install a new release, users with old simulation runs will get errors until they
manually change the Verilog executable path. Always going through the same
link keeps the path consistent and avoids these errors. Use /path/cadence/ic if
you have one available in the install.pl script.
20
If necessary, change the permissions throughout the local directory so users have
the appropriate access. This will depend on your site installation. For example, we
use AFS and set access using the AFS file permissions mechanisms.
Verifying Installation
There's no formal way to verify everything's hooked in properly, but you can check pretty
quickly to see if things look ok:
1. Set any environment variables necessary (e.g., $CDS_SITE, $USE_NCSU_CDK)
and start Cadence.
2. Make sure you see the message Loading NCSU SKILL routines... in the CIW
during startup. If you're running DFII 4.4.2.100.22 or later, you should also see
the message Loading NCSU Library Manager customizations...done. in
the Library Manager.
3. Type NCSU_CDK_version in the CIW and hit RETURN; you should get back a
version string, e.g. ``NCSU_CDK 1.2''.
4. Select the ``File->New->Library...'' menu entry in the CIW. A form should appear
that looks like the picture below:
Click the ``Help'' button and make sure the appropriate OpenBook entry appears.
5. Create a library by choosing ``Compile tech file'' and selecting a MOSIS process
from the popup menu that appears. You should see the following messages in the
CIW:
6. Loading technology files...
7. Compiling class 'controls'....
8. Compiling class 'layerDefinitions'....
9. Compiling class 'devices'....
10.Compiling class 'layerRules'....
11.Compiling class 'physicalRules'....
12.Compiling class 'dleRules'....
13.Compiling class 'dlrRules'....
14.Storing symbolic cells...
15.Generating Pcell for 'm1_n layout'.
16.Generating Pcell for 'm1_p layout'.
17.Generating Pcell for 'm1_poly layout'.
18.Generating Pcell for 'm2_m1 layout'.
19.Generating Pcell for 'nmos layout'.
21
You might also see some lines like Loading XXX.cxt. Also, the exact Pcells
generated will depend on the process you chose.
26. Create and open a layout in the new library. In the LSW, nwell should be green
slash, metal 1 should be blue backslash, metal 2 should be magenta dots. The last
menu in the layout window's menu bar should be ``NCSU'' and have the
following entries:
o
Hilite Object...
Align Objects...
Import text...
22
23
# XTERM STUFF
alias xt "xterm -bg gold -fg black &"
alias con 'xterm -g 98x6+0+0 -fg lightgreen -bg black -title CONSOLE -sb -sl 15000 -C'
alias xt1 'xterm -g 80x43+0+200 -fg cyan -bg black -title TERMINAL1 -cr pink -sb -sl 30000 n TERMINAL1'
alias xt2 'xterm -g 80x43+0+119 -fg green -bg darkslategrey -title TERMINAL2 -cr wheat -sb sl 30000 -n TERMINAL2'
alias xt4 'xterm -g 80x43+0+119 -fg white -bg darkgreen -title TERMINAL3 -cr lightgreen -sb
-sl 30000 -n TERMINAL3'
alias xt5 'xterm -g 80x43+0+119 -fg green -bg darkgreen -title TERMINAL4 -cr lightgreen -sb
-sl 30000 -n TERMINAL4'
alias xt3 'xterm -g 80x43+0+100 -fg purple -bg wheat -title TERMINAL5 -cr wheat -sb -sl
50000 -n TERMINAL5'
24
#************************************************
umask 002
#************************************************
#######################################################
#######################
#
25
#
#
#
#
#######################################################
########################
set base_dir
= "/apps/cadence"
set info_dir
= "${base_dir}/.info"
= "/bin/cat"
= "/bin/uname"
26
setenv CLS_CDSD_COMPATIBILITY_LOCKING NO
# this next one sets a path to our wrapper script; the script
# removes this PATH component to unmask the real executable
#
# note that we have to do this explicitly, rather than using prepend,
# because the "add" that got us here already added $CDS/bin, and we want
# it at the front of PATH (prepend won't add it if it's already there)
27
#---- Start clsbd ----------------------------------------------------# clsbd should always be running when we start cadence tools
# note that "bar" is a simple suid root program that starts clsbd (the
# theory is that if it's running as root, a userland process is less
# likely to take it down, and it won't be killed when the user logs out.
# we want this cuz clsbd needs to be running on all workstations that
# run cadence tools so it can respond to queries about locks. see
28
#
# Let's set the DISPLAY variable
#
if ( ! $?DISPLAY ) then
set tty = `tty|sed "s,/dev/,,"`
set who = `who | /bin/grep $tty`
set where = `echo $who | awk '{print $6}'`
set loc = `echo $where | sed "s/[(,),:]//g"`
setenv DISPLAY ${loc}:0.0
unset tty who where loc
endif
29
endif
#---- Display the Cadence options after the xhost message ------------if ( -f ${locker_desc} ) ${cat} ${locker_desc}
30