Setting Up Your Environment

When installation of the Xilinx software completes, verify that your .cshrc or setup file contains lines similar to those outlined in the following subsections.

NOTE

In the following variable settings, platform is sun (Sun4), sol (Solaris), or hp (HP-UX).

Required Environment Variables (All Platforms)

Verify the set up of the following variables.

setenv XILINX path_to_Xilinx_root_dir

path_to_Xilinx_root_dir is the location of the Xilinx software.

If using the Motif version of DynaText or the EPIC editor, you must set an environment variable to access the set of Key bindings used by a Motif application. Typically, an XKeysymDB file installs into your $XILINX/bin/platform directory during the Xilinx install. Do the following to access this file.

setenv XKEYSYMDB $XILINX/bin/platform/XKeysymDB

Failure to set up this environment variable results in the following types of messages displaying when you attempt to start up the DynaText viewer. You cannot use listed keys.

   Warning: translation table syntax error: Unknown keysym name: osfActivate

   Warning: ... found while parsing ': <Key>osfActivate:ManagerParentActivate()fDown

Set your LM_LICENSE_FILE variable to point to the Xilinx license file (license.dat).

setenv LM_LICENSE_FILE path_to_Xilinx_license_file ;\ path_to_Cadence_license_file

Make sure the set up of the LD_LIBRARY_PATH points to the Xilinx software. Add the path to your current path for Sun or Solaris.

setenv LD_LIBRARY_PATH \ $XILINX/bin/platform:${LD_LIBRARY_PATH}

NOTE

The backslash (\) at the end of a line is a continuation character indicating that the line wraps to the next line. Use the backslash character only as the last character on the line.

If using a Sparc station, set LD_LIBRARY_PATH as follows.

setenv LD_LIBRARY_PATH \ $XILINX/bin/platform:${LD_LIBRARY_PATH}: \ /usr/openwin/lib

If using an HP workstation, set the SHLIB_PATH.

setenv SHLIB_PATH ${XILINX}/bin/hp : /lib : \ /usr/lib

Concept Environment Setup

In addition, you must set your Concept environment variables in your .cshrc shell or setup file and configure your Concept startup and library files.

Concept Environment Variables

Set the CDS_INST_DIR environment variable to the location of your Cadence installation directory in your .cshrc or setup file.

setenv CDS_INST_DIR location_of_Cadence_tools

NOTE
You can create a soft link called “tools” under $CDS_INST_DIR, and link it to the directory $CDS_INST_DIR/tools. platform, where platform is “hppa” (for the HP) or “sun4v” (for Solaris). For example, to create a link called “tools” to your “tools.sun4v” Cadence subdirectory (Solaris), use the following commands.

cd $CDS_INST_DIR

ln -s tools.sun4v tools

If your Cadence installation directory does not have a link called “tools,” you can either add the link yourself, or substitute “tools.platform” wherever you see “tools” in the settings.
Add CDS_INST_DIR to your path in your .cshrc or setup file.

set path = ($CDS_INST_DIR/tools/bin \ $CDS_INST_DIR/tools/pic/picdesigner/bin \ $CDS_INST_DIR/tools/editor/lib $path)

Concept Setup Library Files

Before you begin design entry, verify the proper set up of your Concept setup files. These four files include startup.concept, cds.lib, global.cmd, and master.local. Ensure the files reside in your current working Concept directory. Xilinx provides examples of each of these files in $XILINX/cadence/examples.

Use a text editor to modify your startup.concept file so that you can run HDL Direct. Add the following lines to the file to enable HDL Direct.

set hdl_direct on set hdl_checks on set check_signames on set check_net_names_hdl_ok on set check_port_names_hdl_ok on set check_symbol_names_hdl_ok on set capslock_off

HDL Direct runs automatically when you write your design, writing error and warning messages to the Concept HDL Direct window and to the hdldir.log file.

You can also set these commands directly in Concept by entering them in the Concept command window.

Include the command, “set capslock_off,” in the startup.concept file.

set capslock_off

With this command, Concept maintains the case of the property strings that you add to the design, important when you define linked properties that reference other pre-defined properties, such as linked timespecs. The referencing of pre-defined timespec properties is case-sensitive. HDL Direct writes out these properties to the viewprp file when you save a Concept drawing. Additionally, HDL Direct preserves the case of all properties with the capslock key “off,” thus maintaining case to the viewprps.prp file in the logic view (directory) for the appropriate Concept drawing.

You do not have to enter this command in the startup file. However, if you do not enter the command, make sure that you enter the command at the command line prompt in Concept before you assign property values. If you do not enter the capslock_off command first, the values convert to upper case by default, which can cause problems when defining new TIMEGRPS from existing groups declared in lower case.
Create a cds.lib file in your current working Concept directory that points to the VAN-compiled library for the Xilinx architecture you use. Concept and CONCEPT2XIL scripts require cds.lib file configuration.

