AMS Hit-kit 3.70 and IC 5.1.41 on 64-bit RHEL 4 - HELP?

kgl_13gr · Nov 7, 2009

Hello,

I am trying to configure the AMS Hit-Kit 3.70 to run on a x86_64 RHEL 4 machine with IC 5.1.41usr2_lnx. I also have Mentor Calibre 2003.6, loading at the start-up.

Before I get in the details, has anyone set-up AMS 3.70 to run in a 64-bit machine? Are there any environment variables or switches you can set during/after installation to say to the kit that you are on a 64-bit machine? All my suspicions go towards AMS HK not understanding that it is in a 64-bit machine.

The current situation:
Icfb seems to start fine (except for some locale problems) and I have it fully working with some other design kits, so I assume it's something with the Kit configuration.

The error I am getting is the following
sh: cannot execute binary file (mentor dir)/bin/tcksh8.3.

This I can just ignore (does calibre have to do with analog artist and spectre functionality?), but then if I do, when I create a design and run a simulation I can't plot any results. Some other windows, like, calculator, results browser and so on do not open as well.

My first suspect was unavailability of 64-bit binaries, as these software versions are quite old!

I tried to track the exact point during the start-up where the binary file error comes up and it is this point in .cdsinit:

Code:

;#
;# LOAD REQUIRED SKILL FILES AND ADD THE HIT_KIT MENU
;#
;###########################################################################
if( !CDS_QUIET then printf("Loading generic HIT-Kit skill context.\n"))

cdsVersion=substring(getVersion(t) 13)
if(substring(cdsVersion 1 1)=="4" then
  case( substring(cdsVersion 1 5)
    ("4.4.5"
       loadContext(strcat(AMS_TOP "/artist/HK_ALL/skill/ams_all_445.cxt"))
    )
    ("4.4.6"
       loadContext(strcat(AMS_TOP "/artist/HK_ALL/skill/ams_all_446.cxt"))
    )
  )
else
  case( substring(cdsVersion 1 3)
    (("5.0" "5.1")
       loadContext(strcat(AMS_TOP "/artist/HK_ALL/skill/ams_all_500.cxt"))
    )
  )
)

and more specifically the line:

Code:

loadContext(strcat(AMS_TOP "/artist/HK_ALL/skill/ams_all_500.cxt"))

Now, if I look in the corresponding directory, there is a /skill/64bit/ams_all_500.cxt. But if I change .cdsinit to load this instead, I get:

Code:

\w *WARNING* context read failure: can't read 64-bit context on 32-bit platform
\e *Error* loadContext: context I/O failed - "/export/apps/cadence/kits/ams/3.70
/artist/HK_ALL/skill/64bit/ams_all_500.cxt"
\e *Error* eval: unbound variable - menuIdPull

So it looks like the context file ams_all_500.cxt still thinks I am on a 32-bit machine...

Any ideas on this? Thank you very much in advance.

PS. My uname -m and -i are both: x86_64 and my uname -r 2.6.9-5.ELsmp
PS2. Forgot to say that the mentor software seems to HAVE 64 bit binaries (e.g. tclsh8.3_64) in the same /bin directory. It just seems that they are not called correctly.

rienneir · Nov 8, 2009

hello,

I'm needing AMS HIT-KITs. Can you help me?

This for you. this is a guide of installation of AMS HIT-KIT.

Code:

Installation of Cadence IC 5.0.33 under Linux Mandrake 9.2 DVD PowerPack using KDE interface.
Document written by The Dock, 8 March 2004, for educational purposes only.

***************************************************************
* I am not responsible of the use you will make of this file. *
* Do not copy copyrighted material since it is illegal.       *
***************************************************************

Note 1: All the path specified in this documents are ALWAYS full paths.
Note 2: The following line means: type "ls -" without the "" on the prompt:
	> ls -la
Note 3: The folder "thedock" will design your actual loggin name (i.e. your home folder)
Nota 4: The graphical environement used was KDE, and the shell was original bash.



1. Installation of Cadence IC 5.0.33 (Virtuoso/Spectre/Dracula)
---------------------------------------------------------------

-Start a console (Konsole under KDE)
-Logging as root:
	> su -
	Password:>	(enter the root password here)

-Create the InstallCadence directory in your personal home directory:
	> mkdir /home/thedock/CadenceInstall/
