Configuring RFIC Dynamic Link

This chapter describes system requirements and how to install and configure the software. You may require help from a UNIX or EDA Administrator to complete these tasks. For general system requirements, refer to Check the System Requirements in the UNIX and Linux Installation documentation.

System Requirements

This section provides a reference to the minimum hardware and operating system requirements and also describes the EDA Framework and License requirements necessary for using the RFIC Dynamic Link.

Hardware Requirements

For information on the minimum hardware requirements for installing and using RFIC Dynamic Link, refer to Check the System Requirements in the UNIX and Linux Installation documentation.

Software Requirements

The specific RFIC Dynamic Link version requires that you use a compatible Advanced Design System version. For example, if you are using RFIC Dynamic Link 2006A, you must also use ADS 2006A.

Dynamic Link supports Cadence DFII versions on UNIX & Linux operating system versions from vendors which run this Cadence software. For a summary of supported platforms, refer to Check the System Requirements in the UNIX and Linux Installation documentation, or contact Cadence Design Systems Inc.

Note that the following Cadence context files must be present under your Cadence installation directory in order to run RFIC Dynamic Link:

<Cadence Installation Dir>/tools/dfII/etc/context/spectrei.cxt

<Cadence Installation Dir>/tools/dfII/etc/context/asimenv.cxt

If either of these files is missing, please contact Cadence Design Systems Inc. for information on how to install it.

License Requirements

In addition to your standard Advanced Design System licenses, the following additional product licenses are required.

RFIC Dynamic Link License

Cadence Licenses

Installing RFIC Dynamic Link

The RFIC Dynamic Link installation procedure continues to be improved to make it easier for you to install and configure.
To install RFIC Dynamic Link:

  1. Follow instructions in the UNIX and Linux Installation documentation to run the SETUP utility and load the install program.
  2. After the Agilent EEsof Installation Manager starts, you are prompted to select one of the following installation options:
    • Typical - If you choose a Typical installation, the RFIC Dynamic Link will not be installed.
    • Complete - If you choose a Complete installation, the RFIC Dynamic Link will be automatically installed.
    • Custom - If you choose a Custom installation, you must select both Simulators and Design Entry and The RFIC Dynamic Link components from the scroll-down list in the Agilent EEsof Software Installation dialog box.
      Note
      The Simulators and Design Entry component is the basic ADS software, including the Design Environment, Data Display, and Analog/RF Systems and Signal Processing simulators. This is a minimum requirement for RFIC Dynamic Link.

  3. After the installation is complete, you will need to run the idfConfigCadence script to configure Cadence for use with RFIC Dynamic Link. This script is located under:
    $HPEESOF_DIR/bin/idfConfigCadence
    Note
    For ADS 2001, the Cadence configuration script was located at $HPEESOF_DIR/idf/config/configCadence.

    For more information on the idfConfigCadence script, refer to Customizing a Cadence Installation.

For more information on installation procedures, refer to the["../install/wwhelp.htm" UNIX and Linux Installation] documentation.

Configuring the Cadence Installation

After the installation procedure (see Installing RFIC Dynamic Link), you will need to run the idfConfigCadence script if you want to customize your Cadence installation for Dynamic Link. This script configures the Cadence install directory for use with ADS by adding or modifying five files.

If you prefer not to modify your existing Cadence installation(s), refer to the section on Avoiding Modifications to Your Cadence Installation.

Note
You must have write access to your Cadence install directory in order to run the idfConfigCadence script.

The following files are created:

<Cadence Installation Dir>/tools/dfII/etc/tools/ads/.cdsenv

<Cadence Installation Dir>/tools/dfII/etc/tools/ADSsim/.cdsenv

<Cadence Installation Dir>/tools/dfII/etc/tools/adsDL/.cdsenv

<Cadence Installation Dir>/share/cdssetup/hierEditor/templates/ads

<Cadence Installation Dir>/tools/dfII/etc/skill/hnl/ads.ile

<Cadence Installation Dir>/tools/dfII/etc/skill/si/caplib/ads.ile

An additional file, <Cadence Installation Dir> /tools/dfII/etc/tools/auCore/.cdsenv, is edited to add ads to the Tool Filter list of simulators.

Note
The files described in this section are created or modified based on detailed instructions provided in the Cadence OASIS Direct Integrator's Guide . The information in the Cadence manual __ describes how to integrate a simulator into the Cadence Analog Design Environment using the Cadence direct toolkit .

