Differenze

Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.

Link a questa pagina di confronto

Entrambe le parti precedenti la revisione Revisione precedente
Prossima revisione
Revisione precedente
vlsi:computing_cdsterm [09/04/2013 08:02]
pacher
vlsi:computing_cdsterm [30/07/2013 21:20]
pacher cancellata
Linea 2: Linea 2:
 ====== Running VLSI design platforms ====== ====== Running VLSI design platforms ======
  
-[ __[[vlsi:​home|Home]]__ ]+[ __[[vlsi:​home|VLSI Home]]__ ]
 [ __[[vlsi:​workbook|VLSI Design WorkBook]]__ ] [ __[[vlsi:​workbook|VLSI Design WorkBook]]__ ]
 [ __[[vlsi:​computing_main#​contents|Back to index]]__ ] [ __[[vlsi:​computing_main#​contents|Back to index]]__ ]
Linea 15: Linea 15:
    * [[vlsi:​computing_cdsterm#​manual_configuration|Manual configuration]] ​    * [[vlsi:​computing_cdsterm#​manual_configuration|Manual configuration]] ​
  
-**Keywords:​** environment variable, search path, ''​cdsterm''​, technology+**Keywords:​** ​UNIX environment, ​environment variable, search path, initialization script, Cadence, technology
 +vanilla environment
  
  
Linea 21: Linea 22:
 ===== Introduction ===== ===== Introduction =====
  
-Before you can run any licensed VLSI tool you need to set necessary UNIX **environment variables** ​+Before you can run any licensed VLSI tools you need to set necessary UNIX **environment variables** ​
 and add **executables** to the system **search path**. The runtime environment must be set  and add **executables** to the system **search path**. The runtime environment must be set 
 every time you start a session work, but all the stuff is automatically done for you by an  every time you start a session work, but all the stuff is automatically done for you by an 
Linea 39: Linea 40:
  
 \\ \\
-The script is a csh script that interactively sets environment variables and adds search paths +The script is a **tcsh ​script** that interactively sets environment variables and adds search paths 
 for different design platforms and technologies. for different design platforms and technologies.
  
Linea 46: Linea 47:
  
 <​code>​ <​code>​
-cd ~/​scratch/<​tech_dir+cd ~/​scratch/<​tech_dir>
 cdsterm cdsterm
 </​code>​ </​code>​
Linea 103: Linea 104:
  
 \\ \\
-All VLSI users can work with AMS and IBM technologies. The access to other cutting-edge+All VLSI users can work with AMS and IBM technologies. The access ​(using ''​cdsterm''​) ​to other cutting-edge
 technologies is restricted and it depends on the selected tool and on the user membership ​ technologies is restricted and it depends on the selected tool and on the user membership ​
 to a specific **technology group** defined by the system administrator. Technology ​ to a specific **technology group** defined by the system administrator. Technology ​
Linea 121: Linea 122:
  
 \\ \\
-Note that if the selected tool is Cadence SPB (Allegro) you are not asked to choose a technology.+Note that if the selected tool is Cadence SPB (//Allegro//) you are not asked to choose a technology.
  
  
Linea 132: Linea 133:
  
  
-{{:​vlsi:​parent_shell_and_xterm.png?​800}}+{{:​vlsi:​parent_shell_and_xterm.png?​750}}
  
 You can make a comparison between your parent shell environment and the xterm exported environment typing You can make a comparison between your parent shell environment and the xterm exported environment typing
Linea 143: Linea 144:
  
 \\ \\
-Each design tool will be launched from the xterm command prompt by invoking its specific executable  +Each design tool will be launched from the xterm command prompt by invoking its specific ​**executable  
-name with the general syntax+name** with the general syntax
  
 <​code>​ <​code>​
Linea 156: Linea 157:
 </​code>​ </​code>​
  
 +\\
 Since environment variables and search paths have been exported in xterm, don't invoke ​ Since environment variables and search paths have been exported in xterm, don't invoke ​
 a tool in the parent shell, you will get a ''​Command not found''​ issue otherwise. a tool in the parent shell, you will get a ''​Command not found''​ issue otherwise.
Linea 161: Linea 163:
 Depending on the selected tool follow the instructions listed below. ​ Depending on the selected tool follow the instructions listed below. ​
  
-   * [[computing_run_ic|Cadence IC 6.1.x (Virtuoso)]] FIXME+   * [[computing_run_ic|Cadence IC (Virtuoso)]] FIXME
  
    * [[computing_run_ius|Cadence Incisive]] FIXME    * [[computing_run_ius|Cadence Incisive]] FIXME
Linea 171: Linea 173:
    * [[computing_run_edi|Cadence EDI (Encounter)]] FIXME    * [[computing_run_edi|Cadence EDI (Encounter)]] FIXME
  
-   * [[computing_run_spb|Cadence SPB 16.x (Allegro)]] FIXME+   * [[computing_run_spb|Cadence SPB (Allegro)]] FIXME
  
 If the first time  that you try running a tool you face any problems with the Cadence ​ If the first time  that you try running a tool you face any problems with the Cadence ​
Linea 214: Linea 216:
 full-custom analog layout with Cadence IC or if you deal with digital synthesis and  full-custom analog layout with Cadence IC or if you deal with digital synthesis and 
 place-and-route with Cadence RC and Cadence SOC/EDI respectively. \\ place-and-route with Cadence RC and Cadence SOC/EDI respectively. \\
-According to this, the most part of WorkBook ​tutorial ​can be carried out with a simple ​+According to this, the most part of WorkBook ​tutorials ​can be carried out with a simple ​
 Cadence IC 6.1.x vanilla environment (the latest software release is 6.1.5). Cadence IC 6.1.x vanilla environment (the latest software release is 6.1.5).
  
Linea 223: Linea 225:
 <​code>​ <​code>​
 cd ~/​scratch/​tutorials cd ~/​scratch/​tutorials
 +setenv IC_DIR /​usr/​cadence/​IC_6.1.5
 source /​usr/​local/​config/​cds_config/​CdsIC_615.rc source /​usr/​local/​config/​cds_config/​CdsIC_615.rc
 </​code>​ </​code>​