|  | 
 
 发表于 2006-1-5 14:54:07
|
显示全部楼层 
cadence的ftp文件目录列表| AMS Methodology Kit - Installation Instructions ===============================================
 The AMS Methodology Kit is composed of (3) workshops and a software bill of
 materials based upon the Linux platform and specific software versions. The
 software IS NOT included in the AMSKIT51. It must be downloaded separately.
 
 Workshops:
 ---------
 AMS Top-Level Simulation Workshop (AMSTL)
 AMS Block Creation Workshop (AMSBC)
 Analog Driven Physical Implementation Workshop  (ADPI)
 
 Software Bill of Materials:
 --------------------------
 ADPI   AMSBC  AMSTL
 ASSURA314_USR1 (3.1.4 USR1)------------------------------- X      X      X
 *IC5141_ISR200511040915 (5.1.41.500.2.24) ---------------- X      X      X
 ICC11241_USR1 (11.2.41.01)-------------------------------- X
 IUS55_Base (IUS55 FCS P4) --------------------------------               X
 MMSIM60_USR1 (6.0.1 USR1) --------------------------------        X
 *NEOCKT32_ISR200511041410 (3.2.8 ISR) --------------------        X
 NEOCELL34_ISR200511040755 (3.4 USR2) ---------------------        X
 SOC42_USR2 (RC 5.1_USR2) --------------------------------- X
 VSDE41_USR1 (04.10_USR1.150) -----------------------------        X
 Note: * If an ISR is no longer available, use a newer software version.
 Installed Disk Space Requirements:
 ---------------------------------
 ASSURA314_USR1    1.187 GB      ADPI         124 MB
 IC5141_ISR24      2.965 GB      AMSBC               40 MB
 ICC11241_USR1     0.305 GB      AMSTL              799 MB
 IUS55_FCS         2.004 GB      EtherPHY DB        770 MB
 MMSIM60_USR1      1.204 GB
 NEOCELL34_USR2    0.326 GB
 NEOCKT32_ISR8     0.650 GB
 SOC42_USR2        1.479 GB
 VSDE41_USR1       0.453 GB
 Software BOM     10.573 GB      Workshop Total   1.692 GB
 
 Installation of the AMS Methodology Kit assumes the use of InstallScape for
 BOTH Installation and Configuration steps. The downloaded files are encrypted
 and will require a license with the feature AMS_Methodology_Kit be available
 from your license server. During the installation process, the Configuration
 step will attempt to checkout this license feature and if it cannot,
 installation of AMSKIT will fail.
 
 -------------------------------
 Section 1: Setting Up Licensing
 -------------------------------
 1. You must have received a new license file from Cadence that contains
 AMS_Methodology_Kit license.
 2. If you have already setup your license server to serve AMS_Methodology_Kit
 license then proceed to step 6.
 3. If you have a license and you need help setting up the license server please
 contact support@cadence.com for further assistance.
 5. If you do not have a license, please contact your Cadence representative for
 further assistance.
 6. set CDS_LIC_FILE environment variable to point to your license server.
 eg. setenv CDS_LIC_FILE 5280@server1.
 Make sure this variable is set in your .cshrc or .profile so that it is
 globally visible.
 
 -------------------------------
 Section 2: Running InstallScape
 -------------------------------
 1. Follow the instruction for installing InstallScape at
 http://downloads.cadence.com. Use InstallScape for Installation and
 Configuration of the AMS Methodology Kit.
 2. The AMS Methodology Kit has been validated with a specific software bill of
 materials on the Linux platform. It is highly recommended that the software
 versions listed above be used with the workshops.
 
 ---------------------------
 Section 3: Kit Installation
 ---------------------------
 After installation and configuration, a collection of *.tgz files will be found
 in <kit_install_dir>/kits/AMSKIT51. Each workshop contains a setup.csh which
 will require local customization and a workshop manual in the form of a pdf
 document which may be viewed with xpdf or printed.
 
 1. To simplify the workshop setup process, create a directory such as
 <kit_install_dir>/kits/AMSKIT51/software_lnx86 which includes links or
 installations of workshop related software:
 ls <kit_install_dir>
 ASSURA314_USR1IUS55_FCS    NEOCKT32_ISR8      cds_license.dat
 IC5141_ISR24MMSIM60_USR1    SOC42_USR2
 ICC11241_USR1NEOCELL34_USR2    VSDE41_USR1
 
 2. The AMS Methodology Kit contains 3 workshops which leverage a common
 EtherPhy database. The kit is structured to operate within a defined
 directory structure which should be copied to a local workspace.
 Example script for setting up ADPI workshop:
 cd <kit_working_dir>
 cp <kit_install_dir>/kits/AMSKIT51/FLOW_ETHER_CDK090_CDB_v2.3e.tgz .
 cp <kit_install_dir>/kits/AMSKIT51/adpi_flow_workshop_5.1.0.3.tgz .
 tar zxvf FLOW*.tgz
 tar zxvf adpi*.tgz
 Example AMS Kit working directory structure:
 <kit_working_dir>/
 adpi_flow_workshop:  Analog Driven Physical Implementation Flow Workshop
 amsbc_flow_workshop: AMS Block Create Flow Workshop
 amstl_flow_workshop: AMS Top-Level Flow Workshop
 FLOW_ETHER_CDK090:   Shared design + library data. ALL workshops use this.
 To simplify the setup scripts, create a link to the workshop software
 installation directory created in step #1 of Section 3.
 
 3. Each workshop has a setup.csh which will need to be modified for your
 working environment. For the software installation, it is easiest to create
 a link from your working environment back to the kit software installation.
 For example:
 cd <kit_working_dir>
 ln -s <kit_install_dir>/kits/AMSKIT51/software_lnx86 .
 
 In the setup.csh found in each workshop directory, change the value for
 KITHOME to point to <kit_install_dir>/kits/AMSKIT51/software_lnx86. In
 addition to software setup, there are environmental variables and alias
 definitions which will be referenced by each of the workshops. Be sure to
 source the setup.csh before starting each workshop.
 
 4. Make sure the license managers are running and licenses are valid:
 
 lmstat -c $CDS_LIC_FILE -a
 
 5. While a specific sequence is not required for running the workshops, the
 recommended order is:
 a. asmtl_flow_workshop
 b. amsbc_flow_workshop
 c. adpi_flow_workshop
 
 6. Workshop pdf documents may be found in the top-level of the workshop
 directory. They may be printed or viewed using xpdf.
 
 | 
 |