Important While deviating from the information described in the Cadence OASIS Direct Integrator's Guide may work for RIFC Dynamic Link, the files have been specifically set up to follow the Cadence documentation. Agilent Technologies does not support deviations from this information.
For more information, refer to the Cadence documentation:
- OASIS Integrator's Guide , Product Version 4.4.5, December, 1999 - Pages 4-12, 4-13, 6-2 and 6-6.
- OASIS Direct Integrator's Guide , Product Version 4.4.6, September, 2001- Pages 67, 101 and 105.

Customizing a Cadence Installation

Before running the idfConfigCadence script, set HPEESOF_DIR to your ADS installation directory and set your PATH to include Cadence software.

The idfConfigCadence command uses the following general syntax:
idfConfigCadence {-h | -ls | -rm}

Simply entering idfConfigCadence at the command line with no options runs the script to configure Cadence for RFIC Dynamic Link. The following table shows a list of the options and definitions used by the idfConfigCadence command.

Option Definitions for idfConfigCadence
Option Definition
-h This option can be used to display the idfConfigCadence help file.
-ls This option can be used to list the Cadence configuration files for ADS/RFIC Dynamic Link and indicate whether Cadence is ready for ADS RFIC Dynamic Link or not.
-rm This option removes the Cadence configuration for ads/RFIC Dynamic Link by deleting the files previously installed with the idfConfigCadence script and removing ads from the Cadence tool Filter. For more information on the Cadence Tool Filter, refer to your Cadence documentation.

Understanding the idfConfigCadence Script

When the idfConfigCadence script is executed without any options, the script performs the following operations:

Customizing Multiple Cadence Installations

The idfConfigCadence script configures the Cadence installation directory for use with Dynamic Link. However, if a new version of the Cadence software is subsequently installed or you have multiple Cadence installations, neither will have the Dynamic Link configuration. In this case, you would need to run the idfConfigCadence script as described in Configuring the Cadence Installation for each Cadence installation.

Avoiding Modifications to Your Cadence Installation

If you do not want to change your Cadence installation or create a Cadence shadow directory tree for RF Design Environment (RFDE) or RFIC Dynamic Link, there is an alternative approach available. You will need to set the following three environment variables before starting Cadence Design Framework II:

CDS_LOAD_ENV=CSF

ossSimUserHnlDir=$HPEESOF_DIR/idf/ads_site/hnl

ossSimUserSiDir=$HPEESOF_DIR/idf/ads_site/si

In addition to the above, you will need to add the following path to your setup.loc file:

$HPEESOF_DIR/idf/ads_site

Sourcing the setCSF.ksh (or setCSF.csh) sample script under $HPEESOF_DIR/bin is one method of accomplishing the tasks above. Assuming you are using the Korn shell, the following is a list of steps for using the sample scripts to setup the environment for RFDE or Dynamic Link in order to work with your original Cadence installation:

  1. Change to a directory where you have write permission. For example, 

    cd /tmp

  2. Set your HPEESOF_DIR to your RFDE or ADS installation root directory.
  3. Add $HPEESOF_DIR/bin to your path. For example, 

    PATH=$HPEESOF_DIR/bin:$PATH

  4. Ensure your Cadence and Agilent licenses are set correctly for your environment.
  5. Ensure that the Cadence <cadence_installation_root> /tools/bin and <cadence_installation_root> /tools/dfII/bin directories are in your PATH.
  6. Set the CDS_LOAD_ENV, ossSimUserHnlDir, ossSimUserSiDir, and setup.loc files appropriately. For example, if using the Korn Shell, 

    . $HPEESOF_DIR/bin/setCSF.ksh

    If you are using the C Shell, use the following command, 

    source $HPEESOF_DIR/bin/setCSF.ksh

  7. Ensure that you have included RFDE Libraries. For example, 

    echo INCLUDE \$HPEESOF_DIR/cdslibs/rfde.lib > cds.lib

  8. Ensure that the RFDE and Dynamic Link startup file ads.ini will be loaded upon starting Cadence Design Framework II. For example, 

    cp $HPEESOF_DIR/idf/examples/.cdsinit .

  9. Launch Cadence by entering icms& or msfb&.
    If Cadence fails to locate the RFDE or Dynamic Link OASIS files under your Cadence installation, the software will look for these OASIS files under $HPEESOF_DIR/idf/ads_site.
    The alternate search location will be used because of the way CDS_LOAD_ENV, ossSimUserHnlDir, ossSimUserSiDir, and setup.loc are set in step 6 above. RFDE and Dynamic Link will still operate normally with your original Cadence installation. This may be the prefered approach when you have multiple Cadence installations, in which case you would need to add RFDE OASIS files to every individual installation or create a shadow directory for each installation.
    According to the Cadence Application Infrastructure User Guide, Product Version 5.01 , Cadence looks for the Cadence setup search file, $CDS_SITE/cdssetup/setup.loc, if $CDS_SITE is defined in the environment; otherwise, it will look for <your_installation_directory> /share/cdssetup/setup.loc.
    For more information about CDS_LOAD_ENV, CSF, setup.loc, or OASIS, refer to your Cadence documentation or contact your Cadence customer support representative.

