===================================================== The Silvaco TCAD CD-ROM Winter 2004 Release For The Following Machines: SOLARIS 8 and 9 LINUX

REDHAT 7.3, 9.0 and E3 LINUX Enterprise 3 for AMD64 Copyright (c) 1995-2004 Silvaco International. All rights reserved. ===================================================== Silvaco International Building 1, 4701 Patrick Henry Drive, Santa Clara, CA 95054, USA. EMAIL: Phone: support@silvaco.com US 408 567 1000 Japan (81) 45 820 3000 Korea (82) 2 447 5421 Taiwan (886) 35 679 686 Singapore (65) 6872 3674 (44) 1480 484400 Germany (49) 89 800 6300 France (33) 456 38 10 10 US 408 496 6080 Japan (81) 45 820 3005 Korea (82) 2 447 5420 Taiwan (886) 35 679 683 Singapore (65) 6872 2497 (44) 1480 484401 Germany (49) 89 800 2451 France (33) 456 38 10 11

UK

Fax:

UK

=================================================================== CD CONTENTS ----------TCAD current TCAD-EXAMPLES current TCAD Software TCAD Examples

=================================================================== TABLE OF CONTENTS -----------------CHAPTER 1: SOFTWARE INSTALLATION 1.1 SYSTEM PREREQUISITES

1.2 CURRENT SILVACO ACTIVITY 1.3 USING THE SILVACO RELEASE CDROM 1.4 FROM A FTP DOWNLOAD OR CUSTOM CDROM CHAPTER 2: LICENSE INSTALLATION CHAPTER 3. SETTING USER ENVIRONMENTS CHAPTER 4: SILVACO INSTALLATION UPDATES CHAPTER 5: GENERAL TROUBLESHOOTING FOR SILVACO SOFTWARE APPENDIX A: SYSTEM PRE-REQUISITES APPENDIX B: SOLVING OUT OF MEMORY PROBLEMS APPENDIX C: MOUNTING THE CDROM

=================================================================== CHAPTER 1: SOFTWARE INSTALLATION --------------------------------1.1 SYSTEM PREREQUISITES ------------------------Check your system against the prerequisites described in Appendix A. Pay particular attention to the operating system version and minimum swap space requirements for the Silvaco software. 1.2 CURRENT SILVACO ACTIVITY ---------------------------------If an installation from either SILVACO already exists the user should ensure that all current jobs are completed before continuing. All Silvaco applications should then be quit. Note : Silvaco recommends that the software be installed as the root user in order that it can be controlled and deletions do not occur. 1.3 SILVACO RELEASE CDROM -------------------------When the CD has been mounted the contents of the CD-ROM are as follows (for notes on mounting the CDROM see Appendix C) : install: -------The top level contains the installation program "install". This program provides access to the entire contents of the CD-ROM and also provides step by step help to guide you. packages: --------This contains one subdirectory for each included product set.

Each of these product set directories contains one tar archive for each included platform, plus one archive of files which are required for all platforms. etc: ---These files are used in the installation process by the "install" program and should be of no interest to the user. readme: ------This file. Installation ============ Quick Installation Instructions: Logon as root. Mount the CD-ROM if necessary (see Appendix C). Change directory to the CD-ROM top level directory. Type "./install" and follow the installation steps. (or type ./INSTALL if CD-ROM is attached to an HP system)

1.4 FTP DOWNLOAD OR CUSTOM CDROM --------------------------------If the Silvaco software was obtained from a ftp download, the file should be named filename.tar.gz and can be installed as follows : - copy filename.tar.gz to the chosen /<silvaco>/ installation directory - run the command "gunzip filename.tar.gz" - run the command "tar xvf filename.tar"

=================================================================== 2. LICENSE INSTALLATION -----------------------This CD contains the new version of the Standard Floating License Manager 6 (SFLM6). New features of the license manager include - registration of the license server machine - web based front end interface to the license daemon All users are advised to install the license server as the root user on the machine hosting the software.

To begin the installation run the commands cd /<silvaco>/bin ./sflm -install You will be prompted to provide a SFLM password the first time that you run this. This password is used to access certain features of SFLM6. After the SFLM license server completes installation, open a web browser (Netscape for instance) and type in the URL http://<machine>:3162 The term <machine> should be replaced with whatever is the hostname of the license server where you just installed the software. Once the browser comes up it should show the SFLM6 Home Page (if not hit Refresh on the browser). All maintained customers must then perform two steps to get the server running - first Register the license server using the Online method (you will be asked to Register the first time you install SFLM6). Select Online registration if your browser can access the www. - once Registration is complete go back to the Home page and click on "Install New License(s)" Click on Automatic Update. This will contact Silvaco and request an automatic download of your new license file to your license server. When complete the server is ready to issue license requests. The Offline method should only be used when the server machine has no access to the www and requires sedning information to Silvaco in some other way. Please see the SFLM6 User Manual for further information.

