Scribd
Upload
64 views1 page

Cadence Labs Setup Instructions

This document provides instructions for running Cadence tools on a Unix system via an Xwindows display emulator from a Windows workstation. It instructs the user to copy a provided .cshrc file to set their environment and run an alias script called 'cds' to set paths for the Cadence tools. The document also instructs users to make a copy of each lab directory, view the instructions for each lab in .doc files within the directories, and run tools from within each lab directory for project-level setups to run automatically.

Uploaded by

naveensilveri
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
64 views1 page

Cadence Labs Setup Instructions

This document provides instructions for running Cadence tools on a Unix system via an Xwindows display emulator from a Windows workstation. It instructs the user to copy a provided .cshrc file to set their environment and run an alias script called 'cds' to set paths for the Cadence tools. The document also instructs users to make a copy of each lab directory, view the instructions for each lab in .doc files within the directories, and run tools from within each lab directory for project-level setups to run automatically.

Uploaded by

naveensilveri
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd

Instructions for All Cadence Labs

1) Cadence tools run only on Unix. From a windows workstation, you must open a shell client (e.g. SSH from SSH Communications Security Corp.) and run an Xwindows display emulator (e.g. X !in"# from Star$et or eXceed from Humming%ird). Set your display resolution to &#'( x &(#). *f you are +a,ing display pro%lems ( ' %it pseudocolor, or any X window display pro%lem w+ic+ pre,ents t+e Cadence tools from starting) please notify t+e folks in CS-. 2) .ake sure you +a,e a clean .cshrc %efore starting t+e Cadence tools. Slig+t c+anges in t+e Unix en,ironment can +a,e frustrating effects on tools of t+is complexity. * recommend you %ack up your existing .cshrc, and copy t+e one * +a,e modified. /+is is t+e standard .cshrc w+ic+ CS- pro,ided for me in 0ugust, %ut wit+ an 1alias2 definition instead of t+e Cadence setups. /+e new alias cds, will call a script to perform all Cadence setups. ... > cd macquigg@shelltoe:~> mv .cshrc .cshrc_bak macquigg@shelltoe:~> cp ~edatools/.cshrc . Open a ne shell to use the ne .cshrc 3) /o set your en,ironment for running Cadence tools, 3ust type t+e alias cds. /+is will s+ow you a list of cds aliases defined in t+e script, and t+e current pat+ settings for t+e default alias. 4ou can switc+ from one toolset to anot+er %y 3ust typing t+e alias. For t+is class, 3ust lea,e t+e default settings (alias cds!!"). macquigg@shelltoe:~> cds ... list o# aliases ... ... current path settings ... $ote5 *f you want your own custom setup script, you can copy ~edatools/setups/scripts/setup$%&.csh to your +ome directory and make c+anges to your own copy. 6e sure to c+ange t+e definition of cds in your .cshrc or it will still call t+e original. 4) .ake your own copy of eac+ la% directory. e.g. macquigg@ece':~/(%)labs> cp *r ~edatools/labs/lab+ . 5) *nstructions for eac+ la% are in t+e ,()%-(.doc files. 7iew t+ese files %y opening t+em in !ord (from your 182 dri,e). 9t+er formats (.htm and .t.t) may %e in t+e la% folders also. 6) /+e setups and initiali:ations specific to eac+ la% will all %e contained wit+in t+e directory for t+at la%. *f you start t+e tools from t+e la% directory, t+ese 1pro3ect le,el2 setups will run automatically.

~edatools/labs/README.doc

DMQ 5/4/04

You might also like