Option Files

The options for all programs that are part of a flow are contained in option files. These files have an .opt extension. Xilinx provides option files for each flow type. Refer to the previous flow file subsections for a listing of the installed option files.

• -config (Create a BIT File for FPGAs)
  
  
• -fit (Fit a CPLD Device)
  
  
• -fsim (Perform a Functional Simulation)
  
  
• -implement (Run FPGA implementation)
  
  
• -tsim (Perform a Timing Simulation)
  
  

The option files are located in the $XILINX/xilinx/data or $XILINX/epld/data directories.The option file data is in ASCII format, which can be edited.

Option File Structure and Content

For each program in the flow file, the option file has a corresponding program block. This block lists the default command line options that are enabled. Preceding each block is a comment section with help messages to obtain the list of all command line options for a program.

Options in the option file can be switches, files, or parameter files.

• Switches
  
  Switches that do not require any arguments, that is, the switch enables or disables a specific operation. For example. -r
  
  Switches that require one or more arguments that are strings or integers. For example, -pl 5 or -cm area.
  
  Switches that accept values in the format option value:value. For example, -g DonePin:PULLUP;
  
  
• Files
  
  This category includes command line options that are just file names.
  
  Example:
  
  calc.pcf;
  
  
• Parameter files
  
  This category specifies parameters for programs in a flow. All the parameters are written into a file.
  
  Example:
  
  CTL file for program hitop for CPLD devices. The option file for CPLD flow has the following entry for program "hitop" to create the CTL file.
  
  

  Program hitop 
  
      -f <design>.ngd; 
  
      -d <design>; 
  
      -l <design>.log 
  
      ParamFile: <design>.ctl 
  
          "DT_SYNTHESIS:TRUE"; 
  
          "MC9500_INPUT_LIMIT: 36"; 
  
          "GSR_OPT; TRUE"; 
  
      End ParamFile 
  
  End Program hitop

  
  
  

For this example, XFLOW creates a CTL file, design.ctl with all the parameters listed in the option file.

Option File Sample

Following is an option file, balanced.opt, that is used with the
-implement flow type. For the most up-to-date version of the file, see the file located in $XILINX/xilinx/data.

FLOWTYPE = FPGA;

###############################################################

## Filename: balanced.opt

##

## Option File For Xilinx FPGA Implementation Flow

## $Header: /devl/xcs/repo/env/Jobs/Xflow/data/optionfiles/Attic/fpga_balanced.opt,v 1.1.4.1 1999/03/04 02:33:19 jayr Exp $

## Version: 1.0.0

###############################################################



# Options for Translator

#

# Type "ngdbuild -h" for a detailed list of ngdbuild command line options

#

Program ngdbuild 

-p <partname>;        # Partname to use - picked from xflow commandline

-nt timestamp;        # NGO File generation. Regenerate only when

                      # source netlist is newer than existing 

                      # NGO file (default)

-u;                   # Allow unexpanded blocks in output NGD design

<userdesign>;         # User design - pick from xflow command line

<design>.ngd;         # Name of NGD file. Filebase same as design filebase

End Program ngdbuild



#

# Options for Mapper

#

# Type "map -h <arch>" for a detailed list of map command line options

#

Program map

-o <design>_map.ncd;  # Output Mapped ncd file

<design>.ngd;         # Input NGD file

<design>.pcf;         # Physical constraints file

END Program map



#

# Options for Post Map Trace

#

# Type "trce -h" for a detailed list of trce command line options

#

Program post_map_trce

-e 3;                 # Produce level 3 error report

-o <design>_map.twr;  # Output trace report file

<design>_map.ncd;     # Input mapped ncd

<design>.pcf;         # Physical constraints file

END Program post_map_trce



#

# Options for Place and Route

#

# Type "par -h" for a detailed list of par command line options

#

Program par

-w;                   # Overwrite existing placed and routed ncd

-ol 2;                # Overall effort level

-d 0;                 # Number of delay based cleanup passes

<design>_map.ncd;     # Input mapped NCD file

<design>.ncd;         # Output placed and routed NCD

<design>.pcf;         # Input physical constraints file

END Program par



#

# Options for Post Par Trace

#

# Type "trce -h" for a detailed list of trce command line options

#

Program post_par_trce

-e 3;                 # Produce level 3 error report

-o <design>.twr;      # Output trace report file

<design>.ncd;         # Input placed and routed ncd

<design>.pcf;         # Physical constraints file

END Program post_par_trce