Synopsys Logo
    HELPING YOU DESIGN THE CHIP INSIDE


DESIGN IMPLEMENTATION
VERIFICATION
INTELLECTUAL PROPERTY
DFM/TCAD
DESIGN SERVICES
Arrow NEWSROOM
Arrow PLATFORM & RELEASES
Arrow PUBLICATIONS
Arrow CUSTOMER EDUCATION

Arrow SOLVNET
Arrow SEARCH FOR IP
Arrow SVP CAFE
Arrow SNUG

Back to TCAD Home

Products

TCAD Release 9.0 Known Problems for Related Tools

 DESSIS

DESSIS cannot find certain materials [90-2]
[All_archos]
Some materials have aliases such as Oxide/SiO2, PolySi/PolySilicon, Si3N4/Nitride, Photoresist/Resist, and Gas/Vacuum/Ambient. DESSIS recognizes only one name for such materials. It is the first one that appears in the datexcodes.txt file.

Solution
Use the first material name appearing in the datexcodes.txt file. For the distributed version of the datexcodes.txt file, the recommended names for these materials are Oxide, PolySi, Si3N4, Photoresist, and Gas.

Raytracing on IBM causes PARDISO to fail [90-13]
[IBM]
Raytracing simulations on IBM using PARDISO as the linear solver lead to a failure in PARDISO. This may occur when only one processor is used.

Solution
Select a different linear solver such as SUPER or UMFPACK in the Math section of the DESSIS command file. Alternatively, set the environment variable OMP_SCHEDULE to STATIC.

Under the csh shell:
 csh> setenv OMP_SCHEDULE STATIC
Under the bash shell:
 bash> OMP_SCHEDULE=STATIC
 bash> export OMP_SCHEDULE

DESSIS is exhausted of file descriptors [90-14]
[All_archos]
DESSIS is depleted of file descriptors when too many inserted files appear in the DESSIS parameter file. The number of files that can be inserted depends on the operating system. On Sun, more than 100 inserted files can lead to this problem and DESSIS fails.

Solution
Use fewer parameter files or expand the inserted files manually.

DESSIS does not put noise output into extraction files [90-15]
[All_archos]
If only circuit elements are present in a noise simulation, DESSIS fails to put noise output in the extraction files for these elements.

Solution
Add an artificial device element into the circuit. The problem will be fixed in ISE TCAD Release 9.5.

DESSIS fails on HP-UX [90-31]
[HP-UX]
On HP-UX 11.00 or HP-UX 11i, DESSIS fails with the error message: can't find library libcps.2, segmentation fault.

Solution
Download and install the operating system patch PHSS_26912 from HP.

DESSIS crashes when using PARDISO [90-48]
[HP-UX]
On a multiple CPU HP-UX 11.11 computer, DESSIS crashes when PARDISO is used.

Solution
Downgrade the system library patch level from:
PHSS_27700 1.0 CPSlib Cumulative Patch (OMP V2.0 for 11.11)
to:
PHSS_26913 1.0 CPSlib Cumulative Patch (OMP V2.0 for 11.11)

 DESSIS-Laser

Different results with laser gain-broadening convolution integral [90-12]
[All_archos]
The integration interval of the trapezoidal integration of the gain-broadening convolution integral has changed since Release 8.5, which results in differences that are prominent in the 1D case. The situation is aggravated if the broadening bandwidth is much smaller than the interval.

Solution
A more accurate and efficient Gaussian quadrature integration routine will replace the existing trapezoidal integration in ISE TCAD Release 9.5.

 DEVISE

Missing library on HP-UX [90-44]
[HP-UX]
DEVISE fails to start due to a missing library file.

Solution
Contact ISE Support for instructions about how to download and install the missing library.

Running DEVISE on a remote host [90-45]
[All_archos]
To run DEVISE on a remote host, certain environment variables must be set. For certain combinations of local and remote hosts, the display quality may remain unsatisfactory.

