startup

Report as inappropriate Your report has been received

Shared by: NiceTime

Tags

Windows startup, startup manager, How to, Startup programs, Windows XP, Absolute StartUp, operating system, windows startup manager, startup company, venture capital

Stats

views:: 84
posted:: 5/27/2010
language:: English
pages:: 11

Public Domain

Document Sample

Startup Guide NCSU MOSIS Package for Cadence 4.4.6
Department of Electrical and Computer Engineering
Microelectronics Research and Communications Institute
University of Idaho

Written by: Kevin Buck, January 2, 2003

Note: This startup guide assumes that the user has never started Cadence in their local
profile OR that the user is starting a new project directory. This tutorial also assumes that
the user has some knowledge of UNIX systems.

About Cadence
(http://www.cadence.com)

Cadence is a very powerful and useful tool. Cadence develops software for both
PC‟s and UNIX systems. Some of these tools include PSpice ( a PC Design Package ),
Allegro (a PC and UNIX Printed Circuit Board Design Package), ICFB (a Unix based
Integrated Circuits Front-to-Back Design for Analog and Digital IC Development),
DIVA (a UNIX based Graphical Verification Package to be used with ICFB and the
Design Framework II Environment), ASSURA (a more advanced and versatile UNIX
based Verification Package).
The Electrical and Computer Engineering (ECE) Department and the
Mircroelectronics Research and Communications Institute (MRCI) at the University of
Idaho (UofI) both use Cadence software. All Cadence licenses are maintained by the
MRCI. The version of Cadence used in the ECE and MRCI will only run under HP-
UNIX 11.x systems.
Cadence documentation is among the best in the industry. All documentation,
examples, and tutorials can be accessed from the programs help menus.

About the North Carolina State University (NCSU) Cadence Design Package
(http://www.cadence.ncsu.edu/index.html)

NCSU has put together a package of commonly used MOSIS design rules,
models, and pre-defined cells. Their website offers much documentation, which will not
be covered in this paper. Their documentation and tutorials can be a valuable resource.

Cadence at the University of Idaho
(http://www.uidaho.edu)

The University of Idaho Cadence website is located at:
http://www.mrc.uidaho.edu/~kmbuck/cadence.htm

Startup files for the University of Idaho NCSU package can be found on this website.
2

Chapter 1

The Operating System Called UNIX.

1.1 Introduction

UNIX is arguably the best operating system around. Since it‟s creation in the

1960‟s at Bell Labs, it has grown, mutated, and survived for three decades. Unix was the

first time-sharing dependable operating system.

UNIX brought about a new way to write software. The creators of UNIX

interconnected many small programs in the creation of a new and power operating

system. This philosophy of programming shows itself today in the software developed

for UNIX systems, more on this later.

1.2 Command Line Interface

UNIX is a command line operating system. Even Apple Corp. has seen the need

for a command prompt in it‟s new OS X (www.apple.com/macosx) operating

system.

There are some very useful commands to remember when using UNIX. Table 1.1

only provides a brief list of usefull commands. O‟Reilly (www.oreilly.com)

publishes a nice assortment of UNIX help books including UNIX IN A NUTSHELL

by Arnold Robbins.

Cadence is a US Trademark of Cadence Design Systems, Inc. All software owned by
Cadence is copyrighted. See www.cadence.com/includes/us_trademarks.html for a list of
up-to-date trademark names.
UNIX is a registered trademark of The Open Group. (www.opengroup.com)
3

1.2.1 Commands

Prompt> top
Displays and updates information about the top processes on the system.
Information the window provides include the system load level, CPU usage, Process
IDs (PID), and Memory usage. To exit type „q‟ or „cntl-c‟.

Prompt> w
Shows how long the system has been up and running and who is logged into the
machine and what they are doing. Also shows the load on the machine.

Prompt> cd
Changes working director.
Example: cd workspace_directory (changes to workspace_directory)
Example2: cd .. (changes back one directory level)

Prompt> rm [-R] (file name)
Deletes a file name. Directories can be deleted when –R is used. Be careful with
this command. You can wipe out your entire home directory space if used
incorrectly.

Prompt> cp (source_file) (/path/destination_file)
Copy a file to another file name or location.

Prompt> mv (source_file) (/path/destination_file)
Moves a file from one name to another name or path.

Prompt> man (command)
This accesses the online manual for the command. This is a useful source when
learning how to use specific commands like top, rm, cp…
Cadence is a US Trademark of Cadence Design Systems, Inc. All software owned by
Cadence is copyrighted. See www.cadence.com/includes/us_trademarks.html for a list of
up-to-date trademark names.
UNIX is a registered trademark of The Open Group. (www.opengroup.com)
4

Prompt> chmod [ugo][+-][rwx]
This command changes the permissions of a file to limit access to the user, the
group, or other. Permisions can be added [+] or taken away [-]. The permissions are
read, write, and execute.
NOTE: directories must be executable to change into them.
Example1: chmod gu+rwx (file_name) {adds permissions to the group and user to
read, write, and execute the file}
Example2: chmod guo+rwx (directory_name) {adds permissions to everyone to
read, write, and execute the directory, but not the files inside the directory}

Prompt> pwd
Displays the current working directory.

Prompt> more (file_name)
Quickly displays what‟s in a text file.
Expample: more test.in
The entire text file „test.in‟ will be displayed on the screen.

Prompt> grep
Allows you to limit a search of a text file.
Example: more test.in | grep node1
The results displayed on the screen will be the lines in the text file „test.in‟ which
contain „node1‟

Promt> xterm
This command brings up another x-terminal to execute commands in.
Example: xterm &
This will cause another xterm window to appear.

Prompt> ps
Reports process status
Example: ps –u (username)
This reports back all the processes that (username) is currently running on the
workstation. It also reports back the Process ID number (PID).

Prompt> kill (PID)
This kills the process associated with the PID. There are a number of options for
the kill statement. Use „man kill‟ to find them.

Prompt> ls
Lists files in the directory

Prompt> ll
Lists files in the directory along with their owner and permissions

1.2.1 Special Characters
Unix has some special characters that may come in useful from time to time. Here‟s
a short list

“ | “ The vertical line is called a pipe. This allows multiple options on a command
line. For example: more test.in | grep node1

“&” Allows the command to be executed in the background while leaving the
command line available for typing. This is useful when calling multiple xterms or
programs from a single window.

Chapter 2

Cadence Startup Files

2.1. Introduction

Cadence, like any other UNIX program, requires the user to inform the system

where the program is located. This is typically done through setup files that the system

administrator installs. Cadence also requires directions to specific project libraries to

properly load the NCSU package.

2.2 Startup Files

Create a directory in your home directory to store your projects. This will be your

working directory for Cadence. Start Netscape in that directory. Change to that directory

and type the following command at the prompt.

Prompt> netscape &

There is a link on the University of Idaho Cadence webpage.

(http://www.mrc.uidaho.edu/~kmbuck/cadence.htm) to obtain the NCSU startup files.

Click on the link NCSU startup files for the University of

Idaho.

1. Download the files into your working directory. (Right click, save link as)

2. Close out of Netscape.

3. Verify the files are in the working directory.

a. Type „pwd‟ at the prompt and verify that you are in your working

directory.

b. Type „ll‟ and verify that the following files are there

i. „AMI16_nom.mod‟

ii. „cadence446.ncsu‟

iii. „cds.lib‟

c. If the files aren‟t there, then copy them from their current location to the

working directory.

4. Change the permissions on the file „cadence446.ncsu‟ to make the file executable

a. Prompt > chmod u+x cadence446.ncsu

5. type „ll‟ at the command prompt to verify that the permissions changed.

6. Type the follow to start Cadence.

Prompt > ./cadence446.ncsu

7. Read everything for your information and hit continue.

Chapter 3

Welcome to Cadence

3.1 Introduction

The first and most powerful window you will find in Cadence is the little ICFB

window that appears when you startup. This window allows you to select the different

tools like Library Manager, Import/Export, Technology Dumps, Layer Editor, Analog

Environment, and allows you to open and create files. This window also displays what‟s

being executed, gives results of Design Rule Checks, and any errors that may occur.

3.2 The Library Manager

While the ICFB window is the most powerful of all the Cadence windows, the

Library Manager is probably the most useful. You can access the library manager from

the ICFB window by left clicking on:

Tools->Library Manager

The Library Manager allows you to create new libraries, new cells, and new

views such as schematics and layouts. It also allows you to edit the library paths to link

your projects to another person‟s projects without copying files.

When you open the library manager you should see four NCSU directories

1. NCSU_Analog_Parts

2. NCSU_Digital_Parts

3. NCSU_Sheets_8ths
Cadence is a US Trademark of Cadence Design Systems, Inc. All software owned by
Cadence is copyrighted. See www.cadence.com/includes/us_trademarks.html for a list of
up-to-date trademark names.
UNIX is a registered trademark of The Open Group. (www.opengroup.com)
9

4. NCSU_TechLib_ami16

In addition to the NCSU libraries there should be

1. US_8ths

2. ahdlLib

3. analoglib

4. basic

5. cdsDefTechLib

6. functional

7. rfExamples

8. rfLib

Most of these will be explained as needed. You can browse through them yourself if you

get curious.

3.2.1 Troubleshooting the NCSU Libraries

If you don‟t see these libraries, then the NCSU package did not load correctly. If you

can‟t find the problem then look on the NCSU website for assistance or ask someone for

help. It is often useful when using CAD tools to try to find the solution yourself first.

Often it‟s just a misspelling in a directory, or a character out of place.

To view the directories in your libraries in File Manager go to:

Edit-> Library Path

A number of Libraries and Paths should be displayed in a new window. Verify that those

directories are correct. If you make any changes save them in that window (File->Save).

3.2.2 NCSU’s Quickstart Instructions

The following text is part of the NCSU documentation located at the NCSU CDK

website. This is copied straight from

http://www.cadence.ncsu.edu/doc/cdsuser/quickstart.html

Creating a New Library

1. Choose ``File->New->Library...'' from the CIW (the main status window) or from
the Library Manager. (Note that the Library Manager menu customization is only
available for versions 4.4.2.100.22 and higher. We have 4.4.5.100.10 at N.C.
State; Cadence should tell you when you start what version you have. If you see
``Loading NCSU Library Manager customizations...done'' in the ``Messages''
field of the Library Manager immediately after starting Cadence, you can use
``File->New->Library...'' from the Library Manager.)
2. Fill in a name for your library (e.g. myLib) and the directory that it's going to
reside in (e.g. ~/cadence). Note that the path you specify must already exist. If
you don't specify a path, the current directory is used.
3. Click ``Attach to existing tech file'', and choose the technology you want to use.
(Note that the lengths given are drawn lengths, so e.g. the TSMC 0.25um process
is listed as "TSMC 0.3u CMOS025 (5M, HV FET)").
4. Click ``OK'', and the new library will show up in the Library Manager along with
the ``technology library'' it's linked to.

Creating a schematic

1. In the Library Manager, click on the name of the library in which you want to
create the schematic. It should highlight.
2. In the ``Cell'' field of the Library Manager, type a name for the new schematic
(e.g. ``inv'') and hit Return.
3. In the form that pops up, choose ``Composer-Schematic'' as the ``Tool''. It should
put ``schematic'' in the ``View Name'' field. Click ``OK''.
4. When the schematic window appears, use ``Add->Component'' to instantiate
components from NCSU_Analog_Parts or NCSU_Digital_Parts. (Of course, you
can also use parts from your own libraries, but you need to make ``symbol'' views

for your parts first. The easiest way to do this is to create your schematic, and then
choose ``Design->Create Cellview->From Cellview...'' in the schematic editor.)
5. Choose ``Design->Check and Save'' when you're done.

Creating a layout

1. In the Library Manager, click on the name of the library in which you want to
create the layout. It should highlight.
2. In the ``Cell'' field of the Library Manager, type a name for the new layout (e.g.
``inv'') and hit Return.
3. In the form that pops up, choose ``Virtuoso'' as the ``Tool''. It should put ``layout''
in the ``View Name'' field. Click ``OK''.
4. When the layout window appears, choose the drawing layer in the LSW (which
should appear automatically), draw rectangles with the r command and paths with
the p command. The easiest way to draw individual transistors and contacts is to
instantiate pcells with the i command.
5. Menu entries to run DRC, extraction and LVS are under the ``Verify'' menu.
6. Choose ``Design->Save'' when you're done.

Circuit Simulation (SPICE, HSPICE, Spectre)

1. Choose ``Tools->Analog Artist'' in the schematic/extracted view window.
2. For simulating digital circuits, you can use BitGen to create your stimuli.

More information on Analog Artist is in Openbook.

The NCSU CDK is (C) NC State University, 1998-2002. Users are free to use or modify
the NCSU CDK as appropriate as long as this notice appears in it. You are also advised
that you use the NCSU CDK at your own risk. By using the NCSU CDK, you assume all
liability for any resulting errors and problems.

For additional documentation about the NCSU package, please refer to the following

website:

http://www.cadence.ncsu.edu/doc/cdsuser/GettingStarted.html