Known Problems and Solutions in HSPICE/SPICE Interface

This document describes the known issues with HSPICE/SPICE Interface and suggests the workarounds for these issues. Each issue is identified by a Cadence Change Request (CCR) number.

Related Topics

Introduction to HSPICE/SPICE Interface

CCR 491344 The OSS HSPICE script should not check for existence of hspice.exe

Description: The 276 interface HSPICE script still checks for the existence of the hspice.exe file in the HSPICE installdir, but this file is no longer provided by Meta.

Solution: Create a link in <installdir>/bin/hspice.exe to point to <installdir>/bin/hspice.

CCR 491338 si hardcoded to look for awk in /bin

Description: The “si” is hardcoded to look for “awk” at /bin.

Solution: Requires a link from /usr/bin/awk to /bin/awk on hppa and ibmrs.

CCR 54032 Remote HSPICE fails if key commands are aliased

Description: If the user aliases commands used by the remote HSPICE script to nonstandard UNIX, remote HSPICE fails. For example, if “rm” is an alias to “rm -i,” the script fails.

Solution: Change the script to use the full path to the command as in /usr/bin/rm or escape the command with “/,” e.g., /rm.