Solution
Set the following display-related environment variables. This syntax applies to csh:
 csh> setenv HOOPS_PICTURE x11/<hostname>:0.0
 csh> setenv HOOPS_SYSTEM_OPTIONS \"no message limit"
 csh> setenv DISPLAY <hostname>:0.0
Note that the placeholder <hostname> must be replaced with the name of the local host.

Missing library link on IBM [90-50]
[IBM]
DEVISE fails to start due to a missing library file.

Solution
Create the missing logic link in the directory
/$ISEROOT/tcad/$ISERELEASE/rs6000/aix5.1/lib/deviselib
with the UNIX command:
 ln -s libqt-mt.so.3.1.2 libqt-mt.a

 DIOS

DIOS does not open [90-22]
[Windows]
On Windows, DIOS requires an X server to display results in user mode. Hummingbird Exceed version 7.0 does not automatically open an X server. As a result, DIOS does not display in user mode.

Solution
To enable the display on a terminal, at every log on, click the Start button, select the Program tab, select the Hummingbird Connectivity 7.0 tab, and select the Exceed tab to the Exceed application. This starts the X server for that session. The X server must be restarted at every log on.

DIOS and PARDISO fail on IBM [90-28]
[IBM]
On IBM platforms, DIOS running with the PARDISO fails with a message such as:
 1587-117 The string for the OpenMP environment variable
 'OMP_NUM_THREADS' contains unexpected or invalid text.
 OpenMP environment variable ignored.
Solution
Set the environment variable OMP_SCHEDULE to STATIC.

Under the csh shell:
 csh> setenv OMP_SCHEDULE STATIC
Under the bash shell:
 bash> OMP_SCHEDULE=STATIC
 bash> export OMP_SCHEDULE

 DMW Scheduler

DMW Scheduler fails on Linux systems with Red Hat 9.x [90-30]
[Linux]
The DMW Scheduler does not submit jobs to Red Hat 9.x machines and DMWUmpire reports that the system is not ready. All ISE TCAD tools running on the (unsupported) Linux version Red Hat 9.x give the following warning on standard output: Incorrectly built binary which accesses errno, h_errno or _res directly. Needs to be fixed.

Other tools give this warning but, to our knowledge, no other adverse effects are accepted. The problem is caused by the basic libraries of Linux, glibc/pthread, which seem to have changed in an incompatible way in Red Hat Release 9.0.

Solution
Use Red Hat Linux 7.1. In general, ISE cannot guarantee compatibility across different Red Hat releases and other Linux releases. However, the problem is under investigation and this web page will be updated if a solution is found.

 FLOOPS

FLOOPS and PARDISO fail on IBM [90-29]
[IBM]
On IBM platforms, FLOOPS running with the PARDISO fails with a message such as:
 1587-117 The string for the OpenMP environment variable
 'OMP_NUM_THREADS' contains unexpected or invalid text.
 OpenMP environment variable ignored.
Solution
Set the environment variable OMP_SCHEDULE to STATIC.

Under the csh shell:
 csh> setenv OMP_SCHEDULE STATIC
Under the bash shell:
 bash> OMP_SCHEDULE=STATIC
 bash> export OMP_SCHEDULE

Tcl error with boron Crystal-TRIM implants [90-32]
[All_archos]
Boron Crystal-TRIM implants of more than 325 keV produce a Tcl error.

Solution
Contact ISE Support.

Differences in DIOS and DIOS models in FLOOPS [90-33]
[All_archos]
ProblemSetting DiosPairModelMode and DiosEquilibriumModelMode do not give the same model as DIOS for polysilicon and do not have the same parameters for boundary conditions. Other differences include oxidation-enhanced diffusion and arsenic clustering for the equilibrium model.

Solution
Contact ISE Support.

FLOOPS allocates too much memory [90-34]
[All_archos]
Setting the MGOALS resolution too small (depending on the structure) causes FLOOPS to allocate a significant amount of memory.

Solution
Use a larger resolution.