Configuring the Software

This section describes the various aspects of configuring and/or modifying the software to provide additional flexibility.

Configuring the UNIX Environment

There are several UNIX environment variables relevant to Dynamic Link. These are described in the following table.

UNIX Environment Variables
Environment Variable Description
IDF_CONFIG_FILE The name of the configuration file (only the file name, not the entire path). Default value is idf.cfg.
IDF_ADS_PROJ_DIR If this environment variable is defined, ADS will attach to the specified project when RFIC Dynamic Link launches ADS.
IDF_DEBUG_MODE If set to TRUE debugging will be turned on and additional log messages will be written to the CIW; the log files mps.log and emx.log are also created. Default value is FALSE.
IDF_LOG_FILE Name of the file (only the file name, not the entire path) to which ADS messages, normally written to stderr are redirected. Default value is idf.log .
PATH The UNIX path variable.

Configuring the ADS Install Directory

The installation procedure configures the ADS install directory by automatically adding, modifying or replacing some files and/or directories.
The following files and/or directories are created, modified or replaced: 

$HPEESOF_DIR/bin/idfmp
$HPEESOF_DIR/bin/idf
$HPEESOF_DIR/bin/idfConfigCadence
$HPEESOF_DIR/idf
$HPEESOF_DIR/idf/ael
$HPEESOF_DIR/cdslibs
$HPEESOF_DIR/idf/config
$HPEESOF_DIR/idf/examples
$HPEESOF_DIR/idf/skill
$HPEESOF_DIR/circuit/symbols/idfSymbol.dsn
$HPEESOF_DIR/tools/lib/dpkg/info/idf\*

Modifying the RFIC Dynamic Link-Cadence Initialization File

The RFIC Dynamic Link-Cadence initialization file ( .cdsinit) is located in the directory $HPEESOF_DIR/idf/config/.cdsinit . Append it to or load it from the first available .cdsinit file from the list below:

Modifying the Configuration File

Dynamic Link comes with the default configuration file $HPEESOF_DIR/idf/config/idf.cfg . This file is used to set various site-specific or user-specific options. It is searched for and read sequentially from the following locations in the order given, so that settings in files read later override those of earlier files:

$HPEESOF_DIR/idf/config/

$HOME/hpeesof/config/

./

The name of the configuration file can be set via the UNIX environment variable IDF_CONFIG_FILE. By default the configuration file is named idf.cfg .
The configuration file consists of lines in the form < parameter > = < value >. The various parameters that can be set in the configuration file are listed below, with brief descriptions and an example for each. If no configuration file is found or some parameters are not set, internal default values are used. Note that wherever a file name is required for a configuration parameter value, it may be specified with a path prefix that is a UNIX environment variable value or using standard UNIX conventions such as ~. A complete example configuration file can be found at the end of this section.

Example Configuration File

IDF_SWITCH_VIEW_LIST = "ads sch.model schematic"

IDF_NETLIST_FILTER = "~/bin/mynetlistfilter"

IDF_NETLIST_SUFFIX = ".net"

Managing Projects and Designs

Your Cadence designs will remain in their original locations. They are not copied, translated, or otherwise modified. When ADS starts up in Dynamic Link mode, it puts you in a project directory defined by the IDF_ADS_PROJ_DIR environment variable. If this variable is not defined, only the ADS Main window will open and no project will be attached. This is the recommended option.

To change this behavior, you can do one of the following:

For more information on projects and design files, refer to Managing Projects and Designs in the Schematic Capture and Layout documentation.

 

Privacy Statement  | Terms of Use  | Legal | Contact Us  | © Agilent 2000-2008 

Contents
Additional Resources