EE 330 Lab 1 Fall 2010

EE 330 Lab 1 Fall 2010 - EE 330 Fall 2010 Lab 1 Cadence...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
EE 330 Fall 2010 Lab 1: Cadence® Custom IC design tools - Setup, Schematic capture and simulation Objective The objective of this lab is to familiarize you with the basics of the Cadence ® Custom IC design tool, Virtuoso ® . You will first set up your account to run the IC tool, learn how to manage your files with the Library Manager, understand the basics of the Schematics Editor, and simulate a simple circuit using the Analog Design Environment (ADE). If you have never used Unix operating system before, first familiarize yourself with some of the basic Unix commands provided in Appendix A. 1. Setup Once you have successfully logged into your account on a Linux machine, you need to take a few steps before you can start using the IC design tools. A) Set Bash Shell for the account Login to http://www.asw.iastate.edu . Click on: Manage user “Net-ID” Click on: Set your login shell (Unix/Linux) Select: “/bin/bash” Click on: Update Shell Click on: logout Page 1 of 14 Update Date: 8/26/2010
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
B) Create a ~/.software file (Only once) The computer support group (CSG) has made a variety of software available for student use on the system. To enable the use of different software tools, every user needs to have a special file .software (the “.” is required!) in their home directory customized for their use. Using a text editor of your choice, create a new file by that name in your home directory, e.g. by entering “gedit ~/.software”, and enter the following lines in that file: IUS ASSURA IC These three entries enable the use of the IC design tools with analog and digital design flow capability. You will need to log out and log in for the new file to take effect. If other tools are needed for a future lab, you may have to edit this file and add appropriate entries as directed by your TA. C) Create a ~/.bashrc file (Only once) Enter the following lines in that file: if [ -f /etc/bashrc ]; then . /etc/bashrc fi D) Create a ~/.bash_profile file (Only once) Enter the following lines in that file: if [ -f ~/.bashrc ]; then . ~/.bashrc fi # User specific environment and startup programs PATH=$PATH:$HOME/bin BASH_ENV=$HOME/.bashrc USERNAME="" export USERNAME BASH_ENV PATH DISPLAY E) Create a ~/cds.lib file (only once) The Library Manager (to be discussed in the next section) keeps information about system-wide libraries as well as your design libraries in a special file called cds.lib (the contents of cds.lib file are case-sensitive ). For better organization purposes, you will create a cds.lib in your home directory. This file will include definitions of system wide libraries as well as any library that you would like to be available for all of your projects and classes. For starters, create the file with the following contents (remember to press enter at the end of second line): Page 2 of 14 Update Date: 8/26/2010
Background image of page 2
INCLUDE $CDS_SITE/cdssetup/cds.lib DEFINE analogLib $IC/tools/dfII/etc/cdslib/artist/analogLib The first line includes a cds.lib file created by the system administrators from
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 14

EE 330 Lab 1 Fall 2010 - EE 330 Fall 2010 Lab 1 Cadence...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online