Home

Installation Guide

Contents

1. 22 31 6 Running the Installation Script 000055 31 7 Setting Up Your Search Path 0 000 000 0 eee 31 9 Checking Your Search Path 0 0 31 9 Modifying Your Search Path 00 0 0005 31 10 Modifying Your Path in the C shell 31 10 Modifying Your Path in the Bourne or Korn Shell 31 10 Setting the User Environment to Find the TCAD License 31 11 Running TCAD Products acd at aeaaeae 31 12 Using Graphics Devices 0000000 0c eee 31 14 Graphics Device Hierarchy 0 00 0c ee eee 31 14 Specifying a Graphics Device 00000 cece eee 31 15 S n andtMaplot i scaxccadvas ce soho bruter idei 31 18 WFOUDISSNOOUNG cs 2 Arad eet ee ees E ue ee ae 31 19 TOAD Utes 4 caeaverccee eee uncncaeee eee eee eens 31 21 TCAD utility Directory 0 000000 00 eee eee 31 21 Executing the TCAD Utilities 2 00000 aes 31 23 Appendix A Installing VirSim version 4 3 Installing the Software 2 2 2 2 ee A 2 Setting Up VirSim for Each User 00 0c cece eee A 3 Setting the SNPSLMD_LICENSE_FILE or LM_LICENSE_FILE Environment Variable ic sci ccces eee ee PERERA Oh ee Ex A 4 Verifying the VirSim Installation 0000 02 eee eee A 5 CUSIOME SUPPO arise eier a oe eee teehee A 5 Index XV xvi Preface This preface includes the following sections e What s New
2. 0000e eee Installing NanoSim version V 2003 12 Installing the Software 0 000 c eee Setting Up NanoSim for Each User anaana anaana eee Verifying the NanoSim Installation 000 00a aee Installing PathMill version V 2003 12 Installing the Software ental esed es eee ies Oe GS ea Setting Up PathMill for Each User 0 00000 a ee Verifying the PathMill Installation 0 220005 Installing PowerMill version U 2003 03 Installing the Software 2 2 0 ee Setting Up PowerMill for Each User 0000005s Verifying the PowerMill Installation 05 vii 14 Installing PrimePower version V 2003 12 Installing the Software 2 2 0 000 ee Setting Up PrimePower for Each User 00055 Verifying the PrimePower Installation 5 15 Installing PrimeTime version V 2003 12 Installing the Software 2 2 2 2 0 2 ee Setting Up PrimeTime for Each User 00000 Verifying the PrimeTime Installation 04 16 Installing RailMill version U 2003 03 Installing the Software aaas aaaea Setting Up RailMill for Each User 222000005 Verifying the RailMill Installation 0000005 17 Installing System Studio version V 2003 12 Installing the Software 2 2 2 00 ee Setting Up System Studio for Each User
3. 20 4 Setting the SNPSLMD_LICENSE_FILE or LM_LICENSE_FILE Environment Variable 20 5 Verifying the VCS and VCSi Installation 20 6 Customer Support 5b RARE E eee eee SERRE SS 21 Installing Vera version 6 2 0 Downloading and Installing the Software Setting the Environment Variables 0000 aes Setting the VERA_HOME Environment Variable Setting the SNPSLMD_LICENSE_FILE or LM LICENSE _ FILE Environment Variable CUSIOMeMSUDDON 24 Acce maa S RRA 22 Installing VHDL Simulation Scirocco version 2002 12 2 Installing the Sottwarey sc ce esieetsaee sso eeeseeeeeneees Setting the Environment Variables 0000eaee Setting the SYNOPSYS_SIM Environment Variable Setting the SNPSLMD_LICENSE_FILE or LM LICENSE _ FILE Environment Variable Setting Up VHDL Simulation Scirocco for Each User Verifying the VHDL Simulation Scirocco Installation 23 Installing Synopsys Online Documentation version V 2003 12 ADOUPSOED CC to rc thew oA ae aig ge hak eet ste iv ied Acquiring and Installing the Acrobat Reader Software Downloading and Installing Acrobat Reader from the Web 5 004 taseice LOM ees tae kollel ale Lite Verifying Your Adobe Acrobat Software 05 Checking the Version Number 0000000 eee eee 23 4 Checking for the Search
4. PATH install_directory platform ns utilities cosmos ai_bin PATH export Path MANPATH install_directory doc ns man SMANPATH export MANPATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Installing NanoSim version V 2003 12 11 3 Verifying the NanoSim Installation To verify the NanoSim installation 1 Make sure you are in a directory where you have read write privileges ed HOME Invoke the tool by entering the following command nanosim If you see information about the product version production date and copyright the installation was successful Run the NanoSim GUI on each installed platform by entering the following command nanosimgui 4 Exit the GUI by choosing File gt Exit in any GUI window Installing NanoSim version V 2003 12 11 4 12 Installing PathMill version V 2003 12 This chapter contains the following sections Installing the Software Setting Up PathMill for Each User Verifying the PathMill Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 Define the SYNOPSYS environment variable see Defining the SYNOPSYS Environment Variable on page 1 19 Have your license server running and have the appropriate license keys installe
5. 5 9 x 5 45 8 MB of available swap space Accessing Memory Beyond 2 GB With 32 Bit Synopsys Tools In general UNIX based systems support a maximum memory of 2 GB for 32 bit processes However the following Synopsys tools can extend memory beyond 2 GB e Design Compiler e DFT Compiler e Floorplan Compiler e Floorplan Manager e Formality e HDL Compiler Presto Verilog e NanoSim e Physical Compiler e Power Compiler e PowerMill e PrimePower e PrimeTime e RailMill e TimeMill e VCS Preparing for Installation 1 13 e Vera e VHDL Simulation Scirocco Note Available memory is space not used by the OS the windowing system or other applications To access memory beyond 2 GB 1 Doone of the following depending on the platform you are using For HP UX Make sure your server has HP UX 11 0 or later loaded For Solaris Make sure your server has Solaris 8 or later loaded 2 Make sure your server has at least 4 GB of memory physical and swap space available Note Physical memory equals data size plus stack size and stack size is used before data size Therefore setting stack size toa large value causes problems for designs that need to go over 2 GB If you set the stack size too high you cannot get enough memory for your data To check the settings use the Limit command at the system prompt For more information see Memory on page 24 2 3 Make sure the system you are us
6. For G SnelWsers cse2 eck teat ee ee a a eee cee sees For Bourne Shell Users 0 0 0 0 0 0 cc es VHDL Simulation aaan anaa nde ke eed ee ee eee he Verifying the System Studio Installation Troubleshooting Startup Problems 00000 eee Key File Problems 12 due desueeeeee soe bas ewn 228 44 ee viii Insufficient Interprocess Communication IPC SEMADNOlES esate shah e heey Rime eee hee eae 17 8 18 Installing TetraMAX version V 2003 12 Installing TetraMAX 2 0 004644 9S404 bb be whee eee bees 18 2 License Key Requirements 022220 0 eees 18 2 64 Bit Mode on HP UX and Solaris Platforms 18 3 Stand Alone Installation 2 2 2 00 000 c eee ee 18 3 Overlay Installation wu va neat ee devia DY Ree Oe Res 18 4 Optional Installation of IddQTest 0000 0 eee eee 18 5 Setting Up the User Environment 2 200005 18 6 Verifying the TetraMAX Installation 005 18 7 19 Installing TimeMill version U 2003 03 Installing the Software 1223550024 e sheared ae eee ee ROS 19 2 Setting Up TimeMill for Each User 200005 19 2 Verifying the TimeMill Installation 005 19 4 20 Installing VCS version 7 0 2 Installing the Software ccs ee weve tbe am eee eee ed Re ead 20 2 Setting the Environment Variables 200005 20 4 Setting the VCS_HOME Environment Variable
7. G graphical user interface Design Analyzer setting up systemwide defaults 3 7 Design Vision 3 8 Physical Compiler 3 8 VirSim 20 2 22 2 A 1 H Hercules environment variables setting 27 5 installing 27 3 setting up for new user 27 7 verifying installation 27 8 HSPICE AvanWaves configuring 28 5 installing 28 3 running 28 12 setting up for each user 28 6 verifying 28 7 configuring 28 5 documentation 28 14 hspice ini file 28 13 installing on UNIX or Linux 28 3 on Windows 28 9 sentinel system drivers 28 10 media 28 2 multiple dongles troubleshooting 28 11 running 28 11 setting up for new user 28 6 supported platforms 28 2 verifying installation 28 7 installation CD 2 9 electronic software transfer 2 6 multiple platform 1 5 prerequisites creating root directory 1 18 setting environment variable 1 19 scripts Synopsys media for PrimeTime 2 13 Synopsys media for synthesis tools 2 10 J JupiterXT installing 25 1 L licensing see Synopsys Common Licensing linking executable files using makefile 3 15 using vconfig 3 14 Linux shared object file problem 1 4 M memory beyond 2 GB 1 13 data size limit 24 2 errors 24 4 physical 1 12 requirements 1 11 swap space 1 12 1 13 24 4 troubleshooting 24 2 multiple platform installation 1 5 N NanoSim installing 11 2 platform keyword 1 6 product ID 1 6 setting up for new user 11 2 verifying installation 11 4 O online documentation FPGA Comp
8. Table 1 3 Disk Space Requirements Continued Synopsys product Required size in MB approximate TetraMAX overlay Platform independent 9 Per platform 40 TetraMAX stand alone Platform independent 9 Per platform 112 TimeMill Platform independent 50 Per platform 300 sparcOS5 450 VCS Per platform 400 Vera Per platform 400 VHDL Simulation Scirocco Platform independent 320 Per platform 500 Memory Requirements The UNIX kernel defines hard per process limits on the maximum amount of memory that can be used and the 1imit command creates soft limits If ignored these limits can cause processes jobs to fail even when sufficient memory is available For more information see Memory on page 24 2 Preparing for Installation 1 10 Table 1 4 lists the general guidelines for the minimum amount of physical memory and swap space virtual memory required to run Synopsys tools Table 1 4 Minimum Memory Requirements Tool Physical memory MB Swap space MB AMPS 256 512 Recommended 1GB Recommended 2GB Arcadia 256 512 Cadabra 1 GB 256 Floorplan Compiler 256 512 Formality 256 512 FPGA Compiler II 64 140 NanoSim 256 512 Recommended 1GB Recommended 2GB PathMill 256 512 Recommended 1GB Recommended 2GB PowerMill 256 512 Recommended 1GB Recommended 2GB PrimePower 128 256 PrimeTime 150 256 RailMill 256 512 Synthesis tools 128 256 System Studio 256 512 TetraMAX 256 512 TimeMill 256
9. CCSS_KEYS Specifies the complete file name of the license file If CCSS_KEYS is not set the tool searches for other license keys in the following order SNPSLMD_LICENSE_FILE LM_LICENSE_FILE For C Shell Users To use the C shell to set up a new System Studio tool user 1 Add the System Studio executable directory to the PATH environment variable Add the following line to the cshrc file setenv SYNOPSYS_CCSS ccss_home platform ccss setenv CCSS SIM DIR ccss_sim_dir set path SYNOPSYS_CCSS bin path Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Installing System Studio version V 2003 12 17 3 Note You can define CCSS_SIM_DIR but if it is not set the GUI provides a reasonable default 2 Point to your license key file by adding one of the following lines to your cshrc file setenv CCSS_KEYS path to synopsys lic 3 Ifthe paths to the C compiler debugger and make command are not already included in your cshrc file add the following line to your cshrec file set path compiler_home bin make_home bin path 4 To source the CCSS setup file add the following line to your cshre file source SSYNOPSYS_CCSS gnupackages source_me csh 5 Make these changes effective by logging out and logging in again or by entering the following command o source cshre For Bourne Shell Users To use the Bourne Korn or
10. If you don t source the CSHRC_ platform file copy the above line and set the path from that file If you are using the Bourne Korn or Bash shell add the following line to the profile or kshrc file PATH install_directory platform rm bin PATH export PATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Verifying the RailMill Installation To verify the RailMill installation 1 Make sure you are in a directory where you have read write privileges ed HOME Invoke the tool by entering the following command rvrailmill If you see information about the product version production date and copyright the installation was successful Installing RailMill version U 2003 03 16 3 3 Run the RailMill GUI on each installed platform by entering the following command SYNOPSYS platform rm bin chipviewer 4 Exitthe GUI by choosing File gt Exit and clicking Yes in the dialog box Installing RailMill version U 2003 03 16 4 1 InstallingSystemStudio versionV 2003 12 This chapter contains the following sections Installing the Software Setting Up System Studio for Each User Verifying the System Studio Installation Troubleshooting Startup Problems To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Direc
11. No option is required If you want to configure HSPICE select Configure HSPICE The configuration options are versions file meta cfg file hspice ini file and setup buttons If you do not select these options the default settings apply After selecting your options click the Configure button The configuration log is shown in the middle of the dialog box Click Exit when the configuration has finished Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 5 Setting Up HSPICE and AvanWaves for Each User To set up a new tool user e Enter the path information e Setup a license variable that points to the license server e Source the cshrc meta file or use a dot with the kshrc meta file where is a Bourne or Korn shell commana Add the following information to the cshrc kshrc or an HSPICE source file 1 Addthe HSPICE and AvanWaves executable files to your search path If you are using the C shell enter set path installation_directory bin path lf you are using the Bourne or Korn shell enter PATH installation_directory bin SPATH 2 Set one of the following licensing variables LM _LICENSE_FILE or AVANTD_LICENSE_FILE For example If you are using the C shell add the following line setenv LM _LICENSE_FILE port hostname Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 6 lf you are using the Bourne or Korn shel
12. cc ee 26 2 Setting Up Astro Rail fora New User 2005 26 4 Verifying the Astro Rail Installation 00 26 5 Installing Hercules version V 2003 12 Media Availability and Supported Platforms 27 2 Installing the SOMWANCy 1 0 ceeceoocaneers Cw eee heen een Bees 27 3 Setting the Environment Variables 000 0c aee 27 5 Setting the HERCULES HOME_DIR Environment Variable 000 cece eee 27 5 Setting the LM_LICENSE_FILE Environment Variable 27 6 Setting Up Hercules for Each User 0 0 0c ee eaee 27 7 Verifying the Hercules Installation 0 00005 27 8 Installing HSPICE version U 2003 09 on UNIX or Windows Platforms Media Availability and Supported Platforms 28 2 Installing the Software on UNIX or Linux Platforms 28 3 Configuring HSPICE and AvanWaves for UNIX and Linux 28 5 Setting Up HSPICE and AvanWaves for Each User 28 6 Verifying the HSPICE and AvanWaves Installation 28 7 Verifying the HSPICE Installation 5 28 8 Verifying the AvanWaves Installation 28 9 Installing the Software on Windows Platforms 28 9 Installing With Windows Explorer 22005 28 10 Installing With Windows DOS Shell 28 10 Installing the Sentinel System Drivers 28 10 Running HSPICE on
13. usr synopsys pts_V 2003 12 directory for the first time Downloading and Installing the Software 2 13 Install Platform Independent Package for pts y n yl y Select platform s to install sparcOS5 for Solaris 8 9 sparc64 for Solaris 8 9 64 bit Enter the list of platform s to install sparcOS5 sparcOS Platform s selected sparcos5 Here is your final selection for installing Synopsys Tools VERSION V 2003 12 PRODUCTS pts PLATFORMS sparcos5 Syn Pla Dis Dis If all opsys Media Directory from cdrom Synopsys Install Directory to usr synopsys pts_V 2003 12 tform Independent Package s for pts k space required 290 MB k space available 10063 MB the information is correct continue with the installation Install Startin INSTALL uncompr INSTALL y n yl y g Installation Please do not interrupt ING pts product platform_independent package V 2003 12 version ess lt pts taz cd usr synopsys pts_V 2003 12 tar xvfp sparcos5 ING pts product sparcos5 package V 2003 12 version uncompress lt sparcos5 pts taz cd usr synopsys pts_V 2003 12 tar xvfp Install ing PrimeTime Synopsy Synopsy Synopsy 000 s Site Identification Number appears on the upper right corner of your s License Key Certificate s Site Identification Number Hit return for 000 Downloading and Instal
14. DC Ultra DC Ultra Plus Design Advisor Design Analyzer Design Vision DesignerHDL DesignTime DFM Workbench DFT Compiler Direct RTL Direct Silicon Access DW8051 DWPCI Dynamic Model Switcher Dynamic Macromodeling ECL Compiler ECO Compiler EDAnavigator Encore Encore PQ Evaccess ExpressModel Floorplan Manager Formal Model Checker FoundryModel FPGA Compiler Il FPGA Express Frame Compiler Galaxy Gatran HDL Advisor HDL Compiler Hercules Hercules Explorer Hercules ll Hierarchical Optimization Technology High Performance Option HotPlace HSPICE Link iN Tandem Integrator Interactive Waveform Viewer Jupiter Jupiter DP JupiterXT JupiterxT ASIC JVXtreme Liberty Libra Passport Libra Visa Library Compiler LRC Magellan Mars Mars Rail Mars Xtalk Medici Metacapture Metacircuit Metamanager Metamixsim Milkyway ModelSource Module Compiler MS 3200 MS 3400 NanoSim Nova Product Family Nova ExploreRTL Nova Trans Nova VeriLint Nova VHDLIlint OpenVera Optimum Silicon Orion_ec Parasitic View Passport Planet Planet PL Planet RTL Polaris Polaris CBS Polaris MT Power Compiler PowerCODE PowerGate ProFPGA Progen Prospector Proteus OPC Protocol Compiler PSMGen Raphael NES RoadRunner RTL Analyzer Saturn ScanBand Schematic Compiler Scirocco Scirocco i Shadow Debugger Silicon Blueprint Silicon Early Access SinglePass SoC Smart Extraction SmartLicense SmartModel Library Softwire Source Level Des
15. Installing the Software 2 0 0 0 ee Setting the Environment Variables 00000 aes Setting the CADABRAHOME Environment Variable Setting the LM_LICENSE FILE Environment Variable Verifying the Cadabra Installation 0 0c ee eaee Customer SUDNON oncees obi hee Rete cee eee wee awee SEES Installing Floorplan Compiler version V 2003 12 Installing the Software gawk iwst eh mate bate Saks hordigis Setting Up Floorplan Compiler for Each User Configuring the Browser for Floorplan Compiler Online Help Verifying the Floorplan Compiler Installation Installing Formality version V 2003 12 Installing the Software a na oditee de epee deere wees ere Setting Up Formality for Each User 00000 Verifying the Formality Installation 2 0005 Installing FPGA Compiler Il version T 2003 09 FC3 8 on UNIX Platforms Product SUDPOM orhe sree d sk Pade EEEE Ea ee OS oR Doe ma ete System Requirements a na nnana aaea 10 11 12 13 Installing the Software 2 2 ee Enabling Online Document Readers 0000 eee Installing FPGA Compiler Il version T 2003 09 FC3 8 on Windows Platforms Product SUDO ON sess rerep eii Cee oe ks eee ee ee System Requirements for Windows 00000 ee aes Installing FPGA Compiler ll 0 000 cee eee Enabling Online Document Readers
16. Replace platform with one of the following hp32 or sparcOS5 Installing Power Compiler VPOWER VPOWER is the Power Compiler interface to VCS the Cadence Verilog XL and NC Verilog simulators and the MTI Verilog simulator VPOWER contains user tasks that allow you to monitor toggle activity during simulation and to output the information in a form readable by Power Compiler To use VPOWER link the user tasks to the executable file of your simulator The following sections describe the steps for static linking VPOWER with Verilog XL and VCS simulators only For information about linking VPOWER with other simulators see the Power Compiler User Guide Verilog XL Simulator The following procedure describes how to link VPOWER to a version of the Verilog XL simulator that contains the standard features you normally use at your site and includes the toggle count utilities needed for Power Compiler Installing the Synopsys Synthesis Tools version V 2003 12 3 11 Note You must perform this installation on a machine that has access to your Verilog XL simulator vendor distribution Consult your Verilog system administrator to obtain the following information before beginning the VPOWER installation e The directory path to your Verilog o a and h files e The directory location of your central Verilog distribution for obtaining a current site copy of the veriuser c file This installation requires modification of your veriuser
17. line to the profile or kshrc file PATH SSYNOPSYS platform amps bin SPATH export PATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Installing AMPS version U 2003 03 4 2 Verifying the AMPS Installation To verify the AMPS installation 1 Make sure you are in a directory where you have read write privileges ed HOME 2 Invoke the tool by entering the following command SYNOPSYS platform amps bin amps Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 If you see information about the product version production date and copyright the installation was successful Installing AMPS version U 2003 03 4 3 Installing AMPS version U 2003 03 4 4 Installing Arcadia version U 2003 03 This chapter contains the following sections Installing the Software Setting Up Arcadia for Each User Verifying the Arcadia Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 5 1 Installing the Software To download and install Arcadia from the Web or by FTP follow the procedures described in Downloading
18. system from starting Installing System Studio version V 2003 12 17 8 18 Installing TetraMAX version V 2003 12 This chapter contains the following sections e Installing TetraMAX e Setting Up the User Environment e Verifying the TetraMAX Installation If you are installing TetraMAX stand alone to ensure a successful installation complete the following procedures before beginning the installation process e Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 e Define the SYNOPSYS environment variable see Defining the SYNOPSYS Environment Variable on page 1 19 18 1 e Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 Installing TetraMAX This section describes Synopsys license key requirements and the two types of installation for TetraMAX ATPG and TetraMAX IddQTest version V 2003 12 e Stand alone Install TetraMAX stand alone in its own directory e Overlay Install TetraMAX overlay in the same directory as the V 2003 12 synthesis tools License Key Requirements TetraMAX version V 2003 12 uses the Synopsys Common Licensing SCL system For information on installing SCL see Acquiring a License on page 1 15 Note Optional features such as Diagnosis lddQTest PatternMap and transition delay fault ATPG each require a separate license For specific information on th
19. version V 2003 12 3 9 You can open either Help system from within its respective GUI tool or open it stand alone in Netscape Navigator Installing Optional Tools The synthesis media installation script automatically installs most of the synthesis tools However the following tools require manual setup or installations e Synopsys Integrator for Falcon Framework e Power Compiler VPOWER e SoCBIST Installing Synopsys Integrator for Falcon Framework To complete the setup for the Synopsys Integrator for Falcon Framework product set the SYNOPSYS_IFF_ROOT environment variable to point to the Synopsys integrator directory When asked for the Falcon Framework version enter e Cif you selected the sf3 product from the installation script e Dif you selected the sf4 product from the installation script Note You can install Falcon Framework version C or D but not both Version C is supported only on the Solaris 8 sparcOS5 operating system version D is supported on both HP UX 11 0 or 11i hp32 and Solaris 8 sparcOS5 operating systems Installing the Synopsys Synthesis Tools version V 2003 12 3 10 If you are using the C shell add the following line to the cshrc file setenv SYNOPSYS_IFF_ROOT S SYNOPSYS platform syn interfaces mentorC If you are using the Bourne Korn or Bash shell add the following lines to the profile file SYNOPSYS_IFF_ROOT SSYNOPSYS platform syn interfaces mentorC export SYNOPSYS_IFF_ROOT
20. 2003 09 on UNIX or Windows Platforms 28 12 You can add different HSPICE executable file full paths to subsequent lines in the versions txt file The second column contains comments as a version reminder and is ignored by the HSPUI utility After invoking HSPUI you can select the HSPICE version in the combo box of the HSPUI window HSPICE will run according to the path selected in the combo box The following executable files are provided on the HSPICE AvanWaves and Utility disks EXE File Sinstalldir bin lmutil lmutil hostid sentinel run from the DOS prompt Sinstalldir bin hspice HSPICE executable running in a PC Windows environment Sinstalldir bin awaves AvanWaves executables running ina W s PC Windows environment Sinstalldir bin hspui GUI utility that launches HSPICE EXE and AWAVES EXE The hspice ini File On Windows platforms the hspice ini file is the configuration file that contains HSPICE options such as the search path For example Option Post 1 Op Option Post_version 9601 If you have installed more than one version of HSPICE on the same PC more than one hspice ini file will exist but only one takes effect when you start the tool The installdir meta cfg file points to the current hspice ini file Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 13 Related Documentation and Customer Support For docu
21. 25 2 Installing the Software The steps in this procedure describe how to install Astro on the Red Hat Linux 32 bit platform For other platforms use the appropriate file name and platform for the tool you want to install To install the Astro software on your server 1 3 Change directory to the installation directory by entering ed install_dir where install_dir is the directory where you want to install the software Examine the contents of your directory o ls cdrom volume_name You should see the following file cdrom volume_name U 2003 09 astro ia 32 tar gz Unzip the file gzip dc cdrom volume_name U 2003 09 astro ia 32 tar gz tar vxf 4 Change to the bin directory For example ed bin ia 32 Copy the Synopsys license daemon to the etc directory cp p avantd etc Create a license directory mkdir usr local flexlm usr local flexlm licenses Installing Astro Astro Interactive Ultra JupiterxT and Columbia 25 3 7 Copy the license to the license directory cp source_dir license dat usr local flexlm licenses where source_diris where the license dat and package dat file resides 8 Start the license server install_dir bin ia 32 lmgrd c usr local flexlm licenses license dat 1l usr local flexlm licenses license log 9 To automatically start the license server whenever you reboot the server add the following line to the etc rc local file instal
22. Columbia 25 5 Installing Astro Astro Interactive Ultra JupiterXT and Columbia 25 6 26 Installing Astro Rail version V 2003 12 Note The installation instructions in this chapter are the most up to date available at the time of production However changes might have occurred For the latest installation information see the product release notes or documentation This chapter contains the following sections Media Availability and Supported Platforms Installing the Software Setting Up Astro Rail for a New User Verifying the Astro Rail Installation 26 1 Media Availability and Supported Platforms Astro Rail is available on CD or by FTP download Obtain the appropriate binary executable files based on the operating system you need Table 26 1 shows the supported platforms for the V 2003 12 release Table 26 1 Supported Operating Systems and Platform Keywords Operating system Platform keyword Solaris 8 9 SUN 32 SUN 64 HP UX 11 0 11i HP 64 Red Hat Linux 7 2 IA 32 Installing the Software The steps in this procedure describe how to install Astro Rail on the Sun Solaris 64 bit platform For other platforms use the appropriate file name and platform for the tool you want to install To install the Astro Rail software on your server 1 Change directory to the installation directory by entering o cd install dir where install_dir is the directory where you want to install the software
23. Error Message Xlib connection to machine 0 0 refused by server Xlib Client is not authorized to connect to Server Bad return from XOpenDisplay Explanation The program does not have permission to open a window on the display e Check to be sure the DISPLAY environment variable is set correctly e Ifthe DISPLAY environment variable is set correctly on the console of the display enter the following command xhost Error Message tmafork command not found Explanation The tmafork TCAD utility cannot be found e Check to be sure the TCAD bin directory is in the search path e Check to be sure the TCAD utilities are installed correctly and that tmafork is linked to the TCAD bin directory Error Message xxx Open Pipe signal 13 code 0 Installing TCAD Products and Utilities 31 19 Explanation The TCADPLOT process is terminating abnormally leaving the TCAD program piping data to a broken pipe e Check to be sure TCADPLOT works correctly outside the TCAD program by entering the following command tmaplot x test e If TCADPLOT works correctly outside the TCAD program the error is most likely caused by insufficient system resources to start the TCADPLOT process Check your system resources when running the TCAD program to be sure there are enough resources to run the TCADPLOT process Error Message window Base frame not passed parent window in environment Cannot create base frame Proces
24. Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 Define the SYNOPSYS environment variable see Defining the SYNOPSYS Environment Variable on page 1 19 Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 4 1 Installing the Software To download and install AMPS from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the AMPS software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 2 on page 2 13 shows a Synopsys media installation script for PrimeTime AMPS is installed in a similar manner The AMPS tool is on the PathMill CD AMPS is a stand alone product and cannot be installed over an existing Synopsys product including a prior version of AMPS You must create a new directory for AMPS Setting Up AMPS for Each User To set up anew AMPS tool user add the AMPS directory containing the executable file to the PATH environment variable If you are using the C shell add the following line to the cshrc file set path SSYNOPSYS platform amps bin path If you are using the Bourne Korn or Bash shell add the following
25. Installing Astro Rail version V 2003 12 26 2 3 Examine the contents of your directory ls cdrom volume_name You should see the following file cdrom volume_name astrorail_V 2003 12_SUN 64 tar gz Unzip the file gzip dc cdrom volume_name astrorail_V 2003 12_SUN 64 tar gz tar vxf 4 8 o oO Change to the bin directory For example cd bin SUN 64 Copy the Synopsys license daemon to the etc directory cp p avantd etc Create a license directory mkdir usr local flexlm usr local flexlm licenses Copy the license to the license directory cp source dir license dat usr local flexlm licenses where source _dir is the location of the license dat and package dat file Start the license server install_dir bin SUN 64 lmgrd c usr local flexlm licenses license dat 1l usr local flexlm licenses license log Installing Astro Rail version V 2003 12 26 3 9 To automatically start the license server whenever you reboot the server add the following line to the etc rc local file install_dir bin SUN 64 1lmgrd c usr local flexlm licenses license dat 1l usr local flexlm licenses license log where nstall_diris the directory where you installed the software For more information about the license server see www synopsys com keys or the FLEX m End User Manual Setting Up Astro Rail for a New User This section describes how to set up a local machine for Solaris so
26. Plug In 0 00 05 23 5 Installing SOLD os ects ice aa a a sla Pee EREE A 23 5 Contents ot SOLDiwcewia teeta eR PARA Reema pees 2 23 5 Installation Options ici00 cede it evecs se eutwcdd dod SS 23 6 Installing SOLD CDs on HP UX Platforms 23 7 Electronic Software Transfer Installation 23 7 CD Installation soeucee lo eee sea datee Ah AACE 23 8 Partial Installation rae nc eee ead oe BER ee ees 23 8 Verifying the SOLD Installation 0 00 eee eee 23 9 Configuring SOLD for Each User 202000005 23 9 Searching SOLD on Linux oo00 coe naked RaW deen Bees 23 10 24 Troubleshooting MEMO padreta eww eb cue eed ite geen eae PE eee eee A 24 2 Why Do Get an out of memory Message 24 2 What Should Do When an out of memory Eror OCCU 25 sc caves idee CE EEN E 24 4 X Window SVSIOIN 2 ni a tharwne aaaeeeaa 24 5 Part Il Physical Implementation 25 Installing Astro Astro Interactive Ultra JupiterXT and Columbia Media Availability and Supported Platforms 25 2 Installing the Software a na saaa aaaea 25 3 xi 26 27 28 xii Setting Up Astro fora New User 20200 eee 25 4 Verifying the Astro Installation 00 0200 0000 a ee 25 5 Installing Astro Rail version V 2003 12 Media Availability and Supported Platforms 26 2 Installing the Software 2 2 2
27. SOLD User Guide To access the SOLD User Guide open SOLD and click the hypertext link labeled Using Synopsys Online Documentation Searching SOLD on Linux Only the Find command Edit gt Find is available for searching the Linux version of SOLD To locate information with the Find command use the print version of a document From the SOLD front page select a document set then click the print version icon lt 3 next to the document you want Installing Synopsys Online Documentation version V 2003 1 2 23 10 24 Troubleshooting This chapter contains the following sections e Memory e X Window System 24 1 Memory Some common memory problems and possible solutions are described in this section Why Do I Get an out of memory Message Here is a possible scenario A large job is running on a machine that has abundant swap space You try to run a Design Compiler job on this machine and assume that you don t need to be concerned about running out of swap space But the application terminates with a fatal out of memory message before the machine runs out of swap space UNIX limits the amount of memory a job or process can consume while it is running If a job reaches these limits before the system runs out of swap space the job terminates with the fatal out of memory error message These limits are built into the UNIX OS to prevent a single job or process from consuming all system resources Swap space
28. Support To ensure a successful installation complete the following procedure before beginning the installation process e Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 The instructions in this chapter also apply to VCSi 20 1 Note The VirSim GUI installs with VCS If you want to install the GUI as a stand alone tool see Appendix A Installing VirSim version 4 3 Installing the Software VCS is a stand alone product and cannot be installed over an existing Synopsys product including a prior version of VCS You must create a new directory for VCS To download and install VCS by electronic software transfer 1 Create a VCS installation directory and change to that directory For example enter mkdir u edatools ed u edatools 2 Download the software to the installation directory 3 Uncompress and untar the files gzip dc u edatools vcs_platform_version tar gz tar xvf This command creates a VCS subdirectory named after the release of VCS that you are installing To install VCS from a CD 1 Create a VCS installation directory and change to that directory For example oe mkdir u edatools vcs ed u edatools vcs Installing VCS version 7 0 2 20 2 2 Mount the CD by using the appropriate command for your operating system For example enter mount o ro dev dsk c2t1id4s0 cdrom Note Moun
29. a browser based HTML Help system For optimal viewing use Netscape Navigator version 4 78 for UNIX This Help system is not supported in Netscape Navigator version 6 or later Important When you use online Help from within the GUI the Netscape executable file must be on the UNIX path Floorplan Compiler Help makes extensive use of Java JavaScript and style sheets In your browser preferences select the Advanced category and make sure that e The Enable Java applets Enable JavaScript and Enable Style Sheets options are all selected e The Enable Java Plugin option is deselected You can open the Help system from within the Floorplan Compiler GUI tool or stand alone in Netscape Navigator Installing Floorplan Compiler version V 2003 12 7 3 Verifying the Floorplan Compiler Installation To verify the Floorplan Compiler installation 1 Make sure you are in a directory where you have read write privileges ed HOME Invoke the tool by entering the following command SYNOPSYS platform fpc bin fpc_shell Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 If you see information about the product version production date and copyright the installation was successful Exit foc_shell by entering exit on the command line Run the Floorplan Compiler GUI on each installed platform by entering the following command SYNOPSYS platform fpc bin fpc_gui Replac
30. a single term by the system such as set_annotated_delay Indicates a keyboard combination such as holding down the Control key and pressing c Indicates a continuation of a command line Indicates levels of directory structure Indicates a path to a menu command such as opening the Edit menu and choosing Copy Customer Support Customer support is available through SolvNet online customer support and through contacting the Synopsys Technical Support Center Accessing SolvNet SolvNet includes an electronic knowledge base of technical articles and answers to frequently asked questions about Synopsys tools SolvNet also gives you access to a wide range of Synopsys online services including software downloads documentation on the Web and Enter a Call to the Support Center To access SolvNet 1 Go to the SolvNet Web page at http solvnet synopsys com 2 If prompted enter your user name and password If you do not have a Synopsys user name and password follow the instructions to register with SolvNet If you need help using SolvNet click SolvNet Help in the Support Resources section Xxi xxii Contacting the Synopsys Technical Support Center If you have problems questions or suggestions you can contact the Synopsys Technical Support Center in the following ways e Open a call to your local support center from the Web by going to http solvnet synopsys com Synopsys user name and password requ
31. and Installing the Software by EST on page 2 2 To install the Arcadia software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 1 on page 2 10 shows a Synopsys media installation script for the synthesis tools Arcadia is installed ina similar manner Arcadia is a stand alone product and cannot be installed over an existing Synopsys product including a prior version of Arcadia You must create a new directory for Arcadia Setting Up Arcadia for Each User To set up a new Arcadia tool user e If you are using the C shell source the CSHRC_ platform file located in the install directory cd install_directory source CSHRC_platform ole The install script for Arcadia creates a CSHRC_ platform file for each platform installed The term platform is replaced with the platform you installed The CSHRC_ platform file contains the line set path install_directory platform arc bin Spath Installing Arcadia version U 2003 03 5 2 where install_directory is the directory in which the tool has been installed If you don t source the CSHRC_ platform file copy the preceding line and set the path from that file If you are using the Bourne or Korn shell add the following line to the profile file or kshrc file PATH install_directory platform arc bin PATH export PATH Replace platform with the appropriate platform see Products and Suppor
32. any GUI window Installing Formality version V 2003 12 8 3 Installing Formality version V 2003 12 8 4 Installing FPGA Compiler II version T 2003 09 FC3 8 on UNIX Platforms This chapter explains how to install FPGA Compiler Il ona workstation running Solaris or HP UX For instructions on how to install FRGA Compiler Il on a system running a Windows NT platform see Chapter 10 Installing FPGA Compiler II version T 2003 09 FC3 8 on Windows Platforms This chapter contains the following sections e Product Support e System Requirements e Installing the Software e Enabling Online Document Readers 9 1 Product Support The FPGA Solutions Web page is regularly updated Check it for application notes online Help updates and other valuable information http www synopsys com products fpga For additional installation instructions go to http www synopsys com products fpga install_ fc2 htm System Requirements Table 9 1 shows the minimum system requirements for UNIX installations of FPGA Compiler II Table 9 1 UNIX System Requirements Operating system Memory Disk space for installation Solaris 7 8 64 MB of RAM 100 150 MB eoit mode ay 140 MB of swap space HP UX 11 0 11 11 11i 64 MB of RAM 100 150 MB 32 bit mode only 140 MB of swap space 1 200 MB of virtual memory RAM swap space is recommended for most designs Larger designs might require more memory Installing FPG
33. files to the PATH environment variable If you are using the C shell add the following line to the cshrc file set path usr dt bin usr bin X11 path For Solaris 8 or 9 add set path usr dt bin usr openwin bin path If you are using the Bourne Korn or Bash shell add the following line to the profile kshrc or bashrc file PATH usr dt bin usr bin X11 S PATH export PATH For Solaris 8 or 9 add PATH usr dt bin usr openwin bin X11 SPATH export PATH Installing the Synopsys Synthesis Tools version V 2003 12 3 6 Setting Up the Systemwide Defaults If you are using the Design Analyzer product you can customize the display for all users at a site by modifying the Design Analyzer application defaults app defaults file This file is placed in the following location during installation SYNOPSYS admin setup Design_analyzer To see a list of available colors for the Solaris 7 and 8 platforms enter more usr openwin 1lib X11 rgb txt For all other platforms enter more usr 1lib X11 rgb txt To see a list of available fonts enter xlsfonts more To install the changes copy the modified app defaults file into the systemwide app defaults location which varies from site to site To find the systemwide location at your site contact your system administrator Note You must have root access privileges to install this systemwide defaults file If your app defaults location is in X11 a comm
34. for Each User Verifying the Star RCXT Installation Customer Support Installing Star RCXT version V 2003 12 29 1 Media Availability and Supported Platforms Star RCXT is available on CD or by EST download Obtain the appropriate binary executable files based on the operating system you need Table 29 1 shows the supported platforms for the V 2003 12 release Table 29 1 Supported Operating Systems and Platform Keywords Operating System Platform keyword Solaris 5 7 Sun 32 Sun 64 HP UX B 11 00 HP 32 HP 64 Red Hat Linux 7 2 IA 32 Red Hat Linux Advanced Server 2 1 1A 64 Installing the Software To install Star RCXT 1 Create a Star RCXT installation directory if one does not already exist For example mkdir p usr synopsys star rext 2 Change to the Star RCXT installation directory cd usr synopsys star rext 3 Download the Star RCXT binary files to the installation directory You can get the latest Star RCXT download instructions from the SolvNet Release Library Installing Star RCXT version V 2003 12 29 2 Uncompress and untar the files For example gzip dc platform_star rext version tar gz tar xvf Substitute the appropriate platform keyword for platform See Media Availability and Supported Platforms on page 29 2 Note This command will create a subdirectory in the Star RCXT installation directory For example usr synopsys star rext platform_star rext To set the f
35. in This Release e About This Guide e Customer Support The installation instructions in this guide reflect the latest version of Synopsys software for each product Not all products are the same version All instructions in this guide are for UNIX systems unless otherwise indicated Important Install each version of the software in a new directory Do not install different versions of Synopsys software in the same directory xvii What s New in This Release xviii For information about new features and changes in specific Synopsys tools see the individual product documentation For links to Synopsys documentation see Related Publications in the next section CosmosScope and SaberDesigner Because of last minute changes installation instructions for CosmosScope and SaberDesigner are not included in this Installation Guide For installation instructions for CosmosScope version V 2003 12 see the V 2003 12 INSTALL_README wri file in the product download directory or on the product CD For installation instructions for SaberDesigner or CosmosScope version U 2003 09 see SOLD version U 2003 09 or the U 2003 09 version of the Installation Guide at http www synopsys com support Install_ Guide html About This Guide The Installation Guide provides the basic information and procedures required to install Synopsys tools Audience This guide is written for system administrators responsible for installing Syn
36. operating system For example enter mount o ro dev dsk c2t1d4s0 cdrom Note Mounting instructions are different for each platform See your system administrator for the correct CD mounting commands Also for sparcOS5 with vold the volume management daemon for managing CD and floppy devices the cdrom directory already exists and the CD is automatically mounted Therefore use cd cdrom cdrom0 instead of cd cdrom and use eject to unmount the CD Downloading and Installing the Software 2 8 Installing the Software From the CD The following steps apply only to tools that use the standard installation For CD installation of FPGA Compiler Il see Installing the Software on page 9 3 To install the software 1 Move to the CD ROM directory For example enter cd cdrom 2 View the README 1ST file on the CD for more information View the README productname file for the most up to date disk space requirements 3 Enter the installation command install now 4 Answer the installation program prompts If you receive an UNCOMPRESS TAR ERROR during the installation script rerun the installation command using the i option to correct the problem For example enter f install now i Example 2 1 shows a sample Synopsys media installation script for the synthesis tools on the Sun Solaris platform it applies to installation by EST and from the CD Other tools are installed in a similar manner Downlo
37. or have system administrator privileges You need write permission for the installation directory Note The Hercules software is configured so that multiple platforms of this version can be installed in a single installation directory install _dir To install the Hercules software on your server 1 Create a Hercules installation directory if one does not already exist For example o mkdir p usr synopsys hercules In the rest of this chapter this directory path is referred to as install _dir 2 Download the Hercules release to the installation directory You can get the latest Hercules download instructions from the SolvNet Release Library Installing Hercules version V 2003 12 27 3 3 Uncompress and untar the files o gzip dc hercules version platform tar gz tar xvf This command creates a subdirectory in the Hercules installation directory For example usr synopsys hercules necessary_files_and_directories In the remainder of this chapter this subdirectory is referred to as the Hercules installation directory To set the file permissions on the new directory tree and its contents enter chmod R 755 install dir Remove the hercules version platform tar gz file o rm hercules_version_platform tar gz Installing Hercules version V 2003 12 27 4 Setting the Environment Variables This section discusses the following environment variables e SHERCULES_HOME_DIR e LM LI
38. section explains how to set up your search path so that you can run a TCAD product from any directory Checking Your Search Path Ifa TCAD product has already been installed on your system with the installation script the TCAD bin directory might already exist in your search path To determine whether it does enter which program where programis a TCAD executable file such as medici raphael or taurus If you get a response similar to usr tcad bin program your search path is set correctly If you get a response similar to no program in bin usr bin usr local bin you must modify your search path as described in the following section Installing TCAD Products and Utilities 31 9 Modifying Your Search Path Your search path is defined by the PATH environment variable Determine your current search path by entering echo PATH Note PATH must be entered in uppercase letters This is an example of a search path bin usr bin usr local bin Modifying Your Path in the C shell The following example illustrates the commands used to modify your path In this example the TCAD directory on your system is named usr myaccount tcad e To permanently add this directory to your search path add the following line to your HOME profile set path usr myaccount tcad bin path Save your changes e Enter the following command source cshrec Modifying Your Path in the Bourne or Korn Shell To modify
39. the Linux platform see Searching SOLD on Linux on page 23 10 The following sections describe how to determine your current software configuration Checking the Version Number If you are using 3 x or an earlier version of Acrobat you must upgrade to view SOLD Follow the instructions in Acquiring and Installing the Acrobat Reader Software on page 23 3 To check the version number 1 Open Acrobat Reader 2 Choose Help gt About Acrobat Reader or Help gt About Adobe Acrobat 3 In the window that appears verify that the words Acrobat Reader 4 0 or Adobe Acrobat 4 0 appear Later versions of Acrobat Reader are also supported 4 Close the About screen by clicking anywhere in the window Installing Synopsys Online Documentation version V 2003 12 23 4 Checking for the Search Plug In If you are using Acrobat Reader without the Search plug in you must upgrade to have full text searching capability in SOLD The Search plug in cannot be downloaded from the Adobe site as a separate file to upgrade you must download the entire Acrobat Reader with Search plug in package Follow the instructions in Acquiring and Installing the Acrobat Reader Software on page 23 3 To check for the Search plug in 1 Open Acrobat Reader if it is not already open 2 Choose Help gt About Plug Ins or About Adobe Acrobat Plug Ins to verify that Acrobat Search is on the list of installed plug ins Ins
40. the input netlist file and output list files If you do not name an output file all of the lis st0 and trO files will be written in the directory in which you run HSPICE or hspice exe At the DOS prompt in Windows enter c gt ed work_directory c gt installdir BIN HSPICE i netlist o listfile Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 11 Running AvanWaves on Windows Start AvanWaves in any of the following ways e Double click the HSPUI icon and then click the AvanWaves button e Double click the AvanWaves icon e Atthe DOS prompt in Windows enter c gt installdir BIN AWAVES Important If you start AvanWaves by using a method other than selecting the HSPUI icon and then you open online Help you must delete the Galaxy Help Server task from the Task Manager after you exit AvanWaves Otherwise the next invocation of HSPICE can have a memory conflict with the AvanWaves Galaxy Help server Running Older Versions of HSPICE You can use the HSPUI utilities to run different versions of HSPICE that are already installed on your computer In the installation directory installdir the versions txt file contains all the information about different versions of HSPICE An example of a versions txt file follows lt BOF gt c avanti Hspice2001 2 BIN hspice exe HSPICE 2001 2 c avanti Hspice2002 2 BIN hspice_mt exe HSPICE 2002 2 lt EOF gt Installing HSPICE version U
41. the tool by entering the following command SYNOPSYS platform pm bin pathmill Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 If you see information about the product version production date and copyright the installation was successful Installing PathMill version V 2003 12 12 3 Installing PathMill version V 2003 1 2 12 4 13 Installing PowerMill version U 2003 03 This chapter contains the following sections Installing the Software Setting Up PowerMill for Each User Verifying the PowerMill Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 13 1 Installing the Software To download and install PowerMill from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the PowerMill software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 2 on page 2 13 shows a Synopsys media installation script for PrimeTime PowerMill is installed in a similar manner The PowerMill subtools ADFMI TurboWave and VTRAN ar
42. to sale to certain countries Contact your sales representative for additional information Installing TCAD Products The general procedure for installing a TCAD product consists of the following steps 1 Obtain a SolvNet account Download TCAD software or request CD media 2 3 Establish a TCAD directory 4 Run the product installation script Installing TCAD Products and Utilities 31 3 5 Obtain the license dat file and start the license daemon To obtain the license dat file go to the SmartKeys Web page at http www synopsys com smartkeys For information on starting the license daemon go to the Licensing QuickStart Guide at www synopsys com keys Obtaining a SolvNet Account SolvNet is the online gateway to Synopsys service and support Through SolvNet customers can retrieve software request media retrieve license files and view online documentation If you do not have a SolvNet account register for an account by visiting the SolvNet Web site http solvnet synopsys com and following the instructions to register with SolvNet Note To access Synopsys online services in SolvNet you need to register with a valid Synopsys site ID Installing TCAD Products and Utilities 31 4 Downloading TCAD Software or Requesting CD Media After establishing a SolvNet account by using your Synopsys site ID you can download the TCAD software from the Synopsys electronic software transfer EST system or if elig
43. to work with the synthesis tools If you encounter problems see the SCL documentation Licensing Quick Start and Licensing Installation and Administration Guide Optional Installation of IddQTest The IddQTest option of TetraMAX is installed separately from TetraMAX ATPG and requires a special license To install lIddQTest 1 Run the same installation script again but enter idq at the Product s Selected prompt 2 For the lddQTest target directory specify the location where you installed the TetraMAX overlay product Note The installation script does not allow you to install IddQTest into a TetraMAX stand alone installation To create a stand alone installation of IddQTest you must specify a completely separate directory Once you have done this manually copy IddQTest into the same directory as the TetraMAX stand alone product Installing TetraMAX version V 2003 12 18 5 Setting Up the User Environment The procedure for setting up a new TetraMAX user has changed When you define the TetraMAX root directory you can now use the SSYNOPSYS environment variable Note For backward compatibility you can still set SYNOPSYS_TMAX If SSYNOPSYS_TMAX is set it will override SYNOPSYS To set up a new TetraMAX tool user add the TetraMAX directory containing the executable file to the PATH environment variable If you are using the C shell add the following line to the cshrc file set path S SYNOPSYS bin pat
44. you must download one common file platform independent package and one or more platform specific files For installation instructions see Performing EST Installation next Downloading and Installing the Software 2 5 Performing EST Installation To install the software le oe Untar the tar files or untar and uncompress the tar Z or tar gz files For example For tar files ole ar xvf productname_productversion_common tar t tar xvf productname_productversion_platform tar ol For tar Z files cat productname_productversion_common tar Z uncompress tar xvf cat productname_productversion_platform tar Z uncompress tar xvf or oe zcat productname_productversion_common tar Z tar xvf zcat productname__productversion_platform tar Z tar xvf oe For tar gz files oe gzip dc productname_productversion_common tar gz tar xvf gzip dc productname_productversion_platform tar gz tar xvf If you want to perform this process in two steps do the following oe gzip d productname_productversion_common tar gz tar xvf productname_productversion_common tar ole ole gzip d productname_productversion_platform tar gz tar xvf productname_productversion_platform tar oe Substitute the appropriate product ID and version for productname_productversion and the platform keyword for platform See Products and Platforms on page 1 6 Downloading and Installing the
45. 0 32 After modification SUN 29 20 32 I SUN 29 20 32 X 30 20 32 15 24 15 24 15 24 15 24 15 24 15 24 33 0 33 20 500 0 33 0 33 0 500 0 33 0 3320 500 0 33 0 33 0 500 0 F FE FIFE 9999 FoR ETET 9999 l F EF FIFF 99 99 l EF FTEF 9999 EF Bs ETET 9999 D F F FTFEF 9999 For further information on the prpdev file and possible graphics devices see the manual for the TCAD product you are installing Installing TCAD Products and Utilities 31 17 Sun X and tmaplot Both Sun and X drivers use the tmaplot graphics utility to generate graphics by piping graphics output through the tmaplotx executable program The tmaplot utility automatically remembers up to 200 plots and allows you to scroll through them Use the following means to control the display e Right mouse button Scroll backward e Left mouse button Scroll forward e Control c Kill tmaplot display To use X graphics you must set the DISPLAY environment variable to your display machine Usually DISPLAY is set to the name of your computer followed by 0 0 For example if the name of your machine is mymachine enter the following command to set DISPLAY setenv DISPLAY mymachine 0 0 Note To Sun users You must also set the LD_LIBRARY_PATH environment variable to your OpenWindows library directory For example setenv LD_LIBRARY_PATH usr openwin 1lib Installing TCAD Products and Utilities 31 18 Troubleshooting
46. 10 System Studio HDL code generation 17 6 installing 17 2 IPC semaphore problems 17 8 key file problems 17 7 setting up for new user 17 3 troubleshooting startup problems 17 7 verifying installation 17 6 VHDL packages 17 6 SystemC Compiler setting up 3 8 systemwide defaults synthesis tools 3 7 System Studio 17 3 T tar files types of 2 2 TCAD disk requirements 31 6 downloading software 31 5 establishing directory tree 31 6 graphics devices 31 14 specifying devices 31 15 Sun X tmaplot 31 17 obtaining SolvNet account 31 4 product format and description 31 12 products installing 31 3 requesting CD media 31 5 running installation script 31 7 search path modifying 31 10 setting up 31 9 utilities 31 21 TCAD utilities 31 21 TetraMAX installing overlay 18 4 stand alone 18 2 license key requirements 18 2 platform keyword 1 7 product ID 1 7 verifying installation 18 7 TimeMill installing 19 2 platform keyword 1 7 product ID 1 7 setting up for new user 19 2 verifying installation 19 4 To 3 6 tools synthesis 3 2 troubleshooting memory 24 2 IN 5 System Studio 17 7 X Windows System 24 5 V VCS installing 20 2 platform keyword 1 7 product ID 1 7 support 20 7 verifying installation 20 6 VCS simulator 3 17 VCSi installing 20 1 Vera documentation obtaining 21 4 downloading and installing 21 2 environment variables setting 20 4 21 3 22 4 license 20 5 21 4 22 5 VERA_HOME 20 4 21 3 22 4 platform keyw
47. 512 Recommended 1GB Recommended 2GB Preparing for Installation 1 11 Table 1 4 Minimum Memory Requirements Continued Tool Physical memory MB Swap space MB VCS 256 768 Recommended 2 GB Vera 256 512 Recommended 1GB Recommended 2GB VHDL Simulation Scirocco 256 512 Recommended 1GB Recommended 2GB 1 Forlarge designs the expected amount of required memory is approximately 1 million bytes per 2 000 gates 2 Physical memory and swap space requirements are dependent on design size For the figures in the table it is assumed that the design size is less than 1 million equivalent NAND gates Physical Memory Requirements for Synthesis PrimeTime and Design Budgeting For the synthesis PrimeTime or design budgeting tools to run efficiently the physical memory must equal 25 to 50 percent of the swap space For example if you have 128 MB of swap space you need at least 32 MB of physical memory You might need as much as 64 MB however The more physical memory you have the more quickly your job runs Swap Space Requirements for Synthesis Tools The amount of swap space required by the synthesis tools depends on the size and type of each circuit design Use the following formula to help you determine the minimum amount of available swap space required for HDL designs 16 3 MB 5 9 x size of the design in K gates Preparing for Installation 1 12 For example a 5K gate design requires 16 3
48. A Compiler Il version T 2003 09 FC3 8 on UNIX Platforms 9 2 Installing the Software Mounting the CD might require root access privileges If you do not have root access privileges see your system administrator for instructions on mounting the CD To install FPGA Compiler Il 1 Mount the CD ROM following the instructions in Mounting the CD on page 2 8 Make sure that your licensing software is installed For information on Synopsys Common Licensing SCL software see Acquiring a License on page 1 15 Change directory to the UNIX directory of the CD ROM For example ed cdrom0 UNIX Run the setup script setup csh from the UNIX directory of the CD ROM drive and follow the instructions For a typical shared installation choose option 1 to install the software and set up the license path Next choose option 1 for Solaris option 2 for HP UX or option 3 for both platforms Enter the path to the network keys in the format port hostname for example 27000 keyserv Installing FPGA Compiler II version T 2003 09 FC3 8 on UNIX Platforms 9 3 Enabling Online Document Readers The FPGA Compiler II User Guide is available online in Portable Document Format PDF To read this online document you must have version 4 0 or later of Adobe Acrobat Reader with Search plug in installed on your system To install Acrobat Reader with Search plug in download the latest version of Acrobat Reader from the Adobe h
49. Bash shell to set up a new user 1 In your HOME directory add the following lines to the appropriate user setup file profile kshrc or bashrc SYNOPSYS_CCSS ccss_home platform ccss export SYNOPSYS CCSS CCSS_SIM DIR ccss_sim_dir export CCSS SIM DIR Installing System Studio version V 2003 12 17 4 PATH SSYNOPSYS_CCSS bin SPATH export PATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Note You can define CCSS_SIM_DIR but if it is not set the GUI provides a reasonable default If the System Studio license file will not be installed in the default location add the following lines to your setup file CCSS_KEYS lic file export CCSS KEYS If the paths to the C compiler debugger and make command are not already included in your setup file add the following lines to it PATH compiler_home bin make_home bin SPATH export PATH To source the CCSS setup file add the following line to your setup file SYNOPSYS_CCSS gnupackages source_me sh Make these changes effective by logging out and logging in again or by entering HOME setup_file where setup _file is profile kshrc or bashrc Installing System Studio version V 2003 12 17 5 VHDL Simulation If you intend to use the external simulation interface for VHDL cosimulation under the algorithmic domain of System Studio you must ensure that the VHDL packages are analyzed before
50. C version Mentor D version If you have purchased any of these tools you must install the synthesis tools suite Most synthesis tools install on all platforms sparcOS5 sparc64 hp32 hp64 linux and rs6000 The exceptions are noted in Table 3 1 Table 3 1 Synthesis Tools That Do Not Install on All Platforms sparcOS5 hp32 linux rs6000 gccsparcOS5 Behavioral Compiler X X x x SystemC Compiler x x x X Design Analyzer xX X Xx Xx Installing the Synopsys Synthesis Tools version V 2003 12 3 3 Installing the Software To download and install the synthesis tools from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To transfer the files from the Synthesis CD to your system follow the installation procedure described in Installing Product Files From a CD on page 2 7 On the sparcOS5 platform you can choose to install either version C sf3 or D sf4 of the Synopsys Integrator for Falcon Framework product but not both On the hp32 platform you can install only version D sf4 Example 2 1 on page 2 10 shows a sample Synopsys media installation script for the synthesis tools Configuring the Synthesis Tools This section describes how to e Setup the synthesis tools for each user e Set up the systemwide defaults e Setup SystemC Compiler for Each User e Configure the Browser for Physical Compiler and Design Vision Online Help Instal
51. CENSE FILE It is recommended that you place these variables in your HOME cshre or HOME profile file as your default settings Setting the HERCULES HOME_DIR Environment Variable Follow these steps 1 Set the HERCULES HOME_DIR environment variable by replacing TOP LEVEL INSTALL DIR in install_dir nercules_setup csh and install_dir hercules_setup sh files with install_ dir 2 Update your environment by entering the following lines If you are using the C shell enter source cshre lf you are using the Bourne shell enter o profile Installing Hercules version V 2003 12 27 5 Setting the LM_LICENSE_FILE Environment Variable The LM_LICENSE_FILE environment variable defines the full path name to the location where the license files have been loaded on your machine To enable Hercules to check out a license set the LM_LICENSE_FILE environment variable For example e If you are using the C shell add the following line setenv LM_LICENSE_FILE port hostname e If you are using the Bourne shell enter these lines set LM_LICENSE_FILE port hostname export LM _LICENSE_FILE The port and host name variables correspond to the TCP port and license server host name specified in the SERVER line of the Synopsys license file To ensure better performance it is recommended that you use port host rather than using the path to the license file Each license file can contain licenses for many packag
52. CPU time number of processes and so on thereby depleting resources for other jobs Some limits applicable to Synopsys applications are e Data size The maximum data size including stack for the process e CPU time The maximum CPU seconds per process e Core dump size The maximum size of a core dump The data size limit is the most important It can be set at two levels e The system level Troubleshooting 24 2 Limits are enforced for everyone who runs on that system e Ona per user basis On all machines except those running HP UX you can change your personal limits by using the Limit command C shell or ulimit s d command Bourne Korn or Bash shell On the HP UX platform only the system administrator can set the limits Personal limits cannot exceed the systemwide limit For example the limits on a Sun client Solaris 8 might look like this limit cputime unlimited filesize unlimited datasize 524280 kbytes stacksize 8192 kbytes coredumpsize unlimited descriptors 256 memorysize unlimited Note In this example any jobs or processes started on the Sun client can grow to 524 MB before limits are enforced On some solaris systems setting the data size to unlimited defaults to a data size of only 2 GB To set a larger data size set the data size explicitly For example set it to 3 8 GB by using the following command limit datasize 3891 MB If the data size is sufficient check the sta
53. Formality You must create a new directory for Formality Setting Up Formality for Each User To set up a new Formality tool user add the Formality directory containing the executable file to the PATH environment variable If you are using the C shell add the following line to the cshrc file set path SSYNOPSYS platform fm bin path If you are using the Bourne Korn or Bash shell add the following line to the profile kshrc or bashrc file PATH SSYNOPSYS platform fm bin PATH export PATH Installing Formality version V 2003 12 8 2 Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 For information about the Synopsys setup file see the Formality User Guide Verifying the Formality Installation To verify the Formality installation 1 Make sure you are in a directory where you have read write privileges cd HOME Invoke the Formality shell by entering the following command S SYNOPSYS platform fm bin fm_shell Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 If you see information about the product version production date and copyright the installation was successful Exit fm_shell by entering exit on the command line Run the Formality GUI on each installed platform by entering the following command SYNOPSYS platform fm bin formality Exit the GUI by choosing File gt Exit in
54. Installation Guide Version V 2003 12 December 2003 Comments E mail your comments about Synopsys documentation to doc synopsys com SYNOPSYS Copyright Notice and Proprietary Information Copyright 2003 Synopsys Inc All rights reserved This software and documentation contain confidential and proprietary information that is the property of Synopsys Inc The software and documentation are furnished under a license agreement and may be used or copied only in accordance with the terms of the license agreement No part of the software and documentation may be reproduced transmitted or translated in any form or by any means electronic mechanical manual optical or otherwise without prior written permission of Synopsys Inc or as expressly provided by the license agreement Right to Copy Documentation The license agreement with Synopsys permits licensee to make copies of the documentation for its internal use only Each copy shall include all copyrights trademarks service marks and proprietary rights notices if any Licensee must assign sequential numbers to all copies These copies shall contain the following legend on the cover page This document is duplicated with the permission of Synopsys Inc for the exclusive use of and its employees This is copy number Destination Control Statement All technical data contained in this publication is subject to the export control laws of the United States of America Di
55. June 2003 release of Synopsys software the way the install now script checks the software version has changed This change affects overlay installation only When you attempt to install overlay software over an earlier release the installation script now looks only at the foundation identifier for example U or V it no longer looks for the release month and year For products that allow overlay installation this change enables you to install a later tool version for the same foundation release over an earlier tool version For example you could install TetraMAX version U 2003 09 over version U 2003 06 of the synthesis tools Do not attempt to install an earlier version of an overlay tool for example U 2003 06 over a later version of the tool U 2003 09 This installation is not supported but the install now script will not stop you from doing it if overlay installation is allowed for a product Supported Platforms and Operating Systems Table 1 1 lists the supported platforms operating systems and corresponding Synopsys platform keywords for this release Many platforms require operating system OS patches including year 2003 patches For detailed information see the Supported Platforms Guide page on the Synopsys Web site Go to Preparing for Installation 1 2 http www synopsys com products sw_platform html and under Supported Platforms Guides select the appropriate foundation for your release This Web page p
56. Makefile sol and Makefile hp To use the makefile method to link your executable file 1 Using a text editor such as vi edit the appropriate makefile to set variable values for VERILOG_LIB and VERILOG_INC Modify the lines in the makefile to read according to your data For example enter VERILOG_LIB VERILOG_INC pathl path2 where path7 is the path to your Verilog distribution o and a files and path2 is the path to your Verilog distribution h files The VERILOG_LIB variable must point to the directory path of the vlog o and omnitasks o files The VERILOG_INC variable must point to the directory path of the acc_user h and veriuser h files 2 Save the modified makefile and exit your text editor 3 Use the make utility to link the executable file make f Makefile platform The platform extension is sol or hp The make command uses the modified makefile to link your executable file creating a customized executable file called verilog_toggle Copying the Linked Executable File After you create your customized executable file change the permissions so that the file is not writable and copy it to a directory suitable for group access Installing the Synopsys Synthesis Tools version V 2003 12 3 16 Enter the following commands at the UNIX prompt chmod ogu w verilog toggle This removes write access to other group and user cp verilog toggle site_verilog_ bin_location This copies the file to the site_ver
57. NSE FILE The port and host name variables correspond to the TCP port and license server host name specified in the SERVER line of the Synopsys license file To ensure better performance it is recommended that you use port host rather than using the path to the license file Each license file can contain licenses for many packages from multiple vendors You can specify multiple license files by separating each entry with a colon Installing VHDL Simulation Scirocco version 2002 12 2 22 5 Setting Up VHDL Simulation Scirocco for Each User To set up a new Scirocco user add the directory containing the Scirocco executable files to the PATH environment variable e Ifyou are using the C shell add the following line to the cshrc file set path SYNOPSYS_SIM bin path e lf you are using the Bourne Korn or Bash shell add the following line to the profile or kshrc file PATH path SSYNOPSYS_SIM bin export PATH Verifying the VHDL Simulation Scirocco Installation To verify Scirocco installation enter SYNOPSYS_SIM admin install sim bin verify_install If Scirocco is correctly installed the system responds by printing the following information and various copyright messages Info Checking files in image Info Checking file permissions passed Info Running Scirocco existence tests passed Verification of u edatools vcs_mx scirocco2002 12 2 PASSED Installing VHDL Simulation Scirocco ver
58. Platforms e Installing the Software e Setting the Environment Variables e Setting Up Hercules for Each User e Verifying the Hercules Installation 27 1 Media Availability and Supported Platforms The Hercules and Hercules Explorer tools are available on CD or by EST download Obtain the appropriate binary executable files based on the operating system you need Table 27 1 shows the supported platforms for the V 2003 12 release Table 27 1 Supported Operating Systems and Platform Keywords Operating system Platform keyword Solaris 8 SUN32_58 SUN64_58 HP UX 11 0 HP32_U11 HP64_U11 Red Hat Linux 7 2 IA32_L24 Red Hat Advanced Server 2 1 IA64_L24 AIX 5 1 RS64_AIX51 Amd Opteron RHEL v3 amd64 64 bit mode 1 The AIX 5 1 and Red Hat Enterprise Linux platforms are not available on CD They will be available for download by electronic software transfer EST at a later date For availability check with your Synopsys sales representative Installing Hercules version V 2003 12 27 2 Installing the Software The steps in the following procedure describe how to install Hercules on the Sun Solaris 32 bit platform The procedure for other platforms is similar Before you begin the installation e Make sure you have enough disk space for Hercules and Hercules Explorer installation For a full installation on one platform 120 MB is recommended e To install Synopsys tools it is recommended that you log on as root
59. PrimeTime version V 2003 12 This chapter contains the following sections Installing the Software Setting Up PrimeTime for Each User Verifying the PrimeTime Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 15 1 Installing the Software To download and install PrimeTime from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the PrimeTime software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 2 on page 2 13 shows a Synopsys media installation script for PrimeTime PrimeTime is a stand alone product and cannot be installed over an existing Synopsys product including a prior version of PrimeTime You must create a new directory for PrimeTime Note You can not install PrimeTime as an overlay product in the same directory as the synthesis tools Setting Up PrimeTime for Each User PrimeTime does not require the SYNOPSYS variable If you have installed other Synopsys tools such as the synthesis tools that use the SYNOPSYS variable a conflict might arise To avoid t
60. Software 2 6 Note If you don t want to see the list of unpacked files omit the v from xvf 2 Execute the following command to install the software install now To install Synopsys tools it is recommended that you log on as root or have system administrator privileges You need write permission for the installation directory 3 Answer the installation program prompts Important When you are prompted to choose a location for installing the software do not select the tmp directory You must specify a new directory Do not install different versions of Synopsys software in the same directory Repeat steps 1 through 3 for each tool you want to install Installing Product Files From a CD Use the same installation procedure to transfer the files from each CD or CD set to your system To install a CD 1 Mount the CD 2 Run the installation script 3 Unmount the CD Downloading and Installing the Software 2 7 Complete information about these steps is given in the following sections Mounting the CD Mounting the CD might require root access privileges If you do not have root access privileges see your system administrator for instructions on mounting the CD If you have the proper privileges complete the following steps To mount the CD 1 Place the CD in the CD drive 2 Create a CD directory For example enter mkdir cdrom 3 Mount the CD by using the appropriate command for your
61. Verilog XL simulator s executable file to the VPOWER user tasks You must define the name of the executable file created by cr_vlog for example verilog_toggle Installing the Synopsys Synthesis Tools version V 2003 12 3 14 To use the vconfig method to link your executable file 1 Use your vconfig utility or an equivalent utility to generate the cr_vlog script or an equivalent script In the script set an environment variable pointing to the directory of the generated library archive For example if you are using Solaris 7 or later setenv PPLILIB lib sparcOS5 libvpower a In cr_vlog look for the line that includes the math libraries 1m Add a line above this line to include the libvpower a library For example SPPLILIB lm Run cr_vlog o cr_vlog This script links your executable file to the VPOWER user tasks and creates the customized executable file called verilog_toggle For details about linking the programmable language interface PLI by using the vconfig utility see the Power Compiler User Guide Proceed to Copying the Linked Executable File on page 3 16 Using a Makefile to Link the Executable File Using the UNIX make command you can use a makefile to link your Verilog XL executable file to the VPOWER user tasks The makefile creates a modified executable file called verilog_toggle Installing the Synopsys Synthesis Tools version V 2003 12 3 15 Two makefiles exist
62. Windows 0000e eee 28 11 Running AvanWaves on Windows 02 05 28 12 Running Older Versions of HSPICE 28 12 The hspice ini File tke ved 6 G4 Geet am este dare eae 28 13 Related Documentation and Customer Support 28 14 29 Installing Star RCXT version V 2003 12 Media Availability and Supported Platforms 29 2 Installing the Software 2 0 00 0c es 29 2 Setting Up Star RCXT for Each User 2 2 00 29 4 Verifying the Star RCXT Installation 2 00 29 5 CUSIOMen Supports y osc cc Meme eae eek eRe Ree RACE WES 29 5 30 Installing StarSim XT version V 2003 12 Media Availability and Supported Platforms 30 2 Downloading and Installing the Software 30 2 Setting the Environment Variables 00000eaee 30 3 xiii 31 xiv Setting the starsimxt_HOME Environment Variable 30 4 Setting the LM_LICENSE FILE Environment Variable 30 4 Verifying the StarSim XT Installation 00 30 5 Customer Support nasasa asaan aaee 30 6 Installing TCAD Products and Utilities Supported Platforms and Media Availability 31 2 Installing TCAD Products anana aaaea 31 3 Obtaining a SolvNet Account 00000 a 31 4 Downloading TCAD Software or Requesting CD Media 31 5 Establishing a TCAD Directory Tree
63. a environment variables setting 6 4 CADABRAHOME 6 4 LM_LICENSE_FILE 6 5 installing 6 2 support 6 6 verifying installation 6 6 CD installing 2 7 loading files from 2 9 mounting 2 8 unmounting 2 15 CoCentric System Studio product ID 1 7 Columbia installing 25 1 command install now 2 7 2 9 core dump size 24 2 CPU time 24 2 D defaults synthesis tools 3 7 System Studio 17 3 Design Analyzer customizing colors 3 7 customizing fonts 3 7 Design Compiler verifying installation 3 20 DesignWare installation 3 2 disk space requirements 1 8 documentation online FPGA Compiler II 9 4 SOLD 23 2 downloading software 2 2 by FTP 2 4 from the Web 2 5 E electronic software transfer 2 6 downloading files by 2 5 installation 2 6 Web address 2 5 environment variable SYNOPSYS 1 19 errors X Window System 24 6 EST see electronic software transfer F file names configuration for long 1 4 file app defaults 3 7 files see product files Floorplan Compiler installing 7 2 platform keyword 1 6 product ID 1 6 setting up for new user 7 2 verifying installation 7 4 Formality installing 8 2 platform keyword 1 6 product ID 1 6 IN 2 setting up for new user 8 2 verifying installation 8 3 FPGA Compiler II installing 9 3 platform keyword 1 6 product ID 1 6 system requirements 9 2 FPGA Compiler Il on Windows platforms installing 10 3 installing from CD ROM 10 3 online documentation enabling 10 4 system requirements 10 2
64. able Document Format PDF with the product files e SolvNet article 900006 VERA Licensing Structure at http solvnet synopsys com retrieve 900006 Installing Vera version 6 2 0 21 5 Installing Vera version 6 2 0 21 6 22 Installing VHDL Simulation Scirocco version 2002 12 2 This chapter contains instructions about installing the VHDL Simulation Scirocco tool in the following sections e Installing the Software e Setting the Environment Variables e Setting Up VHDL Simulation Scirocco for Each User e Verifying the VHDL Simulation Scirocco Installation The instructions in this chapter also apply to Scirocco i To ensure a successful installation have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 22 1 Note The VirSim GUI installs with Scirocco If you want to install the GUI as a stand alone tool see Appendix A Installing VirSim version 4 3 Installing the Software VHDL Simulation Scirocco is a stand alone product and cannot be installed over an existing Synopsys product including a prior version of VHDL Simulation Scirocco You must create a new directory for VHDL Simulation Scirocco Note The installation procedure for VHDL Simulation Scirocco has changed with this release To download and install VHDL Simulation Scirocco by electronic software transfer 1 Create a VHDL Simulation Sci
65. able 31 3 to determine the approximate disk space required for the products you need Make sure you select a location with sufficient disk space to install these products and allow room for future installations Table 31 3 TCAD Disk Requirements Product Disk MB Aurora 190 Raphael 125 Raphael NES 75 Taurus Layout 20 Installing TCAD Products and Utilities 31 6 Table 31 3 TCAD Disk Requirements Continued Product Disk MB Taurus Medici 250 Taurus Tsuprem4 125 Taurus Visual 125 Taurus WorkBench 355 Running the Installation Script If you are installing from a file retrieved from the FTP site make sure the file has the correct file permissions chmod 755 product_version platform install If you are installing from CD mount the CD and change directory to the CD drive Contact your system administrator if you require assistance in mounting the CD Next you must run the installation script product_version_platform_install The installation script creates the appropriate directories and installs the product During execution of the script several actions take place and some require you to respond to prompts 1 The installation script prompts you for your TCAD directory Enter the full path to your TCAD directory The installation script then extracts the product into your TCAD directory Installing TCAD Products and Utilities 31 7 2 Upon successful completion of the installation the script disp
66. aced with the platform you installed Installing TimeMill version U 2003 03 19 2 The CSHRC_ platform file sets the path for Nanosim and the NanoSim man pages set path install_directory platform ns bin Spath setenv MANPATH install_directory doc ns man SMANPATH where install_directory is the directory where the tool has been installed If you don t source the CSHRC_ platform file copy the preceding line and set the path from that file If you are using the Bourne Korn or Bash shell add the following lines to the profile kshrc or bashrc file PATH install_directory platform ns bin PATH export PATH MANPATH install_directory doc ns man SMANPATH export MANPATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Installing TimeMill version U 2003 03 19 3 Verifying the TimeMill Installation To verify the TimeMill installation 1 Make sure you are in a directory where you have read write privileges ed HOME Invoke the tool by entering the following command timemill If you see information about the product version production date and copyright the installation was successful Installing TimeMill version U 2003 03 19 4 20 Installing VCS version 7 0 2 This chapter contains the following sections e Installing the Software e Setting the Environment Variables e Verifying the VCS and VCSi Installation e Customer
67. ading and Installing the Software 2 9 Note To perform an overlay installation for TetraMAX enter tx for TetraMAX when you are prompted to select the product you want to install To perform a stand alone installation enter txs for TetraMAX stand alone Example 2 1 Synopsys Media Installation Script for the Synthesis Tools Synopsys Media Installation Instructions The list within shows the choices for a given option The entry within shows the default selection when you hit the Return key You can cancel the installation by by entering quit when prompted for input The current mounted Synopsys CD file system is V 2003 12 VERSION V 2003 12 PRODUCTS syn sf3 sf4 PLATFORMS sparcOs5 PART NUMBER XXXXXX Install V 2003 12 release y n yl y Enter the full path to the directory where you want to install Synopsys V 2003 12_syn products If the directory does not exist it will be created usr synopsys usr synopsys syn_V 2003 12 Creating Synopsys root directory usr synopsys syn_V 2003 12 Select Synopsys product s to install syn Core Synthesis Tools sf3 Synopsys Integrator for Falcon Framework MentorC sf4 Synopsys Integrator for Falcon Framework MentorD Enter the list of product s to install syn sf3 syn sf 3 Product s selected syn sf3 Platform Independent Package for a particular product contains support files that are common to all the platforms Dow
68. ar the files cd usr synopsys hspice gzip dc hspice_version_platform tar gz tar xvf If you don t want to see the list of unpacked files omit the v from xvf For other methods of handling tar files See Performing EST Installation on page 2 6 Note This creates a subdirectory in the HSPICE installation directory For example usr synopsys hspice version In the remainder of this chapter this subdirectory is referred to as the installation directory or installdir 5 To set the file permissions on the new directory tree and its contents enter chmod R 755 usr synopsys hspice 6 Remove the hspice version platform tar gz file rm hspice_version_platform tar gz 7 Configure HSPICE and AvanWaves for your site Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 4 8 Verify the HSPICE and AvanWaves installations 9 For each user set the required environment variables To configure the tools verify the installations and set the environment variables for each user see the following sections Configuring HSPICE and AvanWaves for UNIX and Linux To configure HSPICE and AvanWaves for UNIX and Linux platforms 1 2 Verify the platform on which you want to configure the products Invoke the configuration program by entering installation_directory bin config The Configure Products dialog box appears If you want to configure AvanWaves select Configure AvanWaves
69. ation see Supported Platforms and Operating Systems on page 1 2 Table 31 1 Supported Platforms Operating Systems and Keywords Platform Operating system Synopsys platform keywords Window environment HP HP UX 11 0 11 hp32 32 bit mode CDE Sun Solaris 8 9 sparcOS5 32 bit mode CDE sparc64 64 bit mode IBM AIX 4 3 3 rs6000 CDE Intel IA 32 Red Hat Linux 7 2 linux 32 bit mode GNOME DEC ALPHA Digital UNIX 4 0 alpha64 TCAD products are available on CD or by FTP download Obtain the appropriate binary executable files for your operating system Installing TCAD Products and Utilities 31 2 Table 31 2 lists the version U 2003 09 U 2003 06 and U 2003 03 TCAD products and their supported platforms For the latest product specific platform information see the release notes for your tool Table 31 2 TCAD Products and Supported Platforms Product Version Platform keyword Aurora U 2003 09 sparcOS5 hp32 linux rs6000 alpha64 Raphael U 2003 09 sparcOS5 sparc64 hp32 rs6000 alpha64 Raphael NES U 2003 03 sparcOS5 hp32 rs6000 Taurus Layout U 2003 09 sparcOS5 hp32 rs6000 alpha64 Taurus Medici V 2003 12 sparcOS5 hp32 rs6000 linux alpha64 Taurus TSuprem4 V 2003 12 Taurus Visual U 2003 09 Taurus Workbench U 2003 09 sparcOS5 hp32 rs6000 linux alpha64 sparcOS5 hp32 rs6000 alpha64 sparcOS5 hp32 rs6000 alpha64 1 These products might require government issued export licenses prior
70. bin SPATH export PATH Installing VCS version 7 0 2 20 4 3 Optional To include the optional utilities shipped with VCS in the path If you are using the C shell enter set path VCS_HOME bin VCS_HOME VCS_HOME bin vcs platform bin VCS_HOME VCS_HOME bin vcs platform util path lf you are using the Bourne shell enter PATH SVCS_HOME bin VCS_HOME VCS_HOME bin vcs platform bin VCS_HOME VCS_HOME bin vcs platform util SPATH export PATH Setting the SNPSLMD_LICENSE FILE or LM LICENSE FILE Environment Variable To enable VCS to check out a license you must set the SNPSLMD_LICENSE_FILEorthe LM LICENSE FILE environment variable e If you are using the C shell enter the following line setenv LM_LICENSE_FILE 27000 my_server e If you are using the Bourne shell enter these lines SNPSLMD_LICENSE_FILE 27000 my_server export SNPSLMD_ LICENSE FILE Installing VCS version 7 0 2 20 5 The port and host name variables correspond to the TCP port and license server host name specified in the SERVER line of the Synopsys license file To ensure better performance it is recommended that you use port host rather than using the path to the license file Each license file can contain licenses for many packages from multiple vendors You can specify multiple license files by separating each entry with a colon Verifying the VCS and VCSi Installation To ve
71. c file By obtaining a current site copy of the veriuser c file you can be sure to include any current site modifications when you modify this file To install VPOWER 1 Change to the Synopsys vpower directory 2 Modify a copy of your site veriuser c file 3 Link the VPOWER user tasks to the simulation executable file 4 Copy the linked executable file The following sections describe these steps Installing the Synopsys Synthesis Tools version V 2003 12 3 12 Changing to the Synopsys power Directory All directories listed are relative to the root of the vpower directory SYNOPSYS auxx syn power vpower To change to the Synopsys vpower directory 1 Make sure the environment variable SYNOPSYS Is set echo SSYNOPSYS If it is not set set it to the correct value setenv S SYNOPSYS root_directory Change to the Synopsys vpower directory cd SYNOPSYS auxx syn power vpower Modifying the veriuser c File To modify the veriuser c file to define the new toggle count utilities 1 Change to the vxl vxl sample directory and review the sample veriuser c file which shows the edits you will have to make cd vxl vxl sample Copy your current site version of veriuser c into the sample directory To copy veriuser c you must know the directory location of your central Verilog distribution cp site_location_dir_path veriuser c By using a current site copy of veriuser c you ensure that any existing cu
72. ck size A stack size that is larger than the default 8 192 KB can cause the data size to be smaller than required Because the stack size is taken at the beginning of the process it uses memory that would normally be available for data Therefore you should set the stack size higher than the default only when absolutely necessary Troubleshooting 24 3 Most system administrators do not adjust the limits unless they are confronted with problems If you do not adjust the limits it is possible for a tool requiring a lot of swap space such as Design Compiler to experience an out of memory problem Note however that it is possible to extend memory physical and swap space For more information see Accessing Memory Beyond 2 GB With 32 Bit Synopsys Tools on page 1 13 What Should Do When an out of memory Error Occurs Make sure that you are not running out of swap space on the system Use the swap 1 command for Sun SPARC systems to obtain swap space information For example o swap l swapfile dev swaplo blocks free dev dsk c0t3d0s1 32 25 8 822520 628872 To determine available swap space on systems other than Sun SPARC contact your system administrator If you have enough swap space but still encounter OS limits use the limit command to find out what the dat asize variable is set to for all machines except HP The 1imit command displays user level limits limit cputime unlimited filesi
73. cter The prpdev file is located in your TCAD directory in program_version platform Note The pr notation in prpdev refers to the product code md dv and so on that you are using See Table 31 5 on page 31 12 Specifying a Graphics Device With TSUPREM 4 you can specify the graphics device in the input file with the DEVICE parameter on the OPTION statement For example the following statement sets the graphics device to X OPTION DEVICE X If you do not specify a graphics device in the input file the DEFPDEV environment variable is used if it is set You can set DEFPDEV to specify the graphics device by entering the following command setenv DEFPDEV graphics device If you are using the Bourne or Korn shell you can use DEFPDEV to specify a graphics device by entering the following command DEFPDEV graphics device export DEFPDEV If you are using the C shell you can set DEFPDEV so that the X graphics device is used by entering the following command Installing TCAD Products and Utilities 31 15 setenv DEFPDEV x Note The graphics device must be entered in lowercase letters By setting the value of the DEFPDEV environment variable you can set the graphics device to any device you want to use without disrupting work in progress by other TCAD software users With TSUPREN 4 if neither OPTION nor DEFPDEV is specified TSUPREM 4 checks the TERM environment variable TSUPREM 4 looks for the graphics
74. d see Acquiring a License on page 1 15 12 1 Installing the Software To download and install PathMill from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the PathMill software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 2 on page 2 13 shows a Synopsys media installation script for PrimeTime PathMill is installed in a similar manner PathMill is a stand alone product and cannot be installed over an existing Synopsys product including a prior version of PathMill You must create a new directory for PathMill Setting Up PathMill for Each User To set up a new PathMill tool user add the PathMill directory containing the executable file to the PATH environment variable If you are using the C shell add the following line to the cshrc file set path S SYNOPSYS platform pm bin path If you are using the Bourne Korn or Bash shell add the following line to the profile or kshrc file PATH SSYNOPSYS platform pm bin PATH export PATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Installing PathMill version V 2003 1 2 12 2 Verifying the PathMill Installation To verify the PathMill installation 1 Make sure you are in a directory where you have read write privileges ed HOME 2 Invoke
75. d for most designs Larger designs might require more memory Installing FPGA Compiler Il version T 2003 09 FC3 8 on Windows Platforms 10 2 Installing FPGA Compiler Il You can install FPGA Compiler Il on a PC running Windows by downloading the tool from the Web or installing it from the CD Note Make sure that your licensing software is installed For information on Synopsys Common Licensing SCL software see Acquiring a License on page 1 15 To install FPGA Compiler II from the Web e Goto http www synopsys com products fpga download_fc2 html and follow the instructions To install FPGA Compiler II from the CD do the following 1 Insert the FPGA Compiler II CD into your computer s CD drive In most cases the setup program automatically starts If the setup program does not start automatically run setup exe from the CD directory 2 Follow the instructions on the screen As you move through the installation screens note the following You can install a subset of the available target devices to save disk space To do this select Custom in the Setup Type dialog box and follow the instructions Installing FPGA Compiler Il version T 2003 09 FC3 8 on Windows Platforms 10 3 The program installation directory path cannot contain space characters Enabling Online Document Readers The FPGA Compiler II User Guide is available online in Portable Document Format PDF The setup program installs thi
76. d to TCAD products and how they are specified with parameters of program statements Graphics Device Hierarchy With TSUPREM 4 the graphics device used is determined as follows e lf agraphics device is specified in the input file with the DEVICE parameter on the OPTION statement TSUPREM 4 uses that device e Otherwise if the DEFPDEV environment variable is defined TSUPREM 4 uses its value as the graphics device e Otherwise if the TERM environment variable is defined TSUPREM 4 uses its value as the graphics device e Otherwise TSUPREM 4 uses the default device specified in the s4pcap file which is initially set to ps for Postscript The s4pcap file contains a description of each device known to the program You can modify the file to make the default device refer to any available real plotting device The default device specified in the s4pcap file is used if neither DEFPDEV nor TERM is defined With the other simulators the graphics device used is determined as follows e lf agraphics device is specified in the input file with the DEVICE parameter on the PLOT statement that device is used Installing TCAD Products and Utilities 31 14 e Otherwise if the DEFPDEV environment variable is defined its value is used as the graphics device e Otherwise the default graphics device is used The default graphics device is defined by the first line in the prpdev file that contains an asterisk as the first nonblank chara
77. device specified by TERM in the s4pcap file If the graphics device is not found and neither OPTION nor DEFPDEV is specified TSUPREM 4 prints the following messages Plot device vt100 not found in s4pcap file Plotting to default device in s4pcap file In the first message vt 100 is the name of the device to which TERM is set With TSUPREN 4 if OPTION is not used and neither DEFPDEV nor TERM Is set TSUPREM 4 uses the default graphics device set in the s4pcap file By default the graphics device is set to ps in the s4pcap file With most other simulators you can specify the graphics device in the input file with the DEVICE parameter on the PLOT statement For example the following statement sets the graphics device to X PLOT 2D TITLE EXAMPLE DEVICE X With the other TCAD simulators if the PLOT statement does not specify a graphics device and DEFPDEV is not set the simulator uses the default graphics device The default graphics device is defined by Installing TCAD Products and Utilities 31 16 the first line in the prpdev file that contains an asterisk as the first nonblank character The prpdev file is located in your TCAD directory in program_version library For example if you want to change the default graphics device from Sun to X edit the prodev file and move the asterisk from the Sun entry to the X entry Before modification SUN 29 20 32 I SUN 29 20 32 X 30 2
78. directory see Creating the Synopsys Root Directory on page 1 18 Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 16 1 Installing the Software To download and install RailMill from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the RailMill software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 1 on page 2 10 shows a Synopsys media installation script for the synthesis tools RailMill is installed in a similar manner RailMill is a stand alone product and cannot be installed over an existing Synopsys product including a prior version of RailMill You must create a new directory for RailMill Setting Up RailMill for Each User To set up a new RailMill tool user e If you are using the C shell source the CSHRC_ platform file located in the install directory cd install_directory source CSHRC_platform oe The install script for RailMill creates a CSHRC_platform file for each platform installed The term platform is replaced with the platform you installed The CSHRC_ platform file contains the line set path install_directory platform rm bin Spath Installing RailMill version U 2003 03 16 2 where install_directory is the directory where the tool has been installed
79. e appropriate command for your operating system For example enter umount cdrom Installing VHDL Simulation Scirocco version 2002 12 2 22 3 Note If you are running the volume management daemon use the eject command to unmount the CD Setting the Environment Variables This section discusses the following environment variables e SYNOPSYS_SIM e SNPSLMD_ LICENSE _ FILE e LM_LICENSE_FILE It is recommended that you place these variables in your HOME cshre or HOME profile file as your default settings Setting the SYNOPSYS_SIM Environment Variable Set the SYNOPSYS_SIM environment variable in the shell that you are using in which the root_directory argument is the name of the Scirocco root directory If you are using the C shell enter setenv SYNOPSYS SIM u edatools vcs_mx scirocco2002 12 2 lf you are using the Bourne shell enter SYNOPSYS SIM u edatools vcs_mx scirocco2002 12 2 export SYNOPSYS SIM Installing VHDL Simulation Scirocco version 2002 12 2 22 4 Setting the SNPSLMD_LICENSE FILE or LM LICENSE FILE Environment Variable To enable Scirocco to check out a license you must set the SNPSLMD_LICENSE_FILE or the LM_LICENSE_FILE environment variable e If you are using the C shell enter the following line setenv SNPSLMD LICENSE_FILE 27000 my_server e If you are using the Bourne shell enter these lines SNPSLMD_LICENSE_FILE 27000 my_server export SNPSLMD_ LICE
80. e automatically installed with the PowerMill installation PowerMill can be installed as a stand alone installation or with any of the tools NanoSim and TimeMill it comes packaged with Setting Up PowerMill for Each User To set up a new PowerMill tool user e If you are using the C shell source the CSHRC_ platform file located in the install directory oe cd install_dir source CSHRC_platform oe The installation script for PowerMill creates a CSHRC_platform file for each platform installed The term platform is replaced with the platform you installed Installing PowerMill version U 2003 03 13 2 The CSHRC_ platform file sets the path for NanoSim and the NanoSim man pages set path install_directory platform ns bin Spath setenv MANPATH install_directory doc ns man SMANPATH where install_directory is the directory where the tool has been installed If you don t source the CSHRC_ platform file copy the preceding line and set the path from that file If you are using the Bourne Korn or Bash shell add the following lines to the profile or kshrc file PATH install_directory platform ns bin PATH export PATH MANPATH install_directory doc ns man SMANPATH export MANPATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Installing PowerMill version U 2003 03 13 3 Verifying the PowerMill Installation To verify the PowerMill installati
81. e licenses required for TetraWMAX options install the product and see the online Help for the Understanding TetraMAX License Usage Installing TetraMAX version V 2003 12 18 2 64 Bit Mode on HP UX and Solaris Platforms In 64 bit mode TetraMAX supports both the shell and GUI on HP UX and Solaris platforms To invoke TetraMAX ATPG in 64 bit mode use the 64 switch o tmax 64 other options An alternative method is to set the TMAX_64BIT environment variable to true or to any string other than null setenv TMAX 64BIT true tmax other options Stand Alone Installation TetraMAX stand alone is a complete installation of all TetraMAX applications It must be installed in its own directory and not over an existing synthesis release To perform stand alone installation 1 Download and install TetraMAX from the Web or by FTP as the described in Downloading and Installing the Software by EST on page 2 2 Or Install the files from the TetraMAX CD to your system as explained in Installing Product Files From a CD on page 2 7 Example 2 1 on page 2 10 shows a Synopsys media installation script for the synthesis tools TetraMAX is installed in a similar manner Installing TetraMAX version V 2003 12 18 3 Note When you are prompted to select the product you want to install enter txs to perform a stand alone installation 2 Make sure that your licensing software is installed For inf
82. e platform with the appropriate platform see Products and Supported Platforms on page 1 6 Exit the GUI by choosing File gt Exit in any GUI window Installing Floorplan Compiler version V 2003 12 7 4 Installing Formality version V 2003 12 This chapter contains the following sections Installing the Software Setting Up Formality for Each User Verifying the Formality Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 Define the SYNOPSYS environment variable see Defining the SYNOPSYS Environment Variable on page 1 19 Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 8 1 Installing the Software To download and install Formality from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the Formality software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 2 on page 2 13 shows a Synopsys media installation script for the PrimeTime tool Formaility is installed in a similar manner Formality is a stand alone product and cannot be installed over an existing Synopsys product including a prior version of
83. enter set path starsimxt_HOME bin path If you are using the Bourne shell enter PATH Sstarsimxt_HOME bin PATH export PATH Setting the LM_LICENSE_FILE Environment Variable To enable StarSim XT to check out a license you must set the LM_LICENSE_FILE environment variable For example e If you are using the C shell enter the following line setenv LM _LICENSE_FILE port hostname e If you are using the Bourne shell enter these lines set LM _LICENSE_FILE port hostname export LM _ LICENSE FILE Installing StarSim XT version V 2003 12 30 4 The port and host name variables correspond to the TCP port and license server hostname specified in the SERVER line of the Synopsys license file To ensure better performance it is recommended that you use port hostname rather than using the path to the license file Each license file can contain licenses for many packages from multiple vendors You can specify multiple license files by separating each entry with a colon Verifying the StarSim XT Installation To verify the StarSim XT installation 1 Make sure you are in a directory with read write privileges cd HOME 2 To run StarSim XT enter star_simxt filename where filename is the name of your netlist For example star_simxt ckt in StarSim XT directs the simulation output to an ASCII text file named ckt lis If you specified the HTML keyword in the configuration file StarSim XT directs the output to a fi
84. es from multiple vendors You can specify multiple license files by separating each entry with a colon Note To obtain your license key file from SmartKeys go to the SmartKeys Web page at http www synopsys com smartkeys Installing Hercules version V 2003 12 27 6 Setting Up Hercules for Each User To set up a new user you must e Source the cshrc or kshrc files e Enter the path information e Setup a license variable that points to the license server It is recommended that the following information be added to the cshrc kshrc or a Hercules source file 1 Add the Hercules executable files to your search path If you are using the C shell enter set path install_dir bin platform path If you are using the Bourne shell enter PATH install_dir bin platform PATH export PATH 2 Set the following licensing variable LM LICENSE FILE Installing Hercules version V 2003 12 27 7 Verifying the Hercules Installation To verify the Hercules installation 1 Make sure you are in a directory where you have read write privileges ed HOME Invoke the tool by entering o hercules V If you see information about the product version production date and copyright the installation was successful Installing Hercules version V 2003 12 27 8 28 Installing HSPICE version U 2003 09 on UNIX or Windows Platforms Note The installation instructions in this chapter are the most up
85. etting Up TimeMill for Each User Verifying the TimeMill Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 19 1 Installing the Software To download and install TimeMill from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the TimeMill software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 2 on page 2 13 shows a Synopsys media installation script for PrimeTime TimeMill is installed in a similar manner The TimeMill subtools ADFMI TurboWave and VTRAN are automatically installed with the TimeMill installation TimeMill can be installed as a stand alone installation or with any of the tools NanoSim and PowerMill it comes packaged with Setting Up TimeMill for Each User To set up a new TimeMill tool user e If you are using the C shell source the CSHRC_ platform file located in the install directory oe cd install_dir source CSHRC_platform oe The installation script for TimeMill creates a CSHRC_ platform file for each platform installed The term platform is repl
86. exist you must create one Uncompress and untar the files pwd usr synopsys vera gzip dc vera version platform tar gz tar xvf This will create a subdirectory in the Vera installation directory For example usr synopsys vera vera version platform In the remainder of this chapter this subdirectory is referred to as the Vera installation directory To set the file permissions on the new directory tree and its contents enter chmod R 755 usr synopsys vera Remove the vera version platform tar gz file rm vera version platform tar gz For each user set the required environment variables See Setting the Environment Variables on page 21 3 Installing Vera version 6 2 0 21 2 Setting the Environment Variables This section discusses the following environment variables e VERA HOME e SNPSLMD_LICENSE_FILE e ILM LICENSE FIGE It is recommended that you place these variables in your HOME cshrc or HOME profile file as your default settings Setting the VERA_HOME Environment Variable 1 Set the VERA_HOME environment variable to point to your Vera installation directory lf you are using the C shell add the following line setenv VERA_HOME install_directory lf you are using the Bourne shell enter these lines VERA_HOME install_ directory export VERA_HOME 2 Add VERA_HOME bin to your search path If you are using the C shell enter set path VERA_HOME bin path l
87. f Installing VirSim version 4 3 A 2 Setting Up VirSim for Each User To set up a new VirSim tool user add the VirSim directory containing the executable file to the PATH environment variable 1 Set the VIRSIMHOME environment variable to point to the installation directory For example If you are using the C shell enter setenv VIRSIMHOME virsim_install dir If you are using the Bourne Korn or Bash shell enter VIRSIMHOME virsim_install_dir export VIRSIMHOME Update your PATH environment variable as follows If you are using the C shell enter set path VIRSIMHOME bin path If you are using the Bourne Korn or Bash shell enter PATH SVIRSIMHOME bin SPATH export PATH Installing VirSim version 4 3 A 3 Setting the SNPSLMD_LICENSE FILE or LM LICENSE FILE Environment Variable To enable VirSim to check out a license you must set the SNPSLMD_ LICENSE FILE or the LM LICENSE FILE environment variable as follows e If you are using the C shell add the following line setenv SNPSLMD_LICENSE_FILE port hostname e If you are using the Bourne Korn or Bash shell enter these lines SNPSLMD_LICENSE_FILE port hostname export SNPSLMD_LICENSE_FILE The port and host name variables correspond to the TCP port and license server host name specified in the SERVER line of the Synopsys license file To ensure better performance it is recommended that you use the port host name rather than using the path t
88. f you are using the Bourne shell enter PATH SVERA_HOME bin SPATH export PATH Installing Vera version 6 2 0 21 3 Setting the SNPSLMD_LICENSE FILE or LM _ LICENSE FILE Environment Variable 1 To enable Vera to check out a license set the SNPSLMD_ LICENSE FILE or the LM LICENSE FILE environment variable If you are using the C shell add the following line setenv SNPSLMD LICENSE_FILE port hostname lf you are using the Bourne shell enter these lines SNPSLMD LICENSE_FILE port hostname export SNPSLMD_LICENSE_FILE The port and host name variables correspond to the TCP port and license server host name specified in the SERVER line of the Synopsys license file To ensure better performance it is recommended that you use port host rather than using the path to the license file Each license file can contain licenses for many packages from multiple vendors You can specify multiple license files by separating each entry with a colon Customer Support You can get support for Vera from the following locations For technical Issues enhancement requests and feedback contact Customer Support at vera support synopsys com For documentation Issues send e mail to vera doc synopsys com Installing Vera version 6 2 0 21 4 For general information on Synopsys licensing see http solvnet synopsys com keys For information on Vera licensing see e The Vera Installation Guide which is packaged in Port
89. g the CD ics i og etl ee ad out eed thas Installing the Synopsys Synthesis Tools version V 2003 1 2 SYNINESIS lOOISs 4 Acct ead ace Soe amen ld bee Installing the Software 2 0 0 0 cee ee 3 4 Configuring the Synthesis Tools 02020e eee 3 4 Setting Up the Synthesis Tools for Each User 3 5 Setting Up the Systemwide Defaults 3 7 Setting up SystemC Compiler for Each User 3 8 Configuring the Browser for Physical Compiler and Design Vision Online Help 3 9 Installing Optional Tools 0 00 c eee ee 3 10 Installing Synopsys Integrator for Falcon Framework 3 10 Installing Power Compiler VPOWER 2 3 11 Verilog XL Simulator wands nacicecesd sa oa BURR E ee ee ee 3 11 VCS SIMUIBION 3 2 cave eee debe eos See ees eS 3 17 Using SCCBIS Tia eerde Ses 2486 Ue ee ae Ge A 3 19 Verifying the Synthesis Tools Installation 3 20 Installing AMPS version U 2003 03 Installing the Software 2 2 2 0 ee 4 2 Setting Up AMPS for Each User 0 0c cece aee 4 2 Verifying the AMPS Installation 000 0 eee eee 4 3 Installing Arcadia version U 2003 03 Installing the Software 2 2 2 ccc ee 5 2 Setting Up Arcadia for Each User 0 0000 eee eae 5 2 Verifying the Arcadia Installation 00000 5 3 vi Installing Cadabra version 7 0
90. h If you are using the Bourne Korn or Bash shell add the following line to the profile or kshrc file PATH SSYNOPSYS bin SPATH export PATH To set up the user environment by using an alias perform one of the following procedures Note that these examples are for the C shell Setups in other shells will differ e To set up the user environment by using an alias enter alias tmax SSYNOPSYS bin tmax e To set up the user environment by using a path enter set path SSYNOPSY bin path Installing TetraMAX version V 2003 12 18 6 To set up the user environment for using SoCBIST enter set path S SYNOPSYS bin S SYNOPSYS platform bin path Replace platform with the required platform Note If you used SSYNOPSYS_TMAxX to define the TetraMAX root directory set the user environment for SOCBIST as follows set path SYNOPSYS_TMAX bin SYNOPSYS platform bin path Verifying the TetraMAX Installation To verify installation of the TetraMAX tools 1 Make sure you are in a directory where you have read write privileges ed SHOME Invoke the TetraMAX GUI by entering the following command on a licensed machine o tmax If the GUI appears the installation was successful Installing TetraMAX version V 2003 12 18 7 Installing TetraMAX version V 2003 12 18 8 19 Installing TimeMill version U 2003 03 This chapter contains the following sections Installing the Software S
91. ha Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 2 Note When you use HSPICE with Windows platforms that use AMD Athlon CPUs only a single processor is supported Installing the Software on UNIX or Linux Platforms To install HSPICE and AvanWaves from the CD 1 5 Make sure you have enough disk space for HSPICE and AvanWaves installation For a full installation on one platform 120 MB is recommended To load the software enter path_to_cdrom install_dir synopsys_install The Synopsys Installation Program dialog box appears Enter the name of the installation directory in which you want to load the products Select the products and platforms that you want to load and then click Load After the loading is completed click Exit Note If you have problems reading the CD on the Solaris 7 platform contact Sun to obtain OS patch version 107465 04 or later kernel fs hsfs patch To install HSPICE and AvanWaves by electronic software transfer 1 If necessary create an HSPICE installation directory For example Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 3 mkdir p usr synopsys hspice 2 Change to the HSPICE installation directory o cd usr synopsys hspice 3 Download the HSPICE binary files to the installation directory You can get the latest HSPICE download instructions from the SolvNet Release Library 4 Uncompress and unt
92. his do the following e Set another variable for PrimeTime for example STATIC e Setthe PrimeTime SYNOPSYS variable in a tool specific setup file not in the profile or cshrc file e Create an alias for PrimeTime in the cshrc profile or bashrc files For example Installing PrimeTime version V 2003 12 15 2 For cshrc files alias pt_setup setenv SYNOPSYS path to PrimeTime_root echo PrimeTime tools setup For profile or bashrc files alias pt_setup set SYNOPSYS path to PrimeTime_root echo PrimeTime tools setup Execute the alias before executing PrimeTime To set up a new PrimeTime user 1 Add the PrimeTime directory containing the executable file to the PATH environment variable If you are using the C shell add the following line to the cshrc file set path S SYNOPSYS platform syn bin path If you are using the Bourne Korn or Bash shell add the following line to the profile kshrc or bashrc file PATH SSYNOPSYS platform syn bin SPATH export PATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Note If you are using another variable such as STATIC to define the PrimeTime root directory substitute that variable for SYNOPSYS in the remainder of this chapter Place a synopsys_pt setup file in the user s home directory If you are using the C shell enter Installing PrimeTime ve
93. his case you must rewrite it as a Bourne bin sh script Troubleshooting 24 6 Part Il Physical Implementation Astro Astro Interactive Ultra JupiterXT and Columbia Astro Rail Hercules HSPICE Star RCXT StarSim XT TCAD 20 Installing Astro Astro Interactive Ultra JupiterXT and Columbia Note The installation instructions in this chapter are the most up to date available at the time of production However changes might have occurred For the latest installation information see the product release notes or documentation The tool versions for this release are e Astro version U 2003 09 e Astro Interactive Ultra version U 2003 09 e JupiterXT version U 2003 09 e Columbia version V 2003 12 25 1 This chapter contains the following sections e Media Availability and Supported Platforms e Installing the Software e Setting Up Astro for a New User e Verifying the Astro Installation Media Availability and Supported Platforms The U 2003 12 version of the Astro tool is available on CD or by FTP download Obtain the appropriate binary executable files based on the operating system you need Table 25 1 shows the supported platforms for the U 2003 12 release Table 25 1 Supported Operating Systems and Platform Keywords Operating system Platform keyword Solaris 8 SUN 32 SUN 64 HP UX 11 0 11i HP 64 Red Hat Linux 7 2 IA 32 Installing Astro Astro Interactive Ultra JupiterXT and Columbia
94. hspice Encryption code XXX If you geta job concluded statement near the bottom of the listing the simulation was successful Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 8 Verifying the AvanWaves Installation To verify the AvanWaves installation 1 Change to the installation directory ed S installdir bin The Sinstalldir environment variable refers to the AvanWaves installation directory This variable is created when you source the cshrc meta file To start AvanWaves enter awaves amp Installing the Software on Windows Platforms This section describes how to install and set up the license server for HSPICE on a PC To run HSPICE your system must have A Pentium or compatible processor or later At least 64 MB of memory 128 MB or more is recommended A parallel port for the security key if you are using a dongle based license Windows NT Windows 2000 or Windows XP operating system Approximately 100 MB of free disk space for a full installation of HSPICE AvanWaves and MetaEncrypt Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 9 Installing With Windows Explorer To install HSPICE by using Windows Explorer 1 Insert the HSPICE CD into the CD drive 2 In Windows Explorer double click the CD drive icon 3 Double click the pchspice folder icon 4 Double click the Setup application icon 5 To install the software follow the screen p
95. ible request CD media To download the software follow these steps 1 Go to ftp synopsys com ftp ftp synopsys com 2 When prompted for a name and password enter your SolvNet logon name and password 3 At the ftp prompt set the transfer mode to binary ftp gt binary 4 Change directory to the revenue vault ftp gt cd rev 5 Change directory to the appropriate product directory for example a_tcad medici_version ftp gt cd product_directory 6 List the directory contents ftp gt dir 7 For each file that you want retrieve the file by using the get command get filename For example get tcad medici_version_platform install 8 After retrieving the product files quit the FTP session Installing TCAD Products and Utilities 31 5 ftp gt quit To request CD media e Log on to the SolvNet Web site http solvnet synopsys com and click the MediaDocs link Note Because of contract restrictions only certain sites are authorized to order CD media If you are not sure about your site s eligibility contact your Synopsys account manager Establishing a TCAD Directory Tree Ifa TCAD product has previously been installed on your system a TCAD directory with a name such as usr tcad should already exist If you are uncertain about the directory name contact your system administrator for assistance Ifa TCAD directory does not exist decide where to store the TCAD products on your system Consult T
96. ication number finding 1 18 SoBist pattern generation functionality 3 19 tool dependencies 3 19 SoCBIST 3 19 software downloading by FTP 2 4 from the Web 2 5 installing by electronic software transfer 2 6 from CD 2 7 SOLD 23 2 contents of CD ROM 23 5 installation CD 23 8 configuring for new user 23 9 electronic software transfer 23 7 options 23 6 partial 23 8 verifying 23 9 software for reading and searching 23 3 Star RCXT documentation 29 5 installing 29 2 media 29 2 setting up for each user 29 4 supported platforms 29 2 verifying installation 29 5 Star Sim XT documentation 30 6 downloading and installing 30 2 environment variables setting 30 3 starsimxt_HOME 30 4 license 30 4 media 30 2 supported platforms 30 2 verifying installation 30 5 swap space 1 12 24 4 Synopsys Common Licensing 1 15 acquiring a license 1 15 acquiring documentation 1 17 installing 1 17 obtaining keys 1 16 SYNOPSYS environment variable 1 19 Synopsys Integrator for Falcon Framework 3 10 Synopsys Online Documentation see SOLD Synopsys platform keywords 1 3 28 2 31 2 Synopsys power directory 3 13 Synopsys Qualified Runtime System Configuration 1 2 Synopsys root directory creating 1 18 ssynopsys_dc setup 24 6 synthesis tools configuring 3 4 installing 3 4 list 3 2 platform keyword 1 7 product ID 1 7 setting up for new users 3 5 verifying installation 3 20 system requirements disk space 1 8 FPGA Compiler Il on Windows 10 2 memory 1
97. icense file To ensure better performance it is recommended that you use port host rather than using the path to the license file You can specify multiple license files by separating each entry witha colon Installing Cadabra version 7 0 6 5 Verifying the Cadabra Installation To verify the Cadabra installation 1 Make sure you are in a directory where you have read write privileges ed SHOME If you are using a display that is not local set the DISPLAY environment variable setenv DISPLAY my_display 0 0 Invoke the tool by entering tool_name Replace too _name with abracad abramap or kazam If the product GUI appears the installation was successful 4 Exit the GUI by choosing File gt Exit in any GUI window Customer Support For information about accessing customer support see Customer Support on page xxi You can also send an e mail message to Cadabra Support at cadabrasupport synopsys com Installing Cadabra version 7 0 6 6 Installing Floorplan Compiler version V 2003 12 This chapter contains the following sections Installing the Software Setting Up Floorplan Compiler for Each User Verifying the Floorplan Compiler Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 Define the SYNOPSYS env
98. ign Star Star DC Star MS Star MTB Star Power Star Rail Star RC Star RCXT Star Sim Star Sim XT Star Time Star XP SWIFT Taurus Taurus Device Taurus Layout Taurus Lithography Taurus OPC Taurus Process Taurus Topography Taurus Visual Taurus Workbench TimeSlice TimeTracker Timing Annotator TopoPlace TopoRoute Trace On Demand True Hspice TSUPREM 4 TymeWare VCS VCS Express VCSi Venus Verification Portal VFormal VHDL Compiler VHDL System Simulator VirSim and VMC are trademarks of Synopsys Inc Service Marks DesignSphere MAP in SVP Caf and TAP in are service marks of Synopsys Inc SystemC is a trademark of the Open SystemC Initiative and is used under license AMBA is a trademark of ARM Limited ARM is a registered trademark of ARM Limited All other product or company names may be trademarks of their respective owners Printed in the U S A Document Order Number 13486 000 SA Installation Guide version V 2003 12 Contents What s New in This Release 00000 ee eae About This Guide 625 5422 poh ote eee eee eo ee SE ORES A eed Customer Support nsss sssaaa aap ies d Haat edad Jakjees Part Logical and Physical Synthesis Simulation Power Test and Verification 1 Preparing for Installation Checking Your Hardware and Software Configuration Installation Changes 00 cece eee Supported Platforms and Operating Systems HP UX Requireme
99. ile permissions on the new directory tree and its contents enter chmod R 755 usr synopsys star rext Remove the platform_star rcxt version tar gz file rm platform_star rcext version tar gz Installing Star RCXT version V 2003 12 29 3 Setting Up Star RCXT for Each User To set up a new tool user each user must e Source cshrc or kshrc e Enter the path information e Setup a license variable that points to the license server It is recommended that the following information be added to the cshrc kshrc or an Star RCXT source file 1 Add the Star RCXT executable files to your search path lf you are using the C shell set path installation_directory bin path If you are using the Bourne shell PATH installation_directory bin SPATH export PATH 2 Set the following licensing variable LM LICENSE FILE Installing Star RCXT version V 2003 12 29 4 Verifying the Star RCXT Installation To verify the Star RCXT installation 1 Make sure you are in a directory with read write privileges ed HOME Run the Star RCXT GUI on each installed platform by entering the following command StarXtract gui The GUI will appear on your screen 3 Exit the GUI by choosing File gt Exit in any GUI window Customer Support For information about using Star RCXT see the Star RCXT User Guide For information about accessing Star RCXT documentation see Related Publications on page xix For inf
100. iler Il 9 4 10 4 operating system additional requirements for HP UX 1 4 patches 1 2 supported 1 2 P PathMill installing 12 2 platform keyword 1 7 product ID 1 7 setting up for new user 12 2 verifying installation 12 3 platforms 64 bit 1 4 installing additional 1 5 installing multiple 1 5 PLI table file modifying 3 17 Power Compiler VPower installing 3 11 PowerMill installing 13 2 platform keyword 1 7 product ID 1 7 setting up for new user 13 2 IN 3 verifying installation 13 4 prerequisites for installing products creating root directory 1 18 setting environment variable 1 19 PrimePower platform keyword 1 7 setting up for new user 14 2 verifying installation 14 3 PrimeTime installing 15 2 media installation script 2 13 platform keyword 1 7 setting up for new user 15 2 verifying installation 15 4 product files downloading by FTP 2 4 from the Web 2 5 installing by electronic software transfer 2 6 from CD 2 7 types of packaging 2 2 untarring 2 6 untarring and uncompressing 2 6 R RailMill installing 16 2 platform keyword 1 7 product ID 1 7 setting up for new user 16 2 verifying installation 16 3 root directory creating 1 18 S Scirocco see VHDL Simulation Scirocco SCL see Synopsys Common Licensing script Synopsys media installation for PrimeTime 2 13 for synthesis tools 2 10 IN 4 semaphores IPC 17 8 setprivgrp 1 4 setting defaults synthesis tools 3 7 System Studio 17 3 site identif
101. ilog_bin_location directory for group access VCS Simulator The following procedure describes how to link VPOWER to a version of VCS that contains the standard features you normally use at your site and includes the toggle count utilities needed for Power Compiler Note The PLI library has been tested with VCS version 3 0 and later versions To install VPOWER 1 Change to the Synopsys vpower directory 2 Modify a copy of the PLI table file 3 Compile the simulation executable file The following sections describe these steps Changing to the Synopsys vpower Directory All directories listed are relative to the root of the vpower directory SYNOPSYS auxx syn power vpower Installing the Synopsys Synthesis Tools version V 2003 12 3 17 1 Make sure the environment variable SSYNOPSYS Is set echo SSYNOPSYS If it is not set set it to the correct value setenv S SYNOPSYS synthesis_root_directory 2 Change to the Synopsys vpower directory cd S SYNOPSYS auxx syn power vpower Modifying the PLI Table File To modify the PLI table file vpower tab to define the new toggle count utilities 1 Change to the vcs vcs sample directory and review the sample vpower tab file which shows the edits you will have to make cd ves vcs sample 2 Make the necessary changes to the vpower tab file Compiling the Simulation Executable File VCS is a compiled simulator so you must compile your designs along with VCS libra
102. ing does not have restrictions that prevent you from using more than 2 GB of memory Preparing for Installation 1 14 4 Create unlimited data size in the shell that you are using C Bourne Korn or Bash If there are systemwide limits on the data size you can create you can remove them or override them You can do this in one of two ways Enter one of the following commands For the C shell limit datasize 3800000 For the Bourne Korn or Bash shell ulimit S d 3800000 Modify the kernel of your server This approach allows everyone using your server to extend memory beyond 2 GB Note On HP UX systems you will see a data size of 2 GB This value is accurate After your process reaches the 2 GB limit the Synopsys product extends the address space Acquiring a License The Synopsys Common Licensing SCL system provides a single common licensing base for all Synopsys tools The SCL software and the documentation describing how to install and configure it are separate from the tools that use it Before you can use the Synopsys tools you must do the following e lf you have not already done so retrieve your license keys from the SmartKeys Web page at http solvnet synopsys com smartkeys Preparing for Installation 1 15 Install the SCL software Note Installation of Synopsys tools and SCL is not order dependent You can install SCL before or after you install your Synopsys tools However you can
103. ired then clicking Enter a Call to the Support Center e Send an e mail message to your local support center E mail support_center synopsys com from within North America Find other local support center e mail addresses at http www synopsys com support support_ctr e Telephone your local support center Call 800 245 8005 from within the continental United States Call 650 584 4200 from Canada Find other local support center telephone numbers at http www synopsys com support support_ctr Part l Logical and Physical Synthesis Simulation Power Test and Verification Synthesis AMPS Arcadia Cadabra Floorplan Compiler Formaility FPGA Compiler II NanoSim PathMill PowerMill PrimePower PrimeTime RailMill System Studio TetraMAX TimeMill VCS Vera VHDL Simulation Scirocco SOLD Preparing for Installation This chapter provides information about steps to complete before you install Synopsys tools The chapter contains the following sections e Checking Your Hardware and Software Configuration e Acquiring a License e Finding Your Site Identification Number e Creating the Synopsys Root Directory e Defining the SYNOPSYS Environment Variable Checking Your Hardware and Software Configuration You must check your hardware and software configuration including patch requirements before you attempt to load any Synopsys tools Installation Changes Beginning with the
104. ironment variable see Defining the SYNOPSYS Environment Variable on page 1 19 7 1 e Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 Installing the Software To download and install Floorplan Compiler from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the Floorplan Compiler software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 1 on page 2 10 shows a Synopsys media installation script for the synthesis tools Floorplan Compiler is installed in a similar manner Setting Up Floorplan Compiler for Each User To set up a new Floorplan Compiler tool user add the Floorplan Compiler directory containing the executable file to the PATH environment variable If you are using the C shell add the following line to the cshrc file set path SSYNOPSYS platform fpc bin path If you are using the Bourne Korn or Bash shell add the following line to the profile or kshrc file PATH SSYNOPSYS platform fpc bin SPATH export PATH Installing Floorplan Compiler version V 2003 12 7 2 Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Configuring the Browser for Floorplan Compiler Online Help The Floorplan Compiler online Help system is
105. l enter pps Make sure that your licensing software is installed For information on SCL software see Acquiring a License on page 1 15 Setting Up PrimePower for Each User To set up a new PrimePower tool user add the PrimePower directory containing the executable file to the PATH environment variable Installing PrimePower version V 2003 12 14 2 If you are using the C shell add the following line to the cshrc file set path install_directory platform syn bin path If you are using the Bourne Korn or Bash shell add the following line to the profile or kshrc file PATH install_directory platform syn bin PATH export PATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 Verifying the PrimePower Installation To verify the PrimePower installation 1 Make sure you are in a directory where you have read write privileges cd HOME Invoke the tool by entering the following command pp_shell If you see information about the product version production date and copyright the installation was successful Exit pp_shell by entering exit on the command line Run the PrimePower GUI on each installed platform by entering the following command primepower amp Exit the GUI by choosing File gt Exit in any GUI window Installing PrimePower version V 2003 12 14 3 Installing PrimePower version V 2003 12 14 4 19 Installing
106. l enter these lines set LM _LICENSE_FILE port hostname export LM _LICENSE_FILE 3 Source the cshrc meta or kshrc meta file For C shell users enter source installation_directory bin cshrc meta For Bourne or Korn shell users enter installation_directory bin kshrc meta Verifying the HSPICE and AvanWaves Installation After you set up the licensing and HSPICE software packages do the following e For C shell users enter source installation directory bin cshrc meta e For Bourne or Korn shell users enter installation directory bin kshrc meta If this step fails or if the cshrc meta file does not exist the installation program failed To find the problem review the installation log file installation_directory bin synopsys_config log_pid Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 7 Verifying the HSPICE Installation To verify the HSPICE installation 1 Make sure you are in a directory where you have read write privileges cd HOME The Sinstalldir environment variable refers to the HSPICE installation directory This variable is created when you source the cshrc meta file 2 Torun a demonstration simulation enter o hspice installdir demo hspice bench demo sp gt demo lis 3 To view the simulation output enter vi demo lis 4 Ifyou are able to get a license you will see a message about licenses near the top of the listing lic Checkout
107. l_dir bin ia 32 lmgrd c usr local flexlm licenses license dat 1l usr local flexlm licenses license log where nstall_diris the directory where you installed the software For more information about the license server see www synopsys com keys or the FLEX m End User Manual Setting Up Astro for a New User This section describes how to set up a local machine for Solaris so that it can access the Synopsys software Perform this procedure for each machine on the network 1 To set up your machine update your environment variables by adding the following variables in your cshrc file setenv LM LICENSE FILE usr local flexlim licenses license dat SLM LICENSE FILE set path install_dir bin platform path Installing Astro Astro Interactive Ultra JupiterXT and Columbia 25 4 where install_diris the directory in which the Synopsys software is installed and platform is the appropriate platform Update your path variable by entering source cshre Make sure the XKeysymDB file resides in or is linked from usr lib X11 Verifying the Astro Installation To verify the Astro installation 1 Make sure you are in a directory where you have read write privileges cd HOME Invoke the tool by entering the following command o Astro If you see information about the product version production date and copyright the installation was successful Installing Astro Astro Interactive Ultra JupiterxT and
108. lays a summary A copy of this summary as well as a log of your responses to the system prompts is located in the install_ program log file in the program directory Caution You must add the tcad bin directory to your search path if it is not already there For example if your TCAD directory is usritcad your search path must include usr tcad bin For details see Setting Up Your Search Path next After the installation is completed the directory tree shown in Table 31 4 exists as subdirectories of the TCAD directory Table 31 4 TCAD Subdirectories Subdirectory Contents bin program_version utility license license_tma Contains links to the TCAD executable files Contains the TCAD product files and directories including the install_program product installation script Contains various utilities for use with TCAD products For a discussion of the contents of the utility directory see the TCAD utility Directory on page 31 21 Contains the TCAD Network License Software and the license dat license data file Contains the TCAD Network License Software for all supported platforms in compressed tar format Installing TCAD Products and Utilities 31 8 Setting Up Your Search Path A search path is a list of directory paths The system searches through directories to find an executable file Each TCAD product user must have a search path that contains the TCAD bin directory This
109. le named ckt html Installing StarSim XT version V 2003 12 30 5 Customer Support A new e mail alias has been created for Star SimXT users To subscribe to this mailing list send an e mail to starsim user request synopsys com and include subscribe in the body of the e mail To unsubscribe type unsubscribe For information about using StarSim XT see the Star Sim XT User Guide To find out how to access StarSim XT documentation see Related Publications on page xix For information about contacting Customer Support see Customer Support on page xxi Installing StarSim XT version V 2003 12 30 6 31 Installing TCAD Products and Utilities Note The installation instructions in this chapter are the most up to date available at the time of production However changes might have occurred For the latest installation information see the product release notes or documentation in SolvNet For tool versions for this release see Table 31 2 on page 31 3 This chapter includes the following sections e Supported Platforms and Media Availability e Installing TCAD Products e Setting the User Environment to Find the TCAD License e Running TCAD Products e Using Graphics Devices 31 1 e Troubleshooting e TCAD Utilities Supported Platforms and Media Availability Table 31 1 lists the supported platforms operating systems and corresponding Synopsys platform keywords for this release For detailed inform
110. ling the Software 2 14 Synopsys License Administrator is a person who must be contacted for Synopsys product related administrative tasks at your site Local Synopsys License Administrator Hit return for customer License Administrator Contact is the current phone number and or Email address of customer License Administrator Contact Hit return for and or user email Created site file usr synopsys pts_V 2003 12 admin license site_info Installation is complete To use this software you must be running the Synopsys Common Licensing SCL version 8 4 daemon snpsimd on your license server For more information on SCL 8 4 see the Synopsys Licensing QuickStart Guide at http www synopsys com keys For any post installation setup requirements see the product specific chapters in the Installation Guide at http www synopsys com support Install_Guide html Thank you Unmounting the CD To unmount the CD 1 Move to another directory For example enter cd tmp 2 Unmount the CD by using the appropriate command for your operating system For example enter umount cdrom Note If you are running the volume management daemon use the eject command to unmount the CD 3 Remove the CD from the drive Downloading and Installing the Software 2 15 Note To run the Synopsys tools Synopsys Common Licensing SCL software must be installed For details about Synopsys licensing softwa
111. ling the Synopsys Synthesis Tools version V 2003 12 3 4 Setting Up the Synthesis Tools for Each User To set up a new synthesis tools user 1 Add the directory for the synthesis executable files to the PATH environment variable If you are using the C shell add the following line to the cshrc file set path SSYNOPSYS platform syn bin path If you are using the Bourne Korn or Bash shell add the following line to the profile kshrc or bashrc file PATH SSYNOPSYS platform syn bin SPATH export PATH Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 When you install the synthesis files a copy of the synthesis setup file is placed in SYNOPSYS admin setup synopsys_dc setup The synopsys_dc setup file contains the system defaults for the synthesis tools You can modify this file to customize the settings for your environment 2 Place a synopsys_ dc setup file in the user s home directory If you are using the C shell enter cp SSYNOPSYS admin setup synopsys_dc setup synopsys_dc setup If you are using the Bourne Korn or Bash shell enter cp SSYNOPSYS admin setup synopsys_dc setup SHOME synopsys_dc setup You can modify this file to customize the settings for each user Installing the Synopsys Synthesis Tools version V 2003 12 3 5 3 Touse agraphical user interface GUI such as Design Analyzer you must also add the X Window System executable
112. m bin snpslmd In this line platform is the operating system keyword see Table 1 1 on page 1 3 Make sure there are no blank lines and no leading or trailing spaces in the license file For all types of license files make sure that all System Studio users have read access to the key file Set the file permission for the key file with the following command chmod 644 CCSS_KEYSS ccss admin license CCSS keys Or if you have defined the symbol CCSS_KEYS use this command Installing System Studio version V 2003 12 17 7 chmod 644 SCCSS_ KEYS Then use the following command to check that the read access is correct ls 1 SSYNOPSYS CCSS ccss admin license CCSS keys You should see a report something like this rw r r 1 thisuser group 4623 Apr 26 11 09 ecss keys Insufficient Interprocess Communication IPC Semaphores When starting System Studio or DAVIS on Solaris 5 x platforms if you see the following report sem _ create gt semget gt IPC_CREATE No space left on device GMA failed FATAL Exec_ sparcOS5 ccss bin ccss_exec_ failed status 139 you need to increase the number of system semaphores Add the following command to the etc system file see the man page system 4 for details set semsys seminfo_semmnu 0x100 After you change the etc system file restart your system by using boot r Caution Changing the etc system file incorrectly will prevent the
113. mentation about using HSPICE and AvanWaves see the e AvanWaves User Guide e Device Models Quick Reference Guide e Elements and Device Models Manual e HSPICE Applications Manual e HSPICE Quick Reference Guide e HSPICE Signal Integrity Guide e HSPICE Simulation and Analysis User Guide e MOSFET Models Manual All documentation is available on SOLD or through Documentation on the Web Print versions are available only for the HSPICE Quick Reference Guide and the Device Models Quick Reference Guide For information about accessing the documentation see Related Publications on page xix For information about contacting Customer Support see Customer Support on page xxi If you cannot solve a problem use an editor to review the following files for system error messages e tmp pid synopsys_install log_pid which is generated during installation e tmp pid synopsys_config log_pid which is generated during configuration Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 14 29 Installing Star RCXT version V 2003 12 Note The installation instructions in this chapter are the most up to date available at the time of production However changes might have occurred For the latest installation information see the product release notes or documentation This chapter includes the following sections Media Availability and Supported Platforms Installing the Software Setting Up Star RCXT
114. mented Do not delete the solid directory it contains the SOLD User Guide Keep the remaining collection directories intact Do not remove files from them or move the files in a collection relative to each other Such modifications can cause hypertext links and the search mechanism to fail Verifying the SOLD Installation Verify the installation by opening SOLD To open SOLD issue the command SSYNOPSYS sold If SOLD is correctly installed this command invokes Acrobat and displays the SOLD welcome screen in the Acrobat window Configuring SOLD for Each User The search engine uses index files to perform full text search and retrieval on a document SOLD provides an index file index pdx with each collection When you open a document the associated index file is automatically available to the search engine However to search SOLD before opening a document you can manually make an index available to the search engine Installing Synopsys Online Documentation version V 2003 12 23 9 To manually make an index available to the search engine 1 Choose Edit gt Search gt Select Indexes in the Acrobat window 2 Click the Add button 3 Navigate to one of the collection directories for example SYNOPSYS doc online synth 4 Select the index pdx file 5 With the index pdx file selected click the Apply button The selected index is added to the list of available indexes For information about using SOLD see the
115. ms a full installation Most sites use a full installation for shared access by many users If disk space is at a premium you can create a partial installation by removing unused directories after the installation is complete see Partial Installation on page 23 8 Installing Synopsys Online Documentation version V 2003 12 23 6 Installing SOLD CDs on HP UX Platforms When SOLD is installed on HP UX platforms the entire content of the CD is not copied to the disk To copy all of SOLD you must download and install the following patches before installing SOLD For HP UX 11 00 PHCO_ 26449 PHKL_ 26450 PHKL_ 28060 For HP UX 11 11 11 i PHKL_28025 PHKL_26269 To download the patches go to http itrc hp com Electronic Software Transfer Installation To download and install SOLD from the Web or by EST follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To access the complete collections of SOLD download ssd1 and ssd2 The SOLD files use the following convention sold_V 2003 12 ssdl tar Z sold_V 2003 12 ssd2 tar Z Two additional SOLD CDs are available one for the Japanese version of SOLD and one specifically for System Studio customers e If you want to download only J SOLD download the sold_V 2003 12_jsd3 tar Z file e To download only System Studio SOLD download the sold_V 2003 12_ ssd4 tar Z file Installing Synopsys Online Documentation ver
116. nformation see Acquiring and Installing the Acrobat Reader Software on page 23 3 The online documentation for System Studio System Studio SOLD is distributed to System Studio customers on a separate CD The installation instructions in this chapter apply to both SOLD and System Studio SOLD Installing Synopsys Online Documentation version V 2003 1 2 23 2 Acquiring and Installing the Acrobat Reader Software You can acquire the Acrobat Reader software by downloading the freeware Acrobat Reader from the Web Note Windows users Beginning with version 6 0 Acrobat Reader is called Adobe Reader Downloading and Installing Acrobat Reader from the Web To download Acrobat Reader from the Acrobat Web site 1 4 Go to http www adobe com and click the Get Acrobat Reader button Follow the instructions on the Web page Uncompress the tar Z file or use the gunzip utility for the tar gz file For example gzip d sol 508 tar gz Untar the resulting file For example tar xvf sol 508 tar Enter install to start the installation script For more information consult the ReadMe html file or instguid txt file that comes packaged with Acrobat Reader Installing Synopsys Online Documentation version V 2003 12 23 3 Verifying Your Adobe Acrobat Software To view SOLD you must have Acrobat Reader version 4 x or later To search SOLD you must have the Search plug in For information about searching SOLD on
117. nloading and Installing the Software 2 10 You must install this package for each product if you are installing it to the usr synopsys syn_V 2003 12 directory for the first time Install Platform Independent Package for syn y n yl y Install Platform Independent Package for sf3 y n yl y sparcos5 Verify cksum for syn taz Pass Verify cksum for sparcos5 syn taz Pass Verify cksum for sf3 taz Pass Verify cksum for sparcos5 sf3 taz Pass Platform s selected sparcos5 Here is your final selection for installing Synopsys Tools VERSION V 2003 12 PRODUCTS syn sf3 PLATFORMS sparcos5 Synopsys Media Directory from cdrom Synopsys Install Directory to usr synopsys syn_V 2003 12 Platform Independent Package s for syn sf3 Disk space required 1034 MB Disk space available 14649 MB If all the information is correct continue with the installation Install y n yl y Starting Installation Please do not interrupt INSTALLING syn product platform_independent package V 2003 12 version uncompress lt syn taz cd usr synopsys syn_V 2003 12 tar xvfp sparcos5 INSTALLING syn product sparcos5 package V 2003 12 version uncompress lt sparcos5 syn taz cd usr synopsys syn_V 2003 12 tar xvfp INSTALLING sf3 product platform_independent package V 2003 12 version uncompress lt sf3 taz cd usr s
118. not use your Synopsys tools until you have installed configured and started SCL Obtaining Your License Keys To obtain your license key file from SmartKeys 1 Go to the SmartKeys Web page at http www synopsys com smartkeys On the SmartKeys Web page click Key Retrieval In the Key Retrieval box enter the following information Your site ID This is the numeric site ID that identifies your customer site If you have synthesis test or VHDL simulation tools installed you can obtain the site ID by viewing your site_info file sSYNOPSYS admin license site_info Your host ID optional To obtain a license key file for a single host enter its host ID To obtain license keys for all hosts at the specified site leave this field blank Your e mail address The default is your Synopsys e mail address This is the address that your key file will be sent to Click Continue to submit your request Preparing for Installation 1 16 Installing Synopsys Common Licensing Software You need to install configure and start a single copy of SCL software for all Synopsys tools If you don t have the SCL software you can download it by EST or FTP See the http www synopsys com keys download_SCL Web page Alternatively you can order the SCL software CD from the Synopsys MediaDocs Shop at http mediadocs synopsys com If you already have SCL running you do not need to reinstall it However if you are updating your lice
119. nse key file you need to notify the SCL daemons that the license file has changed See the SCL documentation for instructions on this process Note Do not install SCL into an existing directory You must install SCL into a stand alone directory For more information about licensing see the following documents e Synopsys Common Licensing Quick Start e Synopsys Common Licensing Installation and Administration Guide Soft copies of the Synopsys Common Licensing Quick Start document and the Synopsys Common Licensing Installation and Administration Guide are available in Portable Document Format PDF from http www synopsys com keys Info_SCL Preparing for Installation 1 17 Finding Your Site Identification Number Before you install any Synopsys product CD locate and make a note of your Synopsys site identification number Enter your site ID when prompted during the installation process Your site ID was shipped in the package with your Synopsys tools or if you download the software it is in your Synopsys Order Notification e mail If you have trouble locating it contact your Synopsys sales representative Creating the Synopsys Root Directory To create a new directory tree for this Synopsys release enter mkdir p usr synopsys product_version To set the permissions on the new directory tree enter chmod 755 usr synopsys product_version Important Install each version of the software in a new directory Do no
120. nts anaana ee eRe eee ee ee Red Hat Linux 7 2 Shared Object File Problem 64 Bit Platform Support 22 020005 Multiple Platform Installation 0000 ce eee Products and Platforms sceen vd aa d i eRe Ae eee Disk Space Requirements 0000e ee eee eeee Memory Requirements 0000 e eee eens Physical Memory Requirements for Synthesis PrimeTime and Design Budgeting Swap Space Requirements for Synthesis Tools Accessing Memory Beyond 2 GB With 32 Bit Synopsys Tools 6253 4 4 05 neue wooenete erat Acgduiring a Lices Oto 2 oe Rn eas ih ele Lt od ai Obtaining Your License Keys 200000005 Installing Synopsys Common Licensing Software Finding Your Site Identification Number Creating the Synopsys Root Directory 00055 Defining the SYNOPSYS Environment Variable Downloading and Installing the Software Downloading and Installing the Software by EST Using the Product Files swe ene A eee PERSE es Downloading the Files by FIP 5 Downloading the Files From the Web Performing EST Installation 0 0 0 0 cece ees Installing Product Files FroomaCD 00 00 eeeeee Mounting INCHGD 2 0d cord ero e nes Ghd mab eee paved Installing the Software From the CD Unmountin
121. nux Formality fm sparcOS5 sparc64 hp32 hp64 rs6000 linux linuxipf FPGA Compiler II fc2 sparcOS5 hp32 Windows NanoSim including ADFMI ns sparcOS5 sparc64 hp32 NanoSim Integration with hp64 rs6000 linux linuxipf VCS CosmosScope turboWave Verilog A and VTRAN Preparing for Installation 1 6 Table 1 2 Products and Supported Platforms Continued Product Product ID Platform keyword PathMill pm sparcOS5 sparc64 hp32 hp64 linux linuxipf rs6000 PowerMill including ADFMI pw sparcOS5 sparc64 hp32 VTRAN and turboWave hp64 rs6000 PrimePower pps sparcOS5 sparc64 hp32 hp64 linux PrimeTime pts sparcOS5 sparc64 hp32 hp64 linux linuxipf rs6000 RailMill rm sparcOS5 sparc64 hp32 hp64 rs6000 Synthesis syn sparcOS5 sparc64 hp32 hp64 rs6000 linux linuxipf SYSTEMSIM SYSTEMEX systemsim sparcOS5 linux systemex System Studio css sparcOS5 hp32 linux gccsparcOS5 TetraMAX tx txs sparcOS5 sparc64 hp32 hp64 linux linuxipf TimeMill including ADFMI tm sparcOS5 sparc64 hp32 VTRAN and turboWave hp64 rs6000 VCS VCS VCSi sparcOS5 sparc64 hp11 0 PA2 0_32 64 linux AIX 32 dec_alpha_osfl_4 0_64 Vera vera sparcOS5 sparc64 hp32 linux rs6000 VHDL Simulation Scirocco scirocco sparcOS5 hpux10 linux rs6000 Preparing for Installation 1 7 Note Products that support the AIX 4 3 3 rs6000 and Linux Intel Itanium platforms will be available by EST a
122. o the license file Installing VirSim version 4 3 A 4 Verifying the VirSim Installation To verify the VirSim installation 1 Change directories to an examples directory cd SVIRSIMHOME examples verilog risc 2 To invoke VirSim enter 6 virsim vpdfiletrisc vpd cfgfiletrisc cfg f run f 3 Exit the GUI by choosing File gt Exit in any GUI window Customer Support The support page on the Synopsys Web site is regularly updated with the latest information Check this page for application notes online help updates and other valuable information http www synopsys com products simulation simulation html You can also send an e mail message to VirSim Support at virsimsupport synopsys com Installing VirSim version 4 3 A 5 Installing VirSim version 4 3 A 6 Index A Acrobat Reader acquiring 23 3 downloading from Web 23 3 verifying Search plug in 23 5 verifying version of 23 4 Adobe Web site 23 3 AMPS installing 4 2 platform keyword 1 6 product ID 1 6 setting up for new user 4 2 verifying installation 4 3 app defaults file 3 7 Arcadia installing 5 2 platform keyword 1 6 product ID 1 6 setting up for new user 5 2 verifying installation 5 3 Astro environment variables 25 4 installing 25 3 setting up for new user 25 4 verifying installation 25 5 Astro Rail environment variables 26 4 installing 26 2 setting up for new user 26 4 supported platforms 26 2 verifying installation 26 5 C Cadabr
123. ome page at http www adobe com For more information see Downloading and Installing Acrobat Reader from the Web on page 23 3 Installing FPGA Compiler Il version T 2003 09 FC3 8 on UNIX Platforms 9 4 10 Installing FPGA Compiler II version T 2003 09 FC3 8 on Windows Platforms You can install the FPGA Compiler II software to run PC running Windows The procedure is explained in the following sections Product Support System Requirements for Windows Installing FPGA Compiler II Enabling Online Document Readers 10 1 Product Support The FPGA Solutions page on the Synopsys World Wide Web site is regularly updated with the latest information Check this page to find application notes online help updates and other valuable information http www synopsys com products fpga For additional installation instructions go to http www synopsys com products fpga install_ fc2 htm System Requirements for Windows Table 10 1 shows the minimum system requirements for installing FPGA Compiler Il on Windows Table 10 1 Windows System Requirements Operating system Memory Disk space for installation Windows NT 4 0 Service Pack 32 MB of RAM 50 270 MB depending on file 4 or later Windows 98 70 MB of swap space system and partition size 50 Windows ME or Windows 2000 MB for NTFS or small FAT partition and 270 MB for large FAT partition 1 100 MB of virtual memory RAM swap space is recommende
124. on 1 Make sure you are in a directory where you have read write privileges ed HOME Invoke the tool by entering the following command powrmill If you see information about the product version production date and copyright the installation was successful Installing PowerMill version U 2003 03 13 4 14 Installing PrimePower version V 2003 12 This chapter contains the following sections e Installing the Software Setting Up PrimePower for Each User e Verifying the PrimePower Installation To ensure a successful installation have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 14 1 Installing the Software Beginning with version version V 2003 12 PrimePower can be installed as a stand alone tool only It no longer overlays the synthesis tools You must install PrimePower in its own directory To install the software 1 Download and install PrimePower from the Web or by FTP following the instructions described in Downloading and Installing the Software by EST on page 2 2 Or Install the files from the PrimePower CD to your system as explained in Installing Product Files From a CD on page 2 7 Example 2 1 on page 2 10 shows a Synopsys media installation script for the synthesis tools PrimePower is installed in a similar manner Note When you are prompted to select the product you want to instal
125. on use the eject command to unmount the CD Installing Cadabra version 7 0 6 3 Setting the Environment Variables This section discusses the following environment variables e CADABRAHOME e ILM LICENSE_FIDE It is recommended that you place these variables in your HOME cshre or HOME profile file as your default settings Setting the CADABRAHOME Environment Variable Follow these steps 1 Set the SCADABRAHOME environment variable to point to your Cadabra installation subdirectory lf you are using the C shell add the following line setenv CADABRAHOME u edatools cadabra version lf you are using the Bourne shell add these lines CADABRAHOME u edatools cadabra version export CADABRAHOME 2 Add CADABRAHOME bin to your search path If you are using the C shell enter set path CADABRAHOME bin path lf you are using the Bourne shell enter PATH SCADABRAHOME bin PATH export PATH Installing Cadabra version 7 0 6 4 Setting the LM_LICENSE_ FILE Environment Variable To enable Cadabra to check out a license you must set the LM _LICENSE_FILE environment variable e If you are using the C shell enter setenv LM_LICENSE_ FILE 27000 my_server e Ifyou are using the Bourne shell enter LM_LICENSE_FILE 27000 my_server export SNPSLMD_ LICENSE FILE The port and host name variables correspond to the TCP port and license server host name specified in the SERVER line of the Synopsys l
126. on location install the Design_analyzer file by entering a command similar to the one in the following example Installing the Synopsys Synthesis Tools version V 2003 12 3 7 cp SSYNOPSYS admin setup Design_analyzer usr openwin 1lib X11 app defaults cp SSYNOPSYS admin setup Design_analyzer usr 1ib X11 app defaults You can customize the GUI display for an individual Design Analyzer user by adding color and font definitions to the Xdefaults file in each user s login directory Values defined in the Xdefaults file override the values in the systemwide app defaults file If you are using the Design Vision or Physical Compiler GUI tools see the appropriate online Help system for information about customizing the tool environment Setting up SystemC Compiler for Each User To set up a SystemC Compiler user in addition to the other synthesis settings you must define the absolute path to a C compiler and the compiler options If you are using the C shell add the following lines to the cshrc file setenv SYSTEMC_CPP compiler _home options If you are using the Bourne Korn or Bash shell add the following lines to the profile kshrc or bashrc file SYSTEMC_CPP compiler_home options export SYSTEMC_CPP For the GNU C Compiler version 2 95 2 or later or version 3 2 for Linux replace compiler_home with the absolute path to the GNU C Compiler and replace options with the typical compiler options you use Fo
127. opsys software tools Related Publications For additional information about Synopsys tools see e Synopsys Online Documentation SOLD which is included with the software for CD users or is available to download through the Synopsys Electronic Software Transfer EST system e Documentation on the Web which is available through SolvNet at http solvnet synopsys com e The Synopsys MediaDocs Shop from which you can order printed copies of Synopsys documents at http mediadocs synopsys com xix XX Conventions The following conventions are used in Synopsys documentation Convention Description Courier Courier italic Courier bold Control c Edit gt Copy Indicates command syntax Indicates a user defined value in Synopsys syntax such as ob ject_name A user defined value that is not Synopsys syntax such as a user defined value in a Verilog or VHDL statement is indicated by regular text font italic Indicates user input text you type verbatin in Synopsys syntax and examples User input that is not Synopsys syntax such as a user name or password you enter in a GUI is indicated by regular text font bold Denotes optional parameters such as pinli pin2 pinN Indicates a choice among alternatives such as low medium high This example indicates that you can enter one of three possible values for an option low medium or high Connects terms that are read as
128. ord 1 7 product ID 1 7 support license 21 5 technical 21 4 verifying installation AMPS 4 3 Arcadia 5 3 Cadabra 6 6 Floorplan Compiler 7 4 Formality 8 3 NanoSim 11 4 PathMill 12 3 PowerMill 13 4 PrimePower 14 3 RailMill 16 3 stamp_compiler 15 4 IN 6 synthesis tools 3 20 System Studio 17 6 TetraMAX 18 7 TimeMill 19 4 VCS 20 6 VirSim A 5 Verilog XL simulator 3 11 veriuser c file modifying 3 12 VHDL simulation 17 6 VHDL Simulation Scirocco installing 22 2 platform keyword 1 7 product ID 1 7 setting up for each user 22 6 verifying installation 22 6 VirSim environment variables setting license A 4 setting up for new user A 3 verifying installation A 5 VirSimr support A 5 VPOWER linking to Verilog XL simulator 3 11 makefile 3 15 vconfig 3 14 VPOWER Power Compiler installing 3 11 X X Window System available colors 3 7 troubleshooting 24 5 xinitre 24 6 xterm 24 5
129. ormation about contacting Customer Support see Customer Support on page xxi Installing Star RCXT version V 2003 12 29 5 Installing Star RCXT version V 2003 12 29 6 30 Installing StarSim XT version V 2003 12 This chapter contains the following sections Media Availability and Supported Platforms Downloading and Installing the Software Setting the Environment Variables Verifying the StarSim XT Installation Customer Support Installing StarSim XT version V 2003 12 30 1 Media Availability and Supported Platforms StarSim XT is available on CD or by EST download Obtain the appropriate binary executable files based on the operating system you need Table 30 1 shows the supported platforms for the V 2003 12 release Table 30 1 Supported Operating Systems and Platform Keywords Operating system Platform keyword Solaris 7 8 sparcOS5 Solaris 5 5 5 6 are also supported sparc64 HP UX 11 0 11i hp32 HP UX 10 2 is also supported hp64 Red Hat linux 7 2 linux Red Hat linux 7 1 is also supported Downloading and Installing the Software To download and install StarSim XT 1 Create a StarSim XT installation directory if one does not already exist For example mkdir p usr synopsys starsimxt 2 Download the StarSim XT release to the installation directory You can get the latest StarSim XT download instructions from the SolvNet Release Library 3 Uncompress and untar the files gzi
130. ormation on SCL software see Acquiring a License on page 1 15 Overlay Installation Install TetraMAX version V 2003 12 over version V 2003 12 of the synthesis tools only Do not install it over any other versions of the synthesis tools You perform overlay installation in the directory in which you installed the Synopsys synthesis tools 6SYNOPSYS You must log on as the same user who installed the Synopsys synthesis tools so that you have write permission in the SYNOPSYS directory Note If you have not installed the Synopsys synthesis tools install them before proceeding with overlay installation see Chapter 3 If you do not have the synthesis tools installed the installation of TetraMAX overlay will not be allowed To perform overlay installation 1 To download and install TetraMAX from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 Or Installing TetraMAX version V 2003 12 18 4 Install the files from the TetraMAX CD to your system as explained in Installing Product Files From a CD on page 2 7 Example 2 1 on page 2 10 shows a Synopsys media installation script for the synthesis tools TetraMAX is installed in a similar manner Note When you are prompted to select the product you want to install enter tx to perform an overlay installation 2 Make sure your Synopsys license server and license key file are set up
131. ort Center To access the online EST Troubleshooting Guide go to http www synopsys com cgi bin est cgi Caution Install each version of the software in a new directory Do not install different versions of Synopsys software in the same directory Using the Product Files Depending on file size product files are packaged by one of three processes tar tar Z or tar gz These instructions cover each process The product files use the following naming convention Downloading and Installing the Software 2 2 For tar files productname_productversion_common tar productname_productversion_platform tar For tar Z files productname_productversion_common tar Z productname_productversion_platform tar Z For tar gz files productname_productversion_common tar gz productname_productversion_platform tar gz For each tool you want to install substitute the appropriate product ID and version for productname_productversion and platform keyword for platform See Products and Platforms on page 1 6 Important For each product except SOLD you must install one common file platform independent package and one or more platform specific files See Figure 1 1 on page 1 5 For SOLD install only the tar files SOLD version U 2003 09 does not have a common file and is platform independent Downloading and Installing the Software 2 3 Downloading the Files by FTP To download the files by FTP 1 For each tool you m
132. ow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 2 on page 2 13 shows a Synopsys media installation script for PrimeTime NanoSim is installed in a similar manner The NanoSim subtools ADFMI NanoSim Integration with VCS TurboWave Verilog A VTRAN and CosmosScope are automatically installed with the NanoSim installation NanoSim can be installed as a stand alone installation or with any of the tools PowerMill and TimeMill it comes packaged with Setting Up NanoSim for Each User To set up a new NanoSim tool user e If you are using the C shell source the CSHRC_ platform file located in the install directory ole cd install_dir source CSHRC_platform The install script for NanoSim creates a CSHRC_platform file for each platform installed The term platform is replaced with the platform you installed Installing NanoSim version V 2003 12 11 2 The CSHRC_ platform file sets the path for NanoSim CosmosScope and the NanoSim man pages set path install_directory platform ns utilities cosmos ai_bin Spath setenv MANPATH install_directory doc ns man SMANPATH where install_directory is the directory where the tool has been installed If you don t source the CSHRC_ platform file copy the above line and set the path from that file If you are using the Bourne Korn or Bash shell add the following line to the profile kshrc or bashrc file
133. p dc starsimxt_version_platform tar gz tar xvf Installing StarSim XT version V 2003 12 30 2 This command creates a subdirectory in the StarSim XT installation directory For example usr synopsys starsimxt starsimxt_version_platform In the remainder of this chapter this subdirectory is referred to as the StarSim XT installation directory 4 To set the file permissions on the new directory tree and its contents enter chmod R 755 usr synopsys starsimxt 5 Remove the starsimxt_version_platform tar gz file rm starsimxt_version_platform tar gz 6 For each user set the required environment variables as described in the next section Setting the Environment Variables This section discusses the following environment variables e starsimxt_HOME LM LICENSE_FILDE It is recommended that you place these variables in your HOME cshrc or HOME profile file as your default settings Installing StarSim XT version V 2003 12 30 3 Setting the starsimxt_HOME Environment Variable Follow these steps 1 Setthe starsimxt_HOME environment variable to point to your StarSim XT installation directory lf you are using the C shell enter setenv starsimxt_HOME starsimxt_installation_directory path If you are using the Bourne shell enter setenv starsimxt_HOME starsimxt_installation_directory path EXPORT starsimxt_HOME 2 Add starsimxt_HOME bin to your search path If you are using the C shell
134. privgrp man page for details Red Hat Linux 7 2 Shared Object File Problem If you receive an error about libncurses so 4 cannot open shared object file no such file or directory when you run a Synopsys tool on a Red Hat 7 2 platform install the ncurses4 package This package is available on the Red Hat CD or you can download it from the Red Hat FTP server at ftp ftp redhat com pub redhat linux 7 2 en os i386 RedHat RPMS ncurses4 5 0 4 i386 rom 64 Bit Platform Support The Synopsys tools support 64 bit operation on HP UX Solaris Linux and AIX platforms When you run the tools in 64 bit mode the upper limit for virtual address space is extended beyond the 4 gigabyte limit imposed by the 32 bit mode allowing you to process larger designs With both the 32 bit and 64 bit platforms installed you have the flexibility to run either 32 bit or 64 bit applications without running out of memory Preparing for Installation 1 4 You can install the 64 bit version of the Synopsys tools in the same root directory as the 32 bit version or in a separate directory When both 32 bit and 64 bit dc_shell executable files are installed and you specify dc_shell the first executable file in the PATH environment is invoked Note If you attempt to use the 64 bit mode executable file on a 32 bit platform you will see an error message Multiple Platform Installation When you install tools on a network that connects different platforms
135. put_filename Runs Davinci 30 000 nodes with an input file Davinci dv30k input_filename Runs Davinci 30 000 nodes with an input file Davinci dv60k input_filename Runs Davinci 60 000 nodes with an input file Davinci dv100k input_filename Runs Davinci 100 000 nodes with an input file Medici medici input_filename Runs Medici 10 000 nodes with an input file Medici md3200 input_filename Runs Medici 3 200 nodes with an input file Medici md10000 input_filename Runs Medici 10 000 nodes with an input file Medici md20000 input_filename Runs Medici 20 000 nodes with an Installing TCAD Products and Utilities 31 12 input file Table 31 5 Products and Keywords Continued Product Format Description Medici md60000 input_filename Runs Medici 60 000 nodes with an input file Raphael raphael_program input_filename Runs Raphael with an input file Raphael dplot input_filename Runs Dplot with an input file Taurus Device tdevice input_filename Runs Taurus Device with an input file Taurus Layout tlayout input_filename Runs Taurus Layout with an input file Taurus Process tprocess input_filename Runs Taurus Process with an input file Taurus Visual tv Runs Taurus Visual Taurus twb Runs Taurus WorkBench WorkBench TSUPREM 4 tsuprem4 input_filename Runs TSUPREM 4 with an input file Installing TCAD Products and Utilities 31 13 Using Graphics Devices This section discusses how graphics devices are describe
136. r example setenv SYSTEMC_CPP usr local bin gcc E C Installing the Synopsys Synthesis Tools version V 2003 12 3 8 For the Sun SparcWorks C Compiler version 5 0 or later replace compiler_home with the absolute path to Sun SparcWorks C Compiler and replace options with the typical compiler options you use For example setenv SYSTEMC CPP usr local bin ce E xCC Xc The SystemC Compiler default path to the SystemC library include files is SYNOPSYS auxx systemc include To define a different path to the SystemC library include files specify the 1 option for SYSTEMC_CPP For example setenv SYSTEMC_CPP usr local bin gcc E C I my_systemc include Configuring the Browser for Physical Compiler and Design Vision Online Help The Physical Compiler and Design Vision online Help systems are browser based HTML Help systems For optimal viewing use Netscape Navigator version 4 78 for UNIX These Help systems are not supported in Netscape Navigator version 6 or later Important When you use online Help from within the GUI the Netscape executable file must be on the UNIX path Both Help systems make extensive use of Java applets JavaScript and style sheets In your browser preferences select the Advanced category and make sure that e The Enable Java Enable JavaScript and Enable Style Sheets options are all selected e The Enable Java Plugin option is deselected Installing the Synopsys Synthesis Tools
137. re see the Licensing Quick Start document and the Licensing Installation and Administration Guide which are available online at www synopsys com keys Downloading and Installing the Software 2 16 Installing the Synopsys Synthesis Tools version V 2003 12 This chapter contains the following sections Synthesis Tools Installing the Software Configuring the Synthesis Tools Installing Optional Tools Verifying the Synthesis Tools Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 3 1 e Define the SYNOPSYS environment variable see Defining the SYNOPSYS Environment Variable on page 1 19 e Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 Synthesis Tools The Synopsys synthesis tools include the following e Core synthesis tools Automated Chip Synthesis BSD Compiler Behavioral Compiler Design Analyzer Design Compiler Design Vision DesignWare DFT Compiler EDIF 2 0 0 Interface Floorplan Manager HDL Compiler Presto Verilog Library Compiler Module Compiler Installing the Synopsys Synthesis Tools version V 2003 12 3 2 Physical Compiler Power Compiler SystemC Compiler VHDL Compiler e Synopsys Integrator for Falcon Framework Mentor
138. ries to make a simulation executable file To add PLI functionality to the simulation executable file you need to link an extra PLI library when you compile your designs For Solaris the appropriate PLI library is lib sparcOS5 libvpower a You normally get a VCS simulation executable file by entering the following command at the UNIX prompt wes Mupdate your_verilog_design_files compiler_options Installing the Synopsys Synthesis Tools version V 2003 12 3 18 To link with the PLI library enter vcs Mupdate P SSYNOPSYS auxx syn power vpower vcs vcs sample vpower tab your_verilog_design_files compiler_options SSYNOPSYS auxx syn power vpower lib sparcOS5 libvpower a This generates an executable file called simv that includes PLI functionality Note You can copy vpower tab and libvpower a into any file locations that are convenient for you Using SoCBIST To insert SoCBIST into your design you need DFT Compiler which installs with the synthesis tools You also need TetraMAX if you want to use the SoCBIST pattern generation functionality You can install TetraMAX as an overlay on the synthesis tools or as a stand alone installation For required SoCBIST environment variables see Setting Up the User Environment on page 18 6 Installing the Synopsys Synthesis Tools version V 2003 12 3 19 Verifying the Synthesis Tools Installation Note The Synopsys Common Licensing SCL software must be ins
139. rify the VCS and VCSi installation 1 Make sure you are in a directory where you have read write privileges ed HOME Invoke the tool by entering ves ID If you see information about the product version production date and copyright the installation was successful Run the VirSim GUI on each installed platform by entering ves RPP Exit the GUI by choosing File gt Exit in any GUI window Installing VCS version 7 0 2 20 6 Customer Support The VCS support page on the Synopsys Web site is regularly updated with the latest information Check this page for application notes online help updates and other valuable information http www synopsys com products simulation simulation html You can also send an e mail message to VCS Support at vcs_support synopsys com Installing VCS version 7 0 2 20 7 Installing VCS version 7 0 2 20 8 OT Installing Vera version 6 2 0 This chapter contains the following sections e Downloading and Installing the Software e Setting the Environment Variables e Customer Support Installing Vera version 6 2 0 21 1 Downloading and Installing the Software 1 Create a Vera installation directory For example mkdir p usr synopsys vera Download the Vera release to the installation directory The latest Vera download instructions can be obtained from the SolvNet Release Library or from vera support synopsys com If a Vera directory does not already
140. rocco installation directory and change to that directory For example enter mkdir u edatools ed u edatools 2 Download the software to the installation directory 3 Uncompress and untar the files gzip dc u edatools vcs_mx ves_mx platform_version tar gz tar xvf This command creates a VHDL Simulation Scirocco subdirectory named after the release of VHDL Simulation Scirocco that you are installing Installing VHDL Simulation Scirocco version 2002 12 2 22 2 To install VHDL Simulation Scirocco from a CD 1 Create a VHDL Simulation Scirocco installation directory and change to that directory For example mkdir u edatools vcs_mx ed u edatools vcs_mx Mount the CD by using the appropriate command for your operating system For example enter mount o ro dev dsk c2t1id4s0 cdrom Note Mounting instructions are different for each platform See your system documentation for the correct CD mounting commands Also for sparcOS5 with vold the volume management daemon for managing CD and floppy devices the cdrom directory already exists and the CD is automatically mounted Therefore use cd cdrom cdrom0 instead of cd cdrom Uncompress and untar the files gzip dc u edatools vcs_mx ves_mx_platform_version tar gz tar xvf This command creates a Scirocco subdirectory named after the release of VHDL Simulation Scirocco that you are installing Unmount the CD by using th
141. rompts Installing With Windows DOS Shell To install HSPICE by using the Windows DOS shell 1 Insert the HSPICE CD into the CD drive 2 Atthe DOS shell command prompt enter c gt CD ROM drive letter pchspice setup exe 3 To install the software follow the screen prompts Installing the Sentinel System Drivers Installation of Sentinel drivers is required only when you use dongle based licenses For information about the Win32 sentinel_key driver dongle key see the README txt file located in the installdir installation directory In Windows Explorer Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 10 1 Double click the installdir DRIVERS flexid exe file to install the driver Set the LM_LICENSE_FILE environment variable This variable is normally set in the Control Panel For Windows NT choose Control Panel gt System gt environment For Windows 2000 or WindowsXP choose Control Panel gt System gt Environment Variables LM LICENSE FILE path_to_license_ file For detailed information about the FLEXIm licensing see the FLEXIm End User Manual Note If you have multiple dongles connected to each other the Synopsys dongle must be connected directly to the PC Running HSPICE on Windows You can run HSPICE in any of the following ways Double click the HSPUI icon and then click the Simulate button Double click the HSPICE icon You are prompted to enter names for
142. rovides information about supported hardware operating systems and required OS patches If the required patch described on this page is not available from the platform vendor install the most recent patch instead Table 1 1 Supported Platforms Operating Systems and Keywords Platform Operating system Synopsys platform keywords Window environment HP PA RISC 2 0 HP UX 11 0 11i hp32 32 bit mode CDE hp64 64 bit mode Sun Sparc Solaris 8 9 sparcOS5 32 bit mode CDE sparc64 64 bit mode Intel IA 32 or X86 32 Red Hat Linux 7 2 linux 32 bit mode GNOME Intel IA 32 or X86 32 RHEL v3 3 linux 32 bit mode GNOME IPF2 2 RHEL v2 11 3 linuxipf 64 bit mode GNOME AMD Opteron RHEL v3 3 amd64 64 bit mode GNOME IBM RS6000 AIX 5 13 rs6000 32 bit mode CDE aix64 64 bit mode 1 Red Hat Enterprise Linux RHEL 2 Itanium Processor Family Intel Itanium 2 processor 3 The AIX 5 1 and Linux RHEL platforms are not available on CD They will be available for download by electronic software transfer EST at a later date For availability check with your Synopsys sales representative Preparing for Installation 1 3 HP UX Requirements The HP UX operating system has the following requirements e Local non NFS file systems must be configured for long file names See the etc convertfs man page for details e The chown privilege must be switched off To switch off chown enter setprivgrp n chown See the set
143. rsion V 2003 12 15 3 cp SSYNOPSYS admin setup synopsys_pt setup synopsys_pt setup If you are using the Bourne Korn or Bash shell enter cp SSYNOPSYS admin setup synopsys_pt setup SHOME synopsys_pt setup You can modify this file to customize the settings for each user Verifying the PrimeTime Installation Note The Synopsys Common Licensing SCL software must be installed and SNPSLMD_LICENSE_FILE or LM_LICENSE_FILE must be defined before you can verify the PrimeTime tools installation For information on installing SCL see Acquiring a License on page 1 15 To verify installation of PrimeTime 1 Make sure you are in a directory where you have read write privileges ed SHOME 2 Invoke the tool by entering one of the following commands on a licensed machine SYNOPSYS platform syn bin pt_shell SYNOPSYS platform syn bin primetime Replace platform with the appropriate platform see Products and Supported Platforms on page 1 6 If you get the correct prompt or if a GUI appears the installation was successful Installing PrimeTime version V 2003 12 15 4 16 Installing RailMill version U 2003 03 This chapter contains the following sections Installing the Software Setting Up RailMill for Each User Verifying the RailMill Installation To ensure a successful installation complete the following procedures before beginning the installation process Create the Synopsys root
144. s aborted Explanation You are attempting to run a SunView application when you are not running in the SunView window environment This error can occur during STUDIO if your path is not set correctly e Ifyou are running OpenWindows be sure the OpenWindows bin directory precedes the bin and usr bin directories Installing TCAD Products and Utilities 31 20 TCAD Utilities The TCAD utilities are a set of programs designed to help you use TCAD products more effectively TCAD utilities are installed automatically as part of a TCAD product installation TCAD utility Directory The utility directory for all new releases of TCAD products after June 1991 is product independent The utility directory contains a file named V where is a number V is the version number of the utility in that directory Table 31 6 lists the utilities that TCAD provides Table 31 6 TCAD Utilities Utility Description tmaplot Generates Sun SunView and X graphics For products released after June 1991 you must use tmaplot if you use Sun or X graphics tmafork Allows systems that do not have a vfork system call to run a TCAD product without temporarily doubling the virtual memory required replot Allows you to re create TCAD graphical output without rerunning a simulation rfbtoa Takes a TCAD binary output file such as a structure file and converts it to ASCII format tfatob Takes a TCAD formatted ASCII file and con
145. s document in the directory where you installed the software To read the Synopsys FPGA online document you must have Adobe Acrobat Reader version 4 0 or later installed on your system Install Acrobat Reader version 4 0 by one of the following methods e To install Acrobat Reader on a Windows system from within FPGA Compiler Il enter the following command CD_ROM_drive acrosrch 32bit setup e Download the latest Acrobat Reader from the Adobe home page at http www adobe com For more information see Downloading and Installing Acrobat Reader from the Web on page 23 3 Installing FPGA Compiler Il version T 2003 09 FC3 8 on Windows Platforms 10 4 11 Installing NanoSim version V 2003 12 This chapter contains the following sections e Installing the Software e Setting Up NanoSim for Each User e Verifying the NanoSim Installation To ensure a successful installation complete the following procedures before beginning the installation process e Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 e Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 11 1 Installing the Software To download and install NanoSim from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the NanoSim software from the CD foll
146. sclosure to nationals of other countries contrary to United States law is prohibited It is the reader s responsibility to determine the applicable regulations and to comply with them Disclaimer SYNOPSYS INC AND ITS LICENSORS MAKE NO WARRANTY OF ANY KIND EXPRESS OR IMPLIED WITH REGARD TO THIS MATERIAL INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE Registered Trademarks Synopsys AMPS Arcadia C Level Design C2HDL C2V C2VHDL Cadabra Calaveras Algorithm CATS COSSAP CSim DelayMill Design Compiler DesignPower DesignWare Device Model Builder EPIC Formality HSPICE Hypermodel iN Phase in Sync InSpecs LEDA MAST Meta Meta Software ModelAccess ModelTools PathMill Photolynx Physical Compiler PowerArc PowerMill PrimeTime RailMill Raphael RapidScript Saber SiVL SmartLogic SNUG SolvNet Stream Driven Simulator Superlog System Compiler Testify TetraMAX TimeMill TMA Vera and Virtual Stepper are registered trademarks of Synopsys Inc Trademarks abraCAD abraMAP Active Parasitics AFGen Apollo Apollo II Apollo DPII Apollo GA ApolloGAIl Astro Astro Rail Astro Xtalk Aurora AvanTestchip AvanWaves BCView Behavioral Compiler BOA BRT Cedar ChipPlanner Circuit Analysis Columbia Columbia CE Comet 3D Cosmos CosmosEnterprise CosmosLE CosmosScope CosmosSE Cyclelink Davinci DC Expert DC Expert Plus DC Professional
147. search path has been modified to include tcad bin it is already set up for updates Installing TCAD Products and Utilities 31 23 Installing TCAD Products and Utilities 31 24 Installing VirSim version 4 3 This appendix contains the following sections that give instructions for installing the stand alone VirSim GUI Installing the Software Setting Up VirSim for Each User Setting the SNPSLMD_LICENSE_FILE or LM_LICENSE_FILE Environment Variable Verifying the VirSim Installation Customer Support Important The stand alone installation instructions in this chapter apply only to customers who do not have the VCS or VHDL Simulation Scirocco tools VirSim installs automatically with those tools A 1 Installing the Software To download and install VirSim from the Web or by FTP e mail virsimsupport synopsys com Table A 1 shows the supported platforms for the 7 1 release Table A 1 Supported Platforms and Keywords Operating system Platform keyword Solaris 7 8 sparcOS5 32 bit platform sparc64 64 bit platform HP UX 11 0 11i hp32 hp64 Red Hat Linux 7 2 linux for Intel 2 4 kernel To download and install VirSim 1 Create a VirSim installation directory and change to that directory For example mkdir virsim_install_ dir cd virsim_install_dir 2 Download the software to the installation directory 3 Uncompress and untar the files 2 gzip dc virsim_platform_version tar gz tar xv
148. sion 2002 12 2 22 6 23 Installing Synopsys Online Documentation version V 2003 12 This chapter contains the following sections About SOLD Acquiring and Installing the Acrobat Reader Software Verifying Your Adobe Acrobat Software Installing SOLD Verifying the SOLD Installation Configuring SOLD for Each User Searching SOLD on Linux To ensure a successful installation complete the following procedures before beginning the installation process 23 1 e Create the Synopsys root directory see Creating the Synopsys Root Directory on page 1 18 e Define the SYNOPSYS environment variable see Defining the SYNOPSYS Environment Variable on page 1 19 The V 2003 12 version of SOLD contains documentation for the V 2003 12 U 2003 09 U 2003 06 and U 2003 03 releases of Synopsys tools You can access the documentation by clicking the product name on the SOLD front panel About SOLD This chapter describes how to install and verify Synopsys Online Documentation SOLD The SOLD CD and the SOLD directory contain document files in the cross platform Adobe Portable Document Format PDF as well as Portable Document Index files PDX that enable full text searching across all SOLD documents To read and search these files you need version 4 0 or later of Adobe Acrobat Reader with Search plug in or Adobe Acrobat You can download Acrobat Reader with Search plug in free of charge from the Adobe Web site For more i
149. sion V 2003 12 23 7 Example 2 1 on page 2 10 shows a Synopsys media installation script for the synthesis tools SOLD is installed in a similar manner CD Installation The SOLD collections are packaged on four CDs Volume 1 2 and 3 are packaged together Volume 4 System Studio SOLD is packaged separately and is provided only to System Studio customers To install SOLD from the CD follow the installation procedure described in Mounting the CD on page 2 8 To access all documentation except for Japanese SOLD J SOLD on volume 3 and System Studio copy the volume 1 and volume 2 CDs to your hard disk by running the install now script To install only J SOLD install the volume 3 CD sold_V 2003 12_jsd3 To install only documentation for System Studio install the System Studio Online Documentation CD sold_V 2003 12_ssd4 Example 2 1 on page 2 10 shows a Synopsys media installation script for the synthesis tools SOLD is installed in a similar manner Partial Installation Because each collection directory is self contained partial installations of SOLD are possible To effect a partial installation of SOLD perform a standard installation then delete from SYNOPSYS doc online those collection directories you do not need at your site Installing Synopsys Online Documentation version V 2003 1 2 23 8 Note Do not delete the top pdf file it contains the SOLD front panel which lists the products that are docu
150. stomizations are included in the VPOWER installation As shown in the sample veriuser c file make the following changes in your current site copy of veriuser c Installing the Synopsys Synthesis Tools version V 2003 12 3 13 Add the following line include tc_extern h Add the following user tasks usertask 0 0 0 tc_set tc_set_sync Stoggle_set 1 usertask 0 0 0 tc_start 0 Stoggle_start 1 usertask 0 0 0 tc_stop 0 Stoggle_stop 1 usertask 0 0 0 tc_reset 0 Stoggle_reset 1 usertask 0 0 0 tc_compatibility 0 Stoggle_count 1 usertask 0 toggle_report_check 0 toggle_report 0 S toggle_report 0 usertask 0 0 0 read_lib_saif tc_lib_sync Sread_lib_saif 1 usertask 0 0 0 read_rtl_saif tc_set_sync Sread_rtl_saif 1 Comment out the following line char veriuser_version_str 4 Save your modified veriuser c file 5 Exit your text editor and remain in the sample directory to link the executable file Linking User Tasks to the Simulation Executable File VPOWER provides two ways to link the user tasks to your simulator executable file by using the vconfig utility or by using a UNIX makefile Each method links your simulator to the VPOWER user tasks Choose the method that you find familiar or comfortable Using vconfig to Link the Executable File The vconfig utility creates a script called cr_vlog The cr_vlog script links your
151. t install different versions of Synopsys software in the same directory Preparing for Installation 1 18 Defining the SYNOPSYS Environment Variable Set the SYNOPSYS environment variable SSYNOPSYS in the shell that you are using C Bourne Korn or Bash In the following examples the root_directory argument is the name of the Synopsys root directory If you are using the C shell enter the following command to set the SYNOPSYS environment variable setenv SYNOPSYS root_directory If you are using the Bourne Korn or Bash shell enter the following command to set the SYNOPSYS environment variable SYNOPSYS root_directory export SYNOPSYS Preparing for Installation 1 19 Preparing for Installation 1 20 2 Downloading and Installing the Software This chapter provides information about downloading and installing Synopsys tools The chapter contains the following sections e Downloading and Installing the Software by EST e Performing EST Installation e Installing Product Files From a CD 2 1 Downloading and Installing the Software by EST You can download Synopsys software in two ways e By FIP e From the Web For help with download problems contact the Synopsys Electronic Software Transfer department E mail support est adm synopsys com Telephone support 650 584 1631 Note The EST department does not help with installation or licensing issues For help with such issues contact your local Supp
152. t a later date For more information contact your local applications consultant Disk Space Requirements Table 1 3 lists the amount of disk space required to install the various Synopsys tools Each CD also includes this information in the top level README product_name file Table 1 3 Disk Space Requirements Synopsys product Required size in MB approximate AMPS Platform independent 35 Per platform 110 Arcadia Platform independent 40 Per platform 450 Cadabra Platform independent 140 Per platform 75 Floorplan Compiler Platform independent 50 Per platform 400 Formality Platform independent 102 Per platform 132 FPGA Compiler II Platform independent 150 Per platform 100 Preparing for Installation 1 8 Table 1 3 Disk Space Requirements Continued Synopsys product Required size in MB approximate NanoSim Platform independent 50 Per platform 500 PathMill Platform independent 11 Per platform 172 PowerMill Platform independent 50 Per platform 300 sparcOS5 450 PrimePower Platform independent 492 Per platform 122 PrimeTime Platform independent 450 Per platform 350 RailMill Platform independent 125 Per platform 300 Synthesis tools Platform independent 400 Per platform 825 Synopsys online documentation 385 English Synopsys online documentation 350 Japanese System Studio Platform independent 700 Per platform 600 System Studio SOLD 100 Preparing for Installation 1 9
153. talled and SNPSLMD_LICENSE_FILE or LM_LICENSE_FILE must be defined before you can verify the synthesis tools installation For information on installing SCL see Acquiring a License on page 1 15 To verify installation 1 Make sure you are in a directory where you have read write privileges ed SHOME 2 Invoke one of the synthesis tools on a licensed machine For example invoke Design Compiler Library Compiler Design Analyzer or Design Vision by entering one of the following commands SYNOPSYS platform syn bin dc_shell SYNOPSYS platform syn bin 1lc_shell o S SYNOPSYS platform syn bin design_analyzer SYNOPSYS platform syn bin design_vision Replace platform with the appropriate platform For the most recent information about tool specific platform support see the documentation for your product Installing the Synopsys Synthesis Tools version V 2003 12 3 20 Note You can verify other synthesis tools by using the preceding command Simply replace the executable file name with the name of another synthesis tool If you get the correct prompt or if a GUI appears the installation was successful Installing the Synopsys Synthesis Tools version V 2003 12 3 21 Installing the Synopsys Synthesis Tools version V 2003 12 3 22 4 Installing AMPS version U 2003 03 This chapter contains the following sections Installing the Software Setting Up AMPS for Each User Verifying the AMPS
154. talling SOLD You can install SOLD by electronic software transfer EST or from the SOLD CD Contents of SOLD The SOLD documentation set contains PDF document files the index PDX files that enable full text searching and the UNIX installation scripts SOLD contains several collections of documents Each collection describes a particular subject area and resides in its own directory Each collection directory contains all the PDF files for the books in its subject area as well as the index files for searching in that collection Installing Synopsys Online Documentation version V 2003 12 23 5 The README 1ST file in the SOLD directory and on the SOLD CD lists the contents of SOLD Installation Options There are two ways to install SOLD e Asa stand alone installation e As an overlay installation installed over an existing Synopsys installation directory Note You cannot install a stand alone product over a stand alone SOLD installation To install SOLD and a stand alone product together install the product first then install SOLD as an overlay installation The SOLD installation procedure copies files from the SOLD directory for EST or SOLD CD into the appropriate places in the Synopsys root directory structure SOLD offers the following installation options e Full installation on hard drive e Partial installation on hard drive e No installation on hard drive read from CD The installation script perfor
155. ted Platforms on page 1 6 Verifying the Arcadia Installation To verify the Arcadia installation 1 Make sure you are in a directory where you have read write privileges cd HOME Invoke the tool by entering the following command DBCONVERT version If you see information about the product version production date and copyright the installation was successful Run the Arcadia GUI on each installed platform by entering the following command SYNOPSYS platform arc bin sviewer 4 Exit the GUI by choosing File gt Exit in any GUI window Installing Arcadia version U 2003 03 5 3 Installing Arcadia version U 2003 03 5 4 Installing Cadabra version 7 0 This chapter contains the following sections e Installing the Software e Setting the Environment Variables e Verifying the Cadabra Installation e Customer Support To ensure a successful installation complete the following procedure before beginning the installation process e Have your license server running and have the appropriate license keys installed see Acquiring a License on page 15 6 1 Installing the Software Cadabra is a stand alone product and cannot be installed over an existing Synopsys product including a prior version of Cadabra You must create a new directory for Cadabra To download and install Cadabra by electronic software transfer EST 1 Create a Cadabra installation directory and change to that direc
156. that it can access the Synopsys software Perform this procedure for each machine on the network To set up your machine 1 Update your environment variables by adding the following variables in your cshrc file setenv LM LICENSE FILE usr local flexlm licenses license dat SLM LICENSE FILE set path install_dir bin platform path where install_diris the directory in which the Synopsys software is installed and platform is the appropriate platform Update your path variable by entering o source cshrce Make sure the XKeysymDB file resides in or is linked from usrlib X11 Installing Astro Rail version V 2003 12 26 4 Verifying the Astro Rail Installation To verify the Astro Rail installation 1 Make sure you are in a directory where you have read write privileges ed HOME Invoke the tool by entering AstroRail If you see information about the product version production date and copyright the installation was successful Installing Astro Rail version V 2003 12 26 5 Installing Astro Rail version V 2003 12 26 6 L Installing Hercules version V 2003 12 Note The installation instructions in this chapter are the most up to date available at the time of production However changes might have occurred For the latest installation information see the product release notes or documentation This chapter contains the following sections e Media Availability and Supported
157. the result is the directory tree shown in Figure 1 1 Figure 1 1 Illustration of a Multiple Platform Installation SYNOPSYS Plat form independent admin auxx doc dw interfaces libraries packages platform1 platform2 Each Synopsys product includes a platform independent package indicated by the shaded box in Figure 1 1 containing files common to all platforms When you select multiple platforms the installation script installs one platform independent package and a platform dependent package for each selected platform If you have previously installed a product on one platform and want to install it on another platform Preparing for Installation 1 5 1 Rerun the installation script for the product 2 Inthe installation script Answer n to the query about installing the platform independent package Specify the new platform when queried about which platform to install Products and Platforms Table 1 2 lists the products and their supported platforms For the latest product specific platform information see the release notes for your tool Table 1 2 Products and Supported Platforms Product Product ID Platform keyword AMPS amps sparcOS5 hp32 linux Arcadia arc sparcOS5 sparc64 hp32 hp64 rs6000 Cadabra cadabra sparcOS5 hp32 linux Floorplan Compiler fpc sparcOS5 sparc64 li
158. ting instructions are different for each platform See your system documentation for the correct CD mounting commands Also for sparcOS5 with vold the volume management daemon for managing CD and floppy devices the cdrom directory already exists and the CD is automatically mounted Therefore use cd cdrom cdrom0 instead of cd cdrom and use eject to unmount the CD 3 Unmount the CD by using the appropriate command for your operating system For example enter umount cdrom Note If you are running the volume management daemon use the eject command to unmount the CD Installing VCS version 7 0 2 20 3 Setting the Environment Variables This section discusses the following environment variables e SVCS_HOME or SVCSI_HOME e SNPSLMD_LICENSE_ FILE e ILM LICENSE_FIDE It is recommended that you place these variables in your HOME cshre or HOME profile file as your default settings Setting the VCS_HOME Environment Variable Follow these steps 1 Set the SvCS_HOME environment variable to point to your VCS installation subdirectory If you are using the C shell add the following line setenv VCS_HOME u edatools vcs7 0 2 lf you are using the Bourne shell add these lines VCS _HOME u edatools vcs7 0 2 export VCS_HOME 2 Add VCS_HOME bin to your search path If you are using the C shell enter set path VCS_HOME bin path lf you are using the Bourne shell enter PATH SVCS_HOME
159. to date available at the time of production However changes might have occurred For the latest installation information see the product release notes or documentation This chapter includes the following sections Media Availability and Supported Platforms Installing the Software on UNIX or Linux Platforms Configuring HSPICE and AvanWaves for UNIX and Linux Setting Up HSPICE and AvanWaves for Each User Verifying the HSPICE and AvanWaves Installation Installing HSPICE version U 2003 09 on UNIX or Windows Platforms 28 1 e Installing the Software on Windows Platforms e Related Documentation and Customer Support Media Availability and Supported Platforms HSPICE Interface AvanWaves and Metaencrypt are available on CD and by EST download on all platforms with the following exceptions e Interface is not available on Linux Dec Alpha SGI or Windows platforms e AvanWaves is not available on the Linux platform Obtain the appropriate binary executable files for your operating system Table 28 1 lists the supported platforms for this release Table 28 1 Platforms and Keywords Operating system Synopsys platform keywords HP UX 10 20 11 0 Solaris 2 5 8 Red Hat Linux 6 2 7 2 AIX 4 3 Windows NT 2000 XP SGI IRIX 6 5 1 DEC Alpha OSF 4 0 hp32 32 bit mode hp64 64 bit mode sparcOS5 32 bit mode sparc64 64 bit mode linux 32 bit mode rs6000 winnt win2000 winxp sgimips alp
160. tory on page 1 18 Define the SYNOPSYS environment variable see Defining the SYNOPSYS Environment Variable on page 1 19 17 1 e Have your license server running and have the appropriate license keys installed see Acquiring a License on page 1 15 Note For detailed information on operating systems and acquiring patches see Supported Platforms and Operating Systems on page 1 2 Installing the Software To download and install System Studio from the Web or by FTP follow the procedures described in Downloading and Installing the Software by EST on page 2 2 To install the System Studio software from the CD follow the installation procedure described in Installing Product Files From a CD on page 2 7 Example 2 1 on page 2 10 shows a Synopsys media installation script for the synthesis tools System Studio is installed in a similar manner Installing System Studio version V 2003 12 17 2 Setting Up System Studio for Each User Set the defaults for each user according to the user s shell and operating system Table 17 1 lists the path name and description of systemwide defaults for System Studio Table 17 1 System Studio Systemwide Defaults Path name Description SYNOPSYS_CCSS Identifies the System Studio installation directory For example SYNOPSYS sparcOS5 ccss CCSS_SIM_DIR Path to the directory for code generation and simulation results defaults to HOME ccss sim
161. tory For example enter mkdir u edatools cadabra version ed u edatools cadabra version 2 Download the software to the installation directory 3 Uncompress and untar the files gzip dc cadabra_platform_version tar gz tar xvf This command creates a Cadabra subdirectory named after the release of Cadabra that you are installing To install Cadabra from a CD 1 Mount the CD by using the appropriate command for your operating system For example enter mount o ro dev dsk c2t1id4s0 cdrom Note Mounting instructions are different for each platform See your system documentation for the correct CD mounting commands Installing Cadabra version 7 0 6 2 3 Also for sparcOS5 with vold the volume management daemon for managing CD and floppy devices the cdrom directory already exists and the CD is automatically mounted Therefore use cd cdrom cdrom0 instead of cd cdrom Create a Cadabra installation directory and change to that directory For example mkdir u edatools cadabra version ed u edatools cadabra version Uncompress and untar the files gzip dc cdrom cadabra7 0 cadabra_platform_version tar gz tar xvf This command creates a Cadabra subdirectory named after the release of Cadabra that you are installing Unmount the CD by using the appropriate command for your operating system For example enter umount cdrom Note If you are running the volume management daem
162. up requirements see the product specific chapters in the Installation Guide at http www synopsys com support Install_Guide html Thank you Example 2 2 shows a sample Synopsys media installation script for version V 2003 12 of the PrimeTime tools it applies to installation by EST and from the CD Other version V 2003 12 tools are installed in a similar manner Example 2 2 Synopsys Media Installation Script for PrimeTime Synopsys Media Installation Instructions The list within shows the choices for a given option The entry within shows the default selection when you hit the Return key You can cancel the installation by entering quit when prompted for input The current mounted Synopsys CD file system is V 2003 12 VERSION V 2003 12 PRODUCTS pts PLATFORMS sparcOS5 sparc64 PART NUMBER XXXXXX Install V 2003 12 release y n y y NOTE The product s pts on this CD ROM must be installed ina stand alone directory Enter the full path to the directory where you want to install Synopsys V 2003 12_pts products If the directory does not exist it will be created usr synopsys usr synopsys pts_V 2003 12 Creating Synopsys root directory usr synopsys pts_V 2003 12 Product s selected pts The Platform Independent Package for a particular product contains support files that are common to all the platforms You must install this package for each product if you are installing it to the
163. ust create a separate empty directory to download your product files into For example ole mkdir tmp product cd tmp product 2 Start an FTP session to ftp synopsys com o ftp ftp synopsys com 3 Enter your SolvNet user name and password 4 At the ftp prompt enter the following commands tp gt binary tp gt cd rev tp gt cd productname_productversion tp gt get productname_productversion_common tar tp gt get productname_productversion_platform tar Hh Hh Hh Hh Hh For a list of supported platforms and products for this release see Table 1 2 on page 1 6 5 Download the files into the directory you just created 6 For installation instructions see Performing EST Installation on page 2 6 Downloading and Installing the Software 2 4 Downloading the Files From the Web To download files from the Web 1 For each tool you must create a separate temporary directory to download your product files into For example oe mkdir tmp product cd tmp product Go to the Electronic Software Transfer EST Web page at http www synopsys com cgi bin est cgi Click the Authenticated Access button Enter your SolvNet user name and password Read the legal page and if you agree click Yes agree to the above terms Click the rev folder Click the file folder for the product and version you want to install Download the files into the temporary directory Note For each product
164. verts it to binary format Installing TCAD Products and Utilities 31 21 The tfatoa and tfotob utilities are useful if you have TCAD products on multiple machine types A binary file can be transferred between machines by converting it to ASCII on one machine and then transferring it to the second machine Then it can be converted back to binary on the second machine Following is the directory structure of the utility directory as it exists in a standard installed TCAD directory tree The directories are shown with a trailing slash TCAD directory bin TCAD product utility Vt install_utility replot replot replotx rppdev rperr0 tfatob tfatob tfat tfbt tfbt tfer tma tma tmap tmap tmap tfbt tfbt tfer Note OVX oa oax ro fork fork Lot Lot Lotx oa oax ro The TCAD utilities do not require licenses You can use them on any machine un der the direct control of your organization However you are not allowed to copy or distribute the TCAD utilities elsewhere Installing TCAD Products and Utilities 31 22 Executing the TCAD Utilities To execute the TCAD utilities you must include the tcad bin directory in your search paths as described in Setting Up Your Search Path on page 31 9 If you install updates to the TCAD utilities in the future the installation script creates links from the new version of the TCAD utilities to the tcad bin directory Therefore once the
165. ynopsys syn_V 2003 12 tar xvfp sparcos5 Downloading and Installing the Software 2 11 INSTALLING sf3 product sparcos5 package V 2003 12 version uncompress lt sparcos5 sf3 taz cd usr synopsys syn_V 2003 12 tar xvfp Installing Design Compiler Installing Module Compiler Installing Library Compiler Installing Physical Compiler Setting up environment for Astro Installing Synopsys Integrator for Falcon Framework version C Synopsys Site Identification Number appears on the upper right corner of your Synopsys License Key Certificate Synopsys Site Identification Number Hit return for 000 000 Synopsys License Administrator is a person who must be contacted for Synopsys product related administrative tasks at your site Local Synopsys License Administrator Hit return for customer License Administrator Contact is the current phone number and or Email address of customer License Administrator Contact Hit return for and or user email Created site file usr synopsys syn_V 2003 12 admin license site_info Installation is complete To use this software you must be running the Synopsys Common Licensing SCL version 8 4 daemon snpsimd on your license server For more information on SCL 8 4 see the Synopsys Licensing QuickStart Guide at http www synopsys com keys Downloading and Installing the Software 2 12 For any post installation set
166. you use them Your system administrator should analyze the files when System Studio is installed The relevant commands are cd SSYNOPSYS_CCSS packages vsscli sre vhdlan nc ccss_vsscli_package vhdl cd SSYNOPSYS_CCSS platform ccss packages bittrue vhdlsynopsys sre whdlan nc ccss_PACKAGE SYNOPSYS vhdl LIB 0 0 1 PACKAGE SYNOPSYS vhdl ol ol Verifying the System Studio Installation To verify the System Studio installation 1 Make sure you are in a directory where you have read write privileges ed HOME 2 Invoke the tool by entering the following command CCSS amp If System Studio is correctly installed this command invokes System Studio displays the System Studio welcome screen and then opens System Studio Installing System Studio version V 2003 12 17 6 Troubleshooting Startup Problems This section addresses common startup problems Key File Problems To test the System Studio installation start the System Studio Design Center If the software does not start check the contents of the key file as follows 1 If you are using a network license file check the first line of the key file and make sure the host name and the host ID match those of the machine on which the license is running SERVER hostname hostid 26585 If you are using a network license file check the second line of the key file and make sure the path to snpsimd exists and is correct VENDOR snpslmd scl_root platfor
167. your path you must use specific commands In this example the TCAD directory on your system is named usr myaccount tcad Installing TCAD Products and Utilities 31 10 e To permanently add this directory to your search path add the following line to your HOME profile or HOME kshrc file PATH usr myaccount tcad bin SPATH export PATH Save your changes e Enter one of the following commands profile or kshre Setting the User Environment to Find the TCAD License When you start a TCAD tool the tool looks for a license in this order e The default location TCAD directory license license dat e TMALIC e LM_LICENSE_FILE The TMALIC and LM_LICENSE_FILE environment variables point to the license server For example setenv LM_LICENSE_FILE path to license dat Installing TCAD Products and Utilities 31 11 Running TCAD Products Table 31 5 lists the general format for most TCAD products For product availability for this release see Supported Platforms and Media Availability on page 31 2 If you install multiple versions of a product the executable name is whatever you chose during installation For most products if you run them without specifying an input file you are in interactive mode Table 31 5 Products and Keywords Product Format Description Aurora aurora input_filename Runs Aurora with an input file Aurora auroragui Runs the Aurora GUI Davinci davinci in
168. ze unlimited datasize 524280 kbytes stacksize 8192 kbytes coredumpsize unlimited descriptors 256 memorysize unlimited Troubleshooting 24 4 If your user level data size limit is too low you can increase it by entering limit datasize xxxxm atthe UNIX prompt where xxxx is the number of megabytes and m stands for megabytes For example limit datasize 3891m Note The limit command is a built in C shell csh command Make sure you are in csh before you execute limit For additional information about the 1imit command see the appropriate man page On HP systems you cannot change the user level limits User level limits can be changed only at the system level The procedure for making limit changes varies from platform to platform The system administrator at each site should be familiar with the procedure If you still encounter problems contact your ncuSynopsys technical representative X Window System Some common X Window System problems and possible solutions are the following e If you cannot use the vi text editor in the xterm window add an xterm entry in your etc termcap file Troubleshooting 24 5 If after an upgrade you can no longer open Design Analyzer from your host verify that the fonts assigned in synopsys_dc setup or the server default fonts are loaded A fatal error results if the fonts are not available Your xinitrc script might not be read on startup because it is a C shell script In t

Download Pdf Manuals

Related Search

Related Contents

User Manual    DL100 Pro – CANopen® Entfernungs-Messgerät  ブルネックボンペ取扱説明書  Premier Mounts UNI-PDSB project mount  215080_d_man.  DPP 1200 System Setup Guide  the great outdoors by Minka Lavery 8690-61 Installation Guide    

Copyright © All rights reserved. Failed to retrieve file