=================================================================== 3. SETTING USER ENVIRONMENTS ----------------------------In order for users to be able to access the Silvaco software, a path should be added to each user's environment path setup as follows (this example is for csh terminal windows): set path = ( /<SILVACO>/bin $path ) where <SILVACO>is the directories chosen by the user. For example if <SILVACO> was /opt/silvaco then this would become: set path = ( /opt/silvaco/bin $path ) Each user should also modify their .cshrc file so that it includes the following:

setenv SFLM_SERVER <hostname> setenv SFLM_SERVERS <hostname> where <hostname> is the hostname of the license server machine.

Note 1: The path points to the /<SILVACO>/bin directory. Note 2: The set path statement normally resets the path variable completely, throwing away any prior setting. Make sure the above statement follows any other path statements. Note 3: Ensure that the set path statement exists outside, and preferably before, any if(...)exit statements. You need to make sure this path update is taken into account before running the Silvaco software, for example by reloading the .cshrc file (source .cshrc).

=================================================================== CHAPTER 4: SILVACO INSTALLATION UPDATES ----------------------------------------

Silvaco installations use a standard directory structure for all tools. Two major features of the structure are: The ability to install and then easily switch between different versions of the tools under a single installation area. The ability to store binary types for different platforms under a single installation area and for automatic run-time selection of the correct binary type for the current platform.

WE STRONGLY RECOMMEND THAT ALL INSTALLATION UPDATES ARE PERFORMED ON TOP OF YOUR EXISTING INSTALLATION. This feature assumes that the customer has the typical configuration of a single installation area located on a file server which is exported and mounted onto various other systems across a network. In summary, the main benefits of this standard structure are: 1. Permits unlimited versions to be installed and managed under a common directory structure. 2. Permits unlimited numbers of binary types to be installed under a common directory structure. 3. Provides automatic run-time selection of the correct binary type for the machine architecture on which the product is being executed. 4. Provides both default setting mechanisms and run-time

selection capabilities for selecting a specific version of a product to run (described below). 5. Permits different users to use different software versions without duplication of files and consequent wasted space.

Description -----------The basic form of the Silvaco directory structure is as shown below.

<install directory> | ------------------------------------------------------------------------------| | | | | | | | | | | | bin lib etc var examples man | (utilities) (fonts) | | | product [1...N] product [1...N] | ---------------------------------| | | | notes help version[1..N] default | | --------------------------------------| | | | common platforms[1..M] help notes

The basic mode of operation of the system is as follows: <install_dir>/bin is assumed to be in the user's path for anything to run. The selection of the machine type is completely automatic and invisible to the user. The selection of the version of the product to run is determined by the following four determinants (in order of precedence): The version specified using a command line option eg smartspice -V 2.6.0.R The version pointed to by the default link (if the link is present). A product default version link is a file called "default" which is a symbolic link to a version directory. The default link and the version directory that it points to must both share the same parent directory. The latest version present. This is the default.

Managing Your Installation With "s_admin" ----------------------------------------s_admin is an administration tool which is provided in order to allow the systems administrator to examine the contents of the Silvaco product directory tree, to make changes to the default links, and to delete selected versions. s_admin is invoked from <install_dir>/etc simply by typing s_admin. Normally the systems administrator would do this and would typically be logged on as root so as to have modification access to the installation area. s_admin allows the following tasks to be performed on the silvaco product directory tree: 1. Display information on all the products that are currently installed, including the versions available for each individual product, and the system platforms with which each of these versions can be used. 2. 3. any. Product version management: Remove all versions of a product for all platforms. Remove a specific version of a product for all platforms. Remove a specific version of a product for a specific platform. Product default version link management: Display information on all existing default version links, if Create/move a product default version link. Remove a product default version link.

To display the options available under s_admin, simply run s_admin from the etc sub directory of the Silvaco installation.

=================================================================== CHAPTER 5: GENERAL TROUBLESHOOTING FOR SILVACO SOFTWARE -------------------------------------------------------This section provides answers to common problems encountered by Silvaco software users after installation which are not specific to the use of a particular product. It is not recommended that users try to fix the problems described here without the help of a systems administrator, unless they have reasonable familiarity with UNIX.