-Copy all the content of the Cadence DVD to the following directory: /home/thedock/CadenceInstall/
	> cp -r /mnt/cdrom/* /home/thedock/CadenceInstall/
Note: you can also use you favorite file manager under KDE to make these two previous steps.
Note: this step is necessary because the Cadence installation program is extremely sensitive to read errors on the CDROM for example.

-From now on, you will have the following directories:
	/home/thedock/CadenceInstall/VSDE33/
	/home/thedock/CadenceInstall/IC5033/
	/home/thedock/CadenceInstall/Hacker/
	/home/thedock/CadenceInstall/InstallCadence_extrafiles/
-Delete the previous Cadence folder if it exists:
	> rm -fr /Cadence
-Go into the following directory: /home/thedock/CadenceInstall/IC5033/ISR200406181244/CDROM1/
	>cd /home/thedock/CadenceInstall/IC5033/ISR200406181244/CDROM1/
-Execute the installation script from this directory (be carefull with the capitals):
	> ./SETUP.SH
-Specify path of install directory [OR type [RETURN] to exit]:
	> /Cadence
-Directory /Cadence does not exist. Create? [y/n]:
	> y
-Do you want to start softload? [y/n]:
	> y
-Warning: Software administration should not be done as root because it could cause file permissions problems while extracting software Press [Return] to proceed, q to quit :
	>		(just press RETURN to accept to continue)
-The available options are:
	> 1		(Load Available Products)
-You must now identify where the CD-ROM is mounted:
	> 1		(Local           (mounted to this machine))
-Specify the CD-ROM mount point:
	> 2		(Other)
-Type the CD-ROM mount point: [ /home/thedock/CadenceInstall/Cadence_Virtuoso_IC5033_lnx86/ISR200406181244/CDROM1 ]
	>		(just press RETURN to accept to continue: the path should be correct at this point)
-Do you want to view the README file? Please press y (yes) or n (no) :
	> y
-Follow the standard Cadence installation instructions. Press [Return] to proceed, q to quit :
	>		(just press RETURN to accept to continue)
-Where is the installation information?
	> 4		(Cadence Catalog)
-311:Unknown Product Name Removed from QSR. Press [RETURN] to continue:
	>		(just press RETURN to accept to continue)
-Go to the end of the products list by pressing the SPACE BAR
-Type your choice (a,n,p,1-3,2 5 9 ...):
	> a		(All of the above)
-Go to the end of the list of the selected products by pressing the SPACE BAR
-Are your selections correct? [y/n]
	> y
-Disk checks successful. The following products will be installed or updated. Just press SPACE BAR to continue.
-The following media is required:
					IC5033 lnx86 P/N 356-70352-0301 CDROM # 1 
					IC5033 lnx86 P/N 356-70352-0302 CDROM # 2 
					IC5033 lnx86 P/N 356-70352-0303 CDROM # 3 
					IC5033 lnx86 ISR 200406181244 CDROM # 1 
					IC5033 lnx86 ISR 200406181244 CDROM # 2 
					IC5033 lnx86 ISR 200406181244 CDROM # 3 
					Press [Return] to proceed, q to quit :
	>		(just press RETURN to accept to continue)
-Wait until the next CDROM is asked for (~7 minutes)
-Your package selections require IC5033 lnx86 P/N 356-70352-0301 CDROM # 1.
	> 4		(Change CD-ROM mount point.)
-You must now identify where the CD-ROM is mounted.
	> 1		(Local           (mounted to this machine))
-Specify the CD-ROM mount point
	> 2		(Other)
-Type the CD-ROM mount point: [ /home/thedock/CadenceInstall/IC5033/ISR200406181244/CDROM1 ]
	> /home/thedock/CadenceInstall/IC5033/Base/CDROM1
-CDROM # 2 and CDROM # 3 will be loaded automaticaly. There is nothing to do, just wait.
-Verify your installation. The available options are:
	> 2		(List Installed Products)
-Specify the operating system of the products:
	> 3		(lnx86)
-Now you can quit the Cadence IC 5.0.33 installation and begin the Aptivia installation. The available options are:
	> q		(Quit)


2. Installation of Cadence Aptivia
----------------------------------
-Before you try to install Cadence Aptivia, you must have installed all the Cadence IC 5.0.33 products.
-Go to the following directory: cd /home/thedock/CadenceInstall/VSDE33/ISR200406301301/CDROM1/
	> cd /home/thedock/CadenceInstall/VSDE33/ISR200406301301/CDROM1/
-Make sure you are also logged in as root:
	> su -
	Password:>	(enter the root password here)
-Execute the installation script from this directory (be carefull with the capitals):
	> ./SETUP.SH
-Specify path of install directory [OR type [RETURN] to exit]:
	> /Cadence/APTIVIA33
-Directory /Cadence/Aptivia does not exist. Create? [y/n]:
	> y
-Do you want to start softload? [y/n]:
	> y
-Warning: Software administration should not be done as root because it could cause file permissions problems while extracting software Press [Return] to proceed, q to quit :
	>		(just press RETURN to accept to continue)
-The available options are:
	> 1		(Load Available Products)
-You must now identify where the CD-ROM is mounted.
	> 1		(Local           (mounted to this machine))
-Specify the CD-ROM mount point
	> 2		(Other)
-Type the CD-ROM mount point: [ /home/thedock/CadenceInstall/Cadence_Aptivia33_lnx86/Base/CDROM1 ]
	>		(just press RETURN to accept to continue: the path should be correct at this point)
-Do you want to view the README file? Please press y (yes) or n (no) :
	> y

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Aptivia 3.3 (for use with IC 5.0.33, IC 5.0.32, or IC 4.4.6 MSR 11 or later)
The following environment variable must be set to the installed location
of the Aptivia software:
    setenv ACV_ROOT <path>/tools/acv
where <path> is the directory where the Aptivia software was installed.
The Aptivia bin directory must be appended to the path variable as follows:
    set path=( $path  $ACV_ROOT/bin)
Documentation is available on SourceLink. HTML versions of the manuals are
additionally installed in the following locations:
Aptivia User's Guide           $ACV_ROOT/docs/acvug
Aptivia Reference Manual       $ACV_ROOT/docs/acvrm
Aptivia Optimization User's
Guide                          $ACV_ROOT/docs/optug
DCM User's Guide               $ACV_ROOT/docs/dcmug
MATLAB Measures User's Guide   $ACV_ROOT/docs/matlabmeasug
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

-Press [Return] to proceed, q to quit :
	>		(just press RETURN to accept to continue)
-Where is the installation information?
	> 4		(Cadence Catalog)
-Type your choice (a,n,p,1-3,2 5 9 ...):
	> a		(All of the above)
-Are your selections correct? [y/n]
	> y
-The following media is required:
					VSDE33 lnx86 P/N 356-73091-0301 CDROM # 1
					VSDE33 lnx86 ISR 200406301301 CDROM # 1
	>		(just press RETURN to accept to continue)
-Your package selections require VSDE33 lnx86 P/N 356-73091-0301 CDROM # 1.
	> 4		(Change CD-ROM mount point.)
-You must now identify where the CD-ROM is mounted.
	> 1		(Local           (mounted to this machine))
-Specify the CD-ROM mount point
	> 2		(Other)
-Type the CD-ROM mount point: [ /home/thedock/CadenceInstall/VSDE33/ISR200406301301/CDROM1 ]
	> /home/thedock/CadenceInstall/VSDE33/Base/CDROM1
-Verify your installation. The available options are:
	> 2		(List Installed Products)
-Specify the operating system of the products:
	> 3		(lnx86)
-Now you can quit the Cadence Aptivia installation and begin the Hacker Script installation. The available options are:
	> q		(Quit)



3. Installation of the Hacker Script
------------------------------------
-When the installations of Cadence IC 5.0.33 and Aptivia was successfull, you can enter the Hacker Script installation.
-Make sure you are also logged in as root:
	> su -
	Password:>	(enter the root password here)
-Copy the Hacker Script and data file to the following directory /Cadence/:
	> cp /home/thedock/CadenceInstall/Hacker/*  /Cadence/IC5033/
-Go into the following directory /Cadence/IC5033
	> cd /Cadence/IC5033
-Build symbolic link to the Cadence files (au lieu d'un lien direct):
	> ln -s /Cadence/IC5033/tools.lnx86 /Cadence/IC5033/tools
	> ln -s /Cadence/VSDE33/tools.lnx86 /Cadence/VSDE33/tools
-Run the Hacker Script:
	> ./hacker hacker.script > /dev/tty	(be carefull: the second ">" in this line is not a prompt: it is the mathematical symbol)
-Normally, a few errors should occur (5~6), but a lot of files should be scanned and some of their will be modified.



4. Installing Netscape 7.1 for Cadence Documentation viewing
------------------------------------------------------------
-Since I found no solution to use Mozilla for documentation viewing in Cadence, here is the description how to install and configure Netscape for using it to view the Cadence Docimentation
-Open a Console (Konsole)
-Make sure you are also logged in as root:
	> su -
	Password:>	(enter the root password here)
-Goto the following directory /home/thedock/CadenceInstall/Netscape
	> cd /home/thedock/CadenceInstall/netscape-i686-pc-linux-gnu-sea/
-Execute the installation script
	> ./netscape-installer
-A new window will pop-up: click "Next"
-Continue by clicking "Accept"
-Select "Full" but let the default installation directory (/usr/local/netscape)
-Click "Next" to continue
-Click "Install" to make the Netscape installation
-Click "OK" when installation has completed: now Netscape is installed into /usr/local/netscape/

-Go to the directory in which the RealPlayer RMP is located:
	> cd /home/thedock/CadenceInstall/RealPlayer
-Launch the installation of the RealPlayer RPM:
	> rpm -i rp8.linux20.libc6.i386.cs2.rpm --nodeps --force
-A new window will open. Click on "Finished"
-Click on "OK"
-Enter you Email, deselect "inform me on updates and events" and click "Next"
-Select you connection speed and click "Finished": RealPlayer is now installed



5. Configuration of the Environement Variables
----------------------------------------------
-After you applied the Hacker Script successfully, you must configure the environement variables
-Now goto your following directory: /home/thedock/
-Edit the .bashrc file: /home/thedock/.bashrc (for bash users only, the others will not be described, but take a look at the end if you are using ksh or compatible)
-Add the environement that follows:
	export ACV_ROOT="/Cadence/VSDE33/tools/acv"
	export LANG C
	PATH=$PATH:/usr/local/netscape:/Cadence:/Cadence/IC5033:/Cadence/IC5033/tools:/Cadence/IC5033/tools/dfII:/Cadence/IC5033/tools/dfII/bin:/Cadence/IC5033/tools/bin:$ACV_ROOT/bin
-If you do not use bash (csh for example), you will need to use following syntax:
	setenv ACV_ROOT /Cadence/VSDE33/tools/acv
	setenv LANG C
	set path = ($path /usr/local/netscape /Cadence /Cadence/tools /Cadence/tools/dfII /Cadence/tools/dfII/bin /Cadence/tools/bin $ACV_ROOT/bin)
-The variables for other shells can also be found in the following directory: /home/thedock/CadenceInstall/InstallCadence_extrafiles/envvariables)
-Reboot you computer
-Open a Console (Konsole for example)
-To start Cadence, type:
	> icfb &
-And now, Cadence will start!
-To start the documentation, type:
	> cdsdoc &

6. Installation of the AMS HitKit 3.60
--------------------------------------
-Make sure you are also logged in as root:
	> su -
	Password:>	(enter the root password here)
-Create an ams_root directory:
	> mkdir /HitKit_3.60
	> mkdir /HitKit_3.60/License
-Put your AMS license file amslmd.lic in the following directory:
	> cp /home/thedock/CadenceInstall/AMS_HitKit_3.60/amslmd.lic /HitKit_3.60/License/
-Once the CD-ROM is mounted start the installation by entering the command:
	> cd /home/thedock/CadenceInstall/AMS_HitKit_3.60/
	> ./ams_install.linux
-Prompt asks you to enter an ams_root directory:
	/HitKit_3.60
-Prompt asks you to enter the path to the license file:
	/HitKit_3.60/License/amslmd.lic
-All files specified in the license file will now be installed in entered ams_root directory
-File permissions of executables will be checked
-The installed libraries will be configured by the script INSTALL_AMS_CDS
-Setup the environement variables in the /home/thedock/.bashrc file:
	export AMS_DIR="/HitKit_3.60"
	export CDSDIR="/Cadence"
	export CDS_Netlisting_Mode="Analog"
	export LM_LICENSE_FILE="/HitKit_3.60/License/amslmd.lic"
	(or	setenv AMS_DIR /HitKit_3.60
		setenv CDSDIR /Cadence
		setenv CDS_Netlisting_Mode Analog
		setenv LM_LICENSE_FILE /HitKit_3.60/License/amslmd.lic
	when using Solaris in the .cshrc file)
-Add the following search path in your path variable (also in .bashrc or .cshrc file):
	set path = $AMS_DIR/artist/bin
-Goto the installation path:
	> cd /HitKit_3.60/Flexlm/i686lx2
-Start license server (if you get an error message, restart entirely Linux):
	> ./lmgrd -c /HitKit_3.60/License/amslmd.lic
	> ./lmgrd -l /HitKit_3.60/License/amslmd.log
-Check the license server status:
	> ./lmstat -c /HitKit_3.60/License/amslmd.lic

6. Compilation of a new Mandrake Kernel
---------------------------------------
-Open a Console (Konsole)
-Make sure you are also logged in as root:
	> su -
	Password:>	(enter the root password here)
-Goto the following directory /usr/src/linux
	> cd /usr/src/linux
-Clean the old sources
	> make mrproper
-Start the graphical kernel configuration interface
	> make xconfig
-Configure the wanted options and click on "Save changes and exit"
-Compile the kernel by typing the following command in the console:
	> make dep clean bzImage modules modules_install install


7. Installation of Matlab 6.5
-----------------------------

Start a console (Konsole under KDE)
-Logging as root:
	> su -
	Password:>	(enter the root password here)
-Go into the following directory: /home/thedock/CadenceInstall/Matlab_6.5/
	> cd /home/thedock/CadenceInstall/Matlab_6.5/
-Make the directory in which you will install Matlab 6.5: /usr/local/matlab6p5/
	> mkdir /usr/local/matlab6p5/
-Copy the license file to that directory:
	> cp license.dat /usr/local/matlab6p5
Note: The SERVER and DAEMON lines in the license.dat file have been removed since they will be generated automaticaly by the installer.

-Unpack the installation script:
	> tar xvf boot.ftp
-Run the install file as root to start the installer:
	> ./install
-A window will pop-up: "MATLAB Installation":
	Click on the OK button to start the installation.
-Another window will pop-up: "License Agreement":
	Click on the "Yes" button to continue.
-MATLAB root directory location: this means Matlab installation directory: enter the following location:
	/usr/local/matlab6p5
	Click the "OK" button to validate.
-The "License File" dialog box will open:
	Simply click on the "OK" button to continue.
-The "Installation Options" dialog box will open:
	Choose Platform Linux, and add all items to the "Item to install:" column if not so. Normaly, it should be preselected.
-The "Installation Data" dialog box will open:
	Check the "Create symbolic links to MATLAB and mex scripts".
	The "Specify directory to put links in" should be /usr/local/bin
	The MATLAB License No. should be 52516.
	And click the "OK" button to install MATLAB.
-The "Begin Installation" dialog box will open:
	Click on the "OK" button to really begin the installation.
-The "Installation Complete" dialog box will open:
	Click on the "Exit" button to finish the installation. Now you need to set up the license server.
-Loggout the root user (license manager will not start if you try to start it as root):
	> exit
-If you choose to run FleXlm manually:
	> /usr/local/matlab6p5/etc/lmstart
-To start Matlab, type:
	> matlab &
-And now, Matlab will start!

**broken link removed**

hock · Nov 9, 2009

Linux 64 bit support came in IC5141 USR1 (for Opteron), and IC5141 USR1a
(for Intel EMT64). All ISRs since then support 64 bit on both platforms.

please go through my post on for installing it on rhel5 and above. i have tested it for usr5 and usr6 and the installation is flawless. it is not tarball installation not is a downgrade mode installation. this will help you in insuring that you have a full working ic5141 on rhel5 64 bit.
even after this the default mode of ic5141 is 32 bit only and you will have to use CDS_AUTO_64BIT environment variable in your ic cshrc file.

hope this will be useful.
once you are sure that you are running it in 64bit mode let me know. i will try to help you setting up AMS hitkit.

hock

Running Layout Editor in 64-Bit

To run 64-bit software,

1.

Install the 64-bit version of software to the same location as your 32-bit software. Ask your Cadence software administrator to install it, if necessary.
2.

Verify that all required patches are installed by running the System Configuration Checking Tool script, checkSysConf. This script is in your local installation of Cadence software, at the following location:

your_install_dir/tools/bin/checkSysConf IC500

IC500 is a parameter expected by the script.

The System Configuration Checking Tool is also available on the SourceLinkSM online customer support system.

All required patches must be installed for the 64-bit executables to work correctly.

3.

Set the environment variable CDS_AUTO_64BIT {ALL|NONE|"list"|INCLUDE: "list"|EXCLUDE:"list"}to select 32-bit or 64-bit executables.

ALL

Invokes all applications as 64-bit, where available. The list of executables available are in:
your_install_dir/tools/bin/64bit

NONE

Invokes all applications as 32-bit.

"list"

Invokes only the executables included in the list, if available, as 64-bit. list is a list of case-sensitive executable names delimited by comma(,), semi-colon(

, or colon

).

"INCLUDE:list"

Invokes all applications in the list as 64-bit, where available.

"EXCLUDE:list"

Invokes all applications as 64-bit, where possible, except the applications in the list.

Examples:

setenv CDS_AUTO_64BIT "pipo,layout.exe"

setenv CDS_AUTO_64BIT "EXCLUDE:si"

If you do not set this environment variable then the 32-bit executable is invoked by default.

All 64-bit executables are controlled by a wrapper executable. The wrapper invokes the 32-bit or 64-bit executables depending on how the CDS_AUTO_64BIT environment variable is set, or whether the 64-bit executable is installed. The wrapper also adjusts the paths before invoking the 32-bit or 64-bit executables.

4.

Launch the executables through the wrapper only.

Example:

your_install_dir/tools/dfII/bin/layout

The wrapper you use to launch the executables is in your_install_dir/tools/dfII/bin.

The 32-bit executables are found in your_install_dir/tools/dfII/bin/32bit.

The 64-bit executables are found in your_install_dir/tools/dfII/bin/64bit.

Do not launch the executables directly from your_install_dir/tools/dfII/bin/64bit or from your_install_dir/tools/dfII/bin/32bit directory.

kgl_13gr · Nov 9, 2009

Thanks for the replies.

@rienneir: I can't do anything about you I m afraid.
@hock:

I have checked your post before posting here. It is indeed very well written but it couldn't solve my problem.

Just in case, the printed information when icfb starts read as follows:

\o Program: @(#)$CDS: icfb.exe version 5.1.0 06/30/2005 00:12 (cicln03) $
\o Hierarchy: /export/apps/cadence/ic/5.1.41usr2_lnx/tools.lnx86/dfII/
\o Sub version: sub-version 5.10.41_USR2.19.52 (32-bit addresses)

Again, I don't think the problem lies with IC... I base that on the fact that I can run it well with hit-kits of other processes. The problem seems to be that the AMS Hit-Kit doesn't realize it is in a 64-bit environment (as amd_cds doesn't automatically set-up .cdsinit to loat the 64-bit ams_500_all.cxt context file and even when I force it to read it, it protests that it can't in a 32-bit environment).

I have tried fiddling a little bit with the ams_architecture script, that seems to provide the platform information to the ams tools, and doesn't seem to output 64bit in case of Linux (it does in case of SunOS), but I couldn't get anything out of it...

Let me know if you have any better idea.

Once again, thanks a lot for the help.

hock · Nov 10, 2009

\o Sub version: sub-version 5.10.41_USR2.19.52 (32-bit addresses)

this is the proof that you have not Set the environment variable CDS_AUTO_64BIT .

R00KIE · Nov 10, 2009

I'm not so sure it is supposed to say 64bit ....
I did install the 64bit executables and I do have CDS_AUTO_64BIT set to all and other programs do automatically start as 64bit but not icfb, also there is no icfb in the 64bit directory.

\o Program: @(#)$CDS: icfb.exe version 5.1.0 08/19/2008 01:12 (cicln04) $
\o Sub version: sub-version 5.10.41.500.5.122 (32-bit addresses)

$ env | grep 64BIT
CDS_AUTO_64BIT=All

$ spectre -V
@(#)$CDS: spectre version 7.0.1 64bit 08/25/2008 00:11 (usimamd64-8) $

The problem must be with the ams hitkit.

Welcome to EDAboard.com

AMS Hit-kit 3.70 and IC 5.1.41 on 64-bit RHEL 4 - HELP?

kgl_13gr

Member level 5

rienneir

Newbie level 5

hock

Advanced Member level 2

kgl_13gr

Member level 5

hock

Advanced Member level 2

R00KIE

Full Member level 2

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Connect with us

Online statistics

Forum statistics