FLOOPS syntax checker indicates false errors [90-35]
[All_archos]
The syntax checker indicates an error for complex, legitimate Tcl code.

Solution
Use floops -n to switch off the syntax check.

Crystal-TRIM and diffusion steps result in floating exceptions [90-36]
[Compaq_Alpha]
On DEC Alpha, Crystal-TRIM and diffusion steps give floating exceptions.

Solution
Use another platform.

FLOOPS crashes intermittently [90-37]
[IBM]
On IBM RS/6000, FLOOPS occasionally crashes.

Solution
In all known cases, rerunning the simulation was successful. Alternatively, change the solver from PARDISO to UMFPACK by using the commands:
 math diffuse dim=1 umf col none !scale
 math diffuse dim=2 umf col none !scale
 math flow dim=2 umf col none !scale

FLOOPS native graphics window does not open [90-40]
[Sun]
On Sun Solaris 7 and 8, if the native graphics output window is selected and the 64-bit version of the binaries are executed, FLOOPS stops simulations with an error:
 Tecplot connection lost!
 Broken pipe
Solution
Use the FLOOPS and Tecplot-ISE interface for visualization or run the 32-bit binaries by setting the environment variable ISEBITS to 32.

Under the csh shell:
 csh> setenv ISEBITS 32
Under the bash shell:
 bash> ISEBITS=32
 bash> export ISEBITS

FLOOPS and Tecplot-ISE interface does not start [90-41]
[All_archos]
The interface does not start even though the proper command is listed in the output log file. This problem is caused by a time-out.

Solution
Prestart Tecplot-ISE in server mode before running FLOOPS with:
 > tecplot_ise -ise:ipc &

Selecting an implant table results in false error messages from syntax checker [90-43]
[All_archos]
The following command results in an error message from the syntax checker:
 implant spec=<dopant> tables=<name>
Solution
Download the FLOOPS patch 9.0.7 (or later) or use the following callback procedure in the input file:
 impLoadTables
For example, replace:
 implant spec=Boron tables=Dios
with:
 impLoadTables Boron Dios

 Interfise

Converting file from OMEGA bound format to DF-ISE boundary format [90-1]
[All_archos]
The conversion of a file from OMEGA bound format to DF-ISE boundary format, using the option -bound2bnd, does not work properly or fails.

Solution
Convert files using the ISE tool MESH:

1. Rename the file extension (for example, change test.bound to test.bnd).
2. Run MESH on this file using the command:
 mesh -n -nop test
This generates the required boundary file as test.bndNEW, which can be renamed test.bnd.

 ISExtract

Parameter extraction for Mextram 504 model does not work [90-17]
[IBM/Compaq_Alpha]
Parameter extraction for the Mextram 504 model does not work properly on IBM and Compaq Alpha platforms as they do not have certain features that ISExtract requires.

Solution
Use another platform. Linux is recommended for its speed.

 License Manager

License manager does not start [90-24]
[Windows]
On Windows, a system service for the license manager is created with lmtools, but the manager does not start.

Solution
In the lmtools 'configure services' window, specify the full path to lmgrd:
 %ISEROOT%\\tcad\\9.0\\ix86\\WinNT\\etc\\lmgrd.exe

Missing license directory after installation [90-25]
[Windows]
On Windows, the installation script does not create a license directory.

Solution
Manually create a directory called licenses under C:\\ISE_TCAD (default path). Copy the ISE license file license.dat into this directory.

License manager does not start [90-27]
[Windows]
On Windows, the license manager fails to start.

Solution
Check the security and permissions of the C:\\ISE_TCAD folder as discussed in Installation and User Setup on UNIX and Windows, Section 7 on page 6.

 LIGAMENT

Incorrect order of LIGAMENT Flow Editor plugins [90-7]
[All_archos]
The order of items in certain LIGAMENT Flow Editor menus can be platform dependent. The LIGAMENT Flow Editor loads plugins in the order that the file names are reported by the operating system. This order may differ from platform to platform.