CONCEPT2XIL writes out an EDIF netlist for you based on library components it reads out of the appropriate library in cds.lib. The library it reads depends on the value you specify for the -family option. The following shows an example cds.lib file for the xce4000x architecture.
```
   define xce4000x_syn full_path_to_Xilinx_sofware/cadence/data/xce4000x_syn
```
In this example, xce4000x_syn is the VAN-compiled library for XC4000EX/XL/XV devices.
Update your global.cmd file to point to the appropriate Xilinx Concept libraries and define the default name of the Structured Computer Aided Logic Design (SCALD) mapping file with the “use” command.

For more details about the global.cmd file, refer to the section “Global.cmd file” in Chapter 2, The Editing Environment, in the Concept Schematic User Guide. The following shows an example file for the an XC4000xl device.
```
   master_library "./master.local" ;
   library "xce4000x" 
           "hdl_direct_lib" ,
           "xcepads" ,
           "standard" ;
   use "design.wrk" ;
   root_drawing "unnamed" ;
```
A brief description of each of the library elements follows.
- xce4000x - text that points to the architecture-specific Concept XC4000EX/XL/XV library.
- hdl_direct_lib - library that contains various components to support HDL Direct methodology, including inports and outports.
- xcepads - text that points to the generic Xilinx pad library.
- standard - standard library that contains standard Concept components such as drawing and border symbols.
  
  All four libraries are required.
  
  When accessing a library, Concept searches through the libraries following a “last read, first out” scheme. For the sample global.cmd file, the libraries are searched in the following order: standard, xcepads, hdl_direct_lib, and xce4000x.
  
  The use command specifies the work or project library listing file from which to read and view existing design names in Concept, and where to write listings for new design blocks from Concept. For example, use "design.wrk"; indicates that design.wrk is the work file.
  
  FILE_TYPE = LOGIC_DIR;
  
  "DESIGN1" 'design1'; "DESIGN2" 'design2';
  
  END.
  
  design1 and design2 are the names of the design blocks for this project.
Enter the references to any user libraries into the master.local file. For more details about the master.local file, see the section “master.local Abbreviations file” in Chapter 2, The Editing Environment in the Concept Schematic User Guide. For M1, you list all Xilinx architecture libraries for Concept in the master.local file. Following is an example user library file for M1 Xilinx designs.

    file_type = master_library;

    "spartan" 'full_path_to_Xilinx_software/cadence/data/spartan/spartan.lib';
    "spartanxl" 'full_path_to_Xilinx_software/cadence/data/spartanxl/spartanxl.lib';
    "xce9000" 'full_path_to_Xilinx_software/cadence/data/xce9000/xce9000.lib';
    "xce5200" 'full_path_to_Xilinx_software/cadence/data/xce5200/xce5200.lib';
    "xce4000x" 'full_path_to_Xilinx_software/cadence/data/xce4000e/xce4000x.lib';
    "xce4000e" 'full_path_to_Xilinx_software/cadence/data/xce4000e/xce4000e.lib';
    "xce3000" 'full_path_to_Xilinx_software/cadence/data/xce3000/xce3000.lib';
    "xcepads" 'full_path_to_Xilinx_software/cadence/data/xcepads/xcepads.lib';

    end.

The xce4000x supports the XC4000EX/XL/XV architectures. The xce4000e supports the XC4000E/L architectures.

Verilog Environment Setup

Set up your Verilog environment so that you can perform functional simulation.

Set the Verilog environment variable, VERILOGEXE, to point to the location of your Verilog executables.

setenv VERILOGEXE $CDS_INST_DIR/tools/\ verilog/bin/verilog
Set VENVHOME to the location where the Verilog 2.0 hierarchy resides. This variable assists you with setting the VENV_PATH and VENV_LD_LIB_PATH variables, usually the same as CDS_INST_DIR.

setenv VENVHOME /tools/cadence97A
Set VENV_PATH to the location of the Verilog executables.

setenv VENV_PATH "${VENVHOME}/\ tools/bin:${VENVHOME}/tools/dfII/bin”
Set VENV_LD_LIB_PATH to the location of libraries used by Verilog.

setenv VENV_LD_LIB_PATH ${VENVHOME}/\ tools/lib:${VENVHOME}/tools/verilog/lib
Reset your PATH variable to add the Verilog executables.

set PATH="${VENV_PATH}:$PATH"
Add the Verilog libraries to the LD_LIBRARY_PATH environment variable.

setenv LD_LIBRARY_PATH \ "${VENV_LD_LIB_PATH}:$LD_LIBRARY_PATH"

If using an HP platform, use the SHLIB_PATH instead of LD_LIBRARY_PATH.
(Optional) Set up the environment variable CDSDIR. The Verilog Language Sensitive Editor (LSE) requires this variable.

setenv CDSDIR $CDS_INST_DIR/tools

Dynatext Environment Variables

Set up the EBTRC variable to point to the DynaText browser.

setenv EBTRC $XILINX/bin/platform/ebtrc_CD