PROBLEM: COMMAND NOT FOUND. A. Most likely caused by incorrect installation resulting in the directory <install_dir>/bin not being in the user's path. To check whether this is the case, enter echo $path. If the problem appears in DeckBuild, check that the path is set before any conditional exits in the .cshrc file and that the setting is not thrown away by some subsequent resetting of the path variable.

PROBLEM: CANNOT WRITE IN CURRENT DIRECTORY. A. If attempting to run software in a directory where you do not have WRITE privilege, move to a directory under the home directory and try again or ask your systems administrator to give write privileges. It is quite common for users to be in a directory for which they have write access but where the physical disk in use is attached to a different machine and mounted onto the user's machine in read- only mode only. Consult the systems administrator to check on this. If the problem persists, consult your systems administrator.

PROBLEM: FILE SYSTEM FULL. A. The software is attempting to write a file and your disk partition is full. The message usually indicates which partition is full. If it is your home (or user) partition, delete some files to give the software enough space to produce the output. Tools also write temporary files to the directory /tmp. It is possible that the partition including /tmp can be filled up. Try removing excess files from /tmp, but if the problem persists move /tmp to another partition. Check with the system administrator or systems manual to see how to do this. One temporary solution is to delete /tmp and insert a link to a different location. Refer to Appendix A: Basic System Prerequisites, for recommended sizing.

PROBLEM: ERROR ON OPEN OF <FILENAME> FILE SYSTEM ERROR. A. Caused by software not finding the correct file. Check file is in current directory and that directory path is correct. Check to see if you have read permission on this file. Check that length of pathname does not exceed 60 characters. On UNIX platforms check to ensure correct case is used, since UNIX files are case-sensitive.

PROBLEM: INSUFFICIENT VIRTUAL MEMORY.

currently obtainable: xx MB minimum required: xx MB. A. There is insufficient virtual memory (swap space) to run. The minimum amount is shown in the message. To test the amount of available memory enter memtest. Refer to Appendix B: Solving Out of Memory Problems.

PROBLEM: SYSTEM BECOMES VERY SLOW. A. Nearly always occurs because the system is configured with insufficient RAM. If running a large number of tasks on one system, then the system performance always degrades, but when the limits of available RAM are reached, a very dramatic system performance degradation occurs as the system then starts "thrashing". Refer to Appendix A: Basic System Prerequisite, for recommended sizing. Run simulations in sequence rather than in parallel. On a uniprocessor system this is almost always quicker. On a multi-processor system, limit the number of simultaneous runs to the number of processors in your system.

PROBLEM: CONNECTION TO <XYZ>:0 (OR <XYZ>:0.0) REFUSED BY SERVER, WHERE <XYZ> IS THE SYSTEM HOSTNAME ON WHICH THE USER IS ATTEMPTING TO DISPLAY. A. Occurs when operating on remote machines and trying to display graphics. Follow the proper UNIX protocol for displaying on remote machines. Ensure the environment variable DISPLAY is correct (i.e. myhost:0.0). Users need authorization to display on the display machine (enter xhost + or xhost <hostname> on the display system).

PROBLEM: HELP DOESN'T WORK. A. Occurs when the HELPPATH environment variable is incorrect. The variable is set automatically by the Silvaco scripts so this is only really likely if being overridden in the user's config files (i.e., .cshrc). Delete any such settings. Could be caused by the absence of the help files if they have been deleted.

PROBLEM: EXAMPLES LOADER DOESN'T WORK. A. The user may be attempting to view examples for a tool which is not

installed. It may be that someone has deleted the examples directory. It may be that there is no deckbuild.examples file in <install_dir>/examples (because it has been deleted).

PROBLEM: FONTS ARE NOT RIGHT. A. If on a Sun system, this is usually caused by a default font being set for OpenWindows. Try switching this off.

PROBLEM: "MANAGER" PROGRAM DOESN'T CONTAIN CORRECT ICONS. A. Delete the directory `~/.silvaco rm -rf ~/.silvaco and restart.

PROBLEM: "LIB/<XYZ>/DEFAULT NOT A SYMBOLIC LINK: IGNORED" (<XYZ> IS A PRODUCT NAME). A. A file called default in this location must be a symbolic link to a version number located under the same parent directory. If the installation directory was copied (using cp -r) rather than using tar, then all symbolic links will have been replaced by a physical copy of whatever the link originally pointed at. Do not use cp -r to replicate installation areas. If this has already been done, the user can recover from this situation by deleting default and optionally replacing it with an appropriate symbolic link.