Solution
There is no known solution.

LIGAMENT Flow Editor GUI problems [90-11]
[All_archos]
Several GUI-related problems can be experienced:
  • Move Up, Move Down do not work.
  • The Show Tip window generates an error message after deleting or moving macro calls.
  • Go To does not work.
  • Deleting a group of macros results in multiple confirmation dialog boxes being displayed.
  • Undo does not work correctly.
  • Cut, copy, paste, and delete functions in the Macro window do not support group selections.
  • Cut, copy, and paste functions do not work in the Argument window.
  • On Windows, a layout file with spaces in the file name cannot be loaded.
Solution
Request the patch LIGAMENT Flow Editor 9.0.14 from ISE Support.

 MDRAW

MDRAW does not open [90-21]
[Windows]
On Windows, MDRAW requires an X server to display results in user mode. Hummingbird Exceed version 7.0 does not automatically open an X server. As a result, MDRAW does not display in user mode.

Solution
To enable the display on a terminal, at every log on, click the Start button, select the Program tab, select the Hummingbird Connectivity 7.0 tab, and select the Exceed tab to the Exceed application. This starts the X server for that session. The X server must be restarted at every log on.

MDRAW does not open [90-23]
[Windows]
On Windows, the shell in which MDRAW is started displays 'starting mdraw' but the GUI does not open.

Solution
Create a local environment variable called DISPLAY with a suitable value. The value 127.0.0.1:0 is displayed to the local machine. This change persists across startups and shutdowns and, therefore, does not need to be repeated. Alternatively, a systems administrator can create this as a system variable.

MDRAW does not start from GENESISe [90-38]
[Windows]
On Windows, MDRAW does not start when using Edit Input > Boundary from the MDRAW icon in a GENESISe project or when GENESISe is running in interactive mode.

Solution
In GENESISe:
  1. Edit > User Preferences.
  2. In the GENESISe Preferences dialog box, in the Binaries section, open the editor entry.
  3. Set the mdraw_bound command to: mdraw -noloadCmd
  4. Open the tool entry.
  5. Set the mdraw command to: mdraw

 MEASURE

Debug message [90-16]
[All_archos]
MEASURE was compiled with debug options, which result in a message when the tool is run. It does not affect the performance of the tool.

Solution
Ignore the message regarding the license checkout. This problem will be fixed in ISE TCAD Release 9.5.

 Tecplot-ISE

Tecplot-ISE does not start [90-10]
[All_archos]
Tecplot-ISE requires OpenGL. If OpenGL is not installed, error messages are displayed that contain a reference to libGLw.so.1.

Solution
Install the OpenGL libraries. Contact your hardware vendor. If you cannot install OpenGL, consider running the older version of Tecplot-ISE (Tecplot-ISE8). Note that with ISE TCAD Release 9.0, Tecplot-ISE8 is no longer shipped.

Tecplot fails on certain Linux installations [90-39]
[All_archos]
On Linux Red Hat 9.0 or other Linux installations based on the kernel version 2.4, Tecplot fails with error messages such as:
 tecplot.shared: relocation error: libtec.so: symbol errno,
 version GLIBC_2.0 not defined in file libc.so.6 with
 link time reference
Solution
  1. Edit the file $ISEROOT/tecplot/ix86/2.2/bin/tecplot.
  2. Change the top of the file to look like:
    #!/bin/sh
    LD_ASSUME_KERNEL=2.4.1
    export LD_ASSUME_KERNEL
  3. If the problem persists, change it to:
    export LD_ASSUME_KERNEL=2
Alternatively, use Red Hat Linux 7.1. In general, ISE cannot guarantee compatibility across different Red Hat releases and other Linux releases.

Tecplot-ISE does not start [90-42]
[All_archos]
Tecplot-ISE fails with error messages such as Err: Not authorized to run Tecplot. This problem is caused by a time-out if loading the binaries, for example, over an auto-mounted file system, takes too long.

Solution
Restart Tecplot-ISE.