PROBLEM: [N] +STOPPED (TTY OUTPUT) . . . A. If using C-shell on any UNIX platform, check the .cshrc file for stty commands which also cause this problem when applications are executed in background mode. Use the following syntax in the .cshrc file to exclude stty commands for non-interactive C-shell use: if ($?prompt == 1) then stty erase ^H endif This also occurs on an HP when the user tries to run any command in background with tostop set for your tty. You can check your tty settings by typing the command stty. The fix for this is to check all the setup files in the home directory for an occurrence of stty tostop (to do this run: grep tostop ~/.??*). Remove any such settings you find. Add the line stty -tostop (switch off tostop) to the .profile/ .vueprofile file (Bourne shell) or .login file (C-shell). If the problem persists, run the command in foreground mode.

PROBLEM: MISSING LIBRARY <LIBRARY_NAME> A. Since many programs now need to be shipped linked in a dynamic way it is essential that the libraries the programs require are loaded onto a system. Dynamically linking programs makes them more compatible with new machines and peripherals. With the ever increasing size of hard disks, Silvaco strongly recommends that all machines be installed with a full operating system, not a mimimalistic set. When this error is seen, the user should check that the requested library is on their machine and that that it can be found. Contact the administator to load the library. Users also need to set the library load path if libraries are in locations other than /usr/lib. On a SUN machine Silvaco recommends a minimal library search path set as follows. setenv LD_LIBRARY_PATH /usr/lib:/usr/dt/lib:/usr/openwin/lib:/usr/ucblib:/opt/SUNWmotif/lib on a HP we recommend at least setenv SHLIB_PATH /lib:/usr/lib:/usr/lib/<XVERSION> where XVERSION is the directory containing the X11 software, typically either X11, X, X11R4, or X11R5. In an attempt to make the system administrator's task easier, Silvaco ships some dynamic libraries in <installation area>/lib/support. Silvaco can not guarantee that these libraries will be compatible with users' systems due to the vast variety of hardware options available. Silvaco recommends that the correct library for the user's system is loaded off the OS media supplied with the user's system, but if the administrator wishes to try and use these libraries Silvaco ships, copy the library to the system area, typically /usr/lib.

FURTHER HELP. If you are having problems specific to a particular product or cannot solve your problem after reading this manual and the product specific manual, then please do not hesitate to contact Silvaco. For contact information please visit www.silvaco.com for you local support office or send email to support@silvaco.com.

=================================================================== APPENDIX A: SYSTEM PRE-REQUISITES ---------------------------------i. Supported Platforms: ------------------------

MAKE TYPE Operating System =================================================================== SUN superSPARC/UltraSparc Solaris 8 and 9

LINUX x86 LINUX AMD64

RedHat 7.3, 9.0 and E3 RedHat Enterprise3

ii. Disk Space: -------------minimum recommended 100 MB per user 500+ MB per user

iii. Recommended Run-Time Requirements: --------------------------------------swap space 128 MB base + 128 MB per additional processor + 64 MB per additional user 64 MB base + 64 MB per additional processor + 32 MB per additional user

RAM

temp space (/tmp) 64 MB base + 16 MB per additional processor + 8 MB per additional user

=================================================================== APPENDIX B: SOLVING OUT OF MEMORY PROBLEMS -------------------------------------------

Running out of swap space can be the cause of a myriad of problems and we strongly advise that you make absolutely sure that your system configuration is adequate in this area. The best way to check the availability of virtual memory (which swap provides) is to use the Silvaco provided utility memtest. Note that the result from memtest is the amount of currently available virtual memory as viewed by a single process. It does not show configured space. You must increase the maximum data segment size process limit as well as swap space in order to increase virtual memory available to individual processes. This particularly applies to HPUX where default kernel limits tend to be set very conservatively. Information on changing this is given later on. If the amount available is not at least as much as the minimum swap given in Appendix A, "Basic System Prerequisites", you should ask your systems administrator to change things for you.

The section below shows how to do this for the platforms which are most commonly used by our customers. Be aware that swap space is a system issue. You should contact your system vendor and not Silvaco to help you with such matters.

Increasing Configured Virtual Memory on Solaris 2 -------------------------------------------------In this example we will increase configured file system swap space by 100 Mbytes. 1. Find a partition which has enough free space by using command "df". 2. cd to the directory associated with the partition which has sufficient spare space as found in step 1. For example: cd /md 3. Make a file with the size by which you want to increase your swap space, using mkfile xxxm filename, for example: mkfile 50m swap1 We could also make a swapfile where the space is dynamically allocated only when required by the system, for use at peak times. Until it is used the space is still available for the file system. For example: mkfile -n 50m swap2 Now we have an extra 50MB permanently allocated (swap1) and 50MB which may be dynamically allocated (swap2). 4. Solaris 2.x systems (SunOS 5.x)

Append an entry in file /etc/vfstab so this swap file will be activated after each reboot. /md/swap1 - - swap - no /md/swap2 - - swap - no 5. Solaris 2.x systems (SunOS 5.x)

/sbin/swapadd (or use swap -a <filename>) Increasing Configured Virtual Memory on HPUX --------------------------------------------Important: Make sure that you also read the following section entitled "Increasing Configured Process Limits On HPUX". 1. Find a partition which has enough free space by typing "bdf".

2. Next, edit the file called /etc/checklist. At the end of the file add the following two lines: dev/dsk/0s0/ swapend 0 0 res=3000 0 0

/dev/dsk/0s0/md/swap swapfsmin=10,

Line 1 ensures that device swap is enabled on this disk. Line 2 enables a file system directory for extra swap space. The first column (the device name) must match the device shown for this directory when you used "bdf" in step 1. In this case the disk is 0s0 but this may not be the case on your system, particularly if you have multiple disks. The second column must show: - the mounted directory name in the first case. - the swap directory name in the second case. On the second line, the extra options indicate the following: min=10 Reserve a small amount of space (10 blocks in this case) when enabled, in order to check that the directory exists, has access permissions and room for the allocation. res=3000 Make sure that the swap file cannot completely fill up the file system. In this case we have told the system to reserve 3000 blocks. A typical blocksize in this case appears to be 8k rather than the 512 bytes you might expect. We recommended that you specify a reserve of no less than 2000 (16MB). If you have plenty of space you should specify a large reserve. An alternative to this is to specify max=xxx to give the maximum size that the swap area can expand to. Use this if you have a problem getting the res option to function correctly. When finished, save the file. 3. As root, type:

swapon -a Increasing Configured Process Limits on HPUX --------------------------------------------It is usually necessary to increase the maximum data segment size allowed by the process limits configured into the kernel on HPUX systems. The limit should be at least 128MB (134217728 bytes). However much swap space you configure, an individual process is never permitted to grab more than the amount of space defined by this

limit. The following summary shows you how to use "sam" in order to check and if necessary change this value. The following is applicable only to HPUX version 9.xx running on HP9000/7xx systems: - Logon as "root" and run "sam". - Select "Kernel Configuration". - Select and press "Open" button. - Select "Configurable Parameters". - Select and press "Open" button. - Wait about 10-20 seconds for this display to appear. - Move sliding scroll bar down right side of window until you see the parameter called "maxdsiz". - Select the " maxdsiz" parameter with the mouse. - Select "Actions" button at top of display. - Select "Modify Configurable Parameter..." from the "Actions" menu. Change "Formula/Value:" field to be at least 0x08000000 (128 MB); a good value for this parameter is 0x10000000 (256 MB). - Press <Return> (this will then show the new value in bytes). - Select and press "OK" button. - Select "Actions". - Select "Create a New Kernel". - Select "Yes" when prompted for confirmation. - Select "Move Kernel into Place and Reboot the System Now". - Press "OK". - When reboot is complete, use "memtest" to confirm that your change has taken effect. Remember that the figure displayed is the lower of the "maxdsiz" limit or the amount of currently available (free) virtual memory. =================================================================== APPENDIX C: MOUNTING THE CDROM ------------------------------Fist make the directory as root: mkdir /cdrom Then choose the appropriate command from the following table. Substitute the appropriate SCSI address for the value "x" and the controller number for the value "y" (0 or 1) when mounting the CDROM. ---------------------------------------------------------------------

HPUX 11.0 /etc/mount -rF cdfs -o cdcase /dev/dsk/cytxd0 /cdrom --------------------------------------------------------------------LINUX mount -t iso9660 /dev/cdrom /cdrom --------------------------------------------------------------------SOLARIS /sbin/mount -rF hsfs /dev/dsk/c0txd0s2 /cdrom (if solaris system is NOT running vold) --------------------------------------------------------------------If vold daemon is running on solaris the CD-ROM is automatically mounted.

=================================================================== END ===================================================================