|
|
|
Command Line Options
The following options are common to many of the command line programs in the Xilinx Development System.
–f (Execute Commands File)
For any Xilinx Development System program, you can store command line program options and file names in a command file. You can then execute the arguments by entering the program name with the –f option followed by the name of the command file. This is useful if you frequently execute the same arguments each time you execute a program or if the command line command becomes too long.
You can use the file in the following ways:
- To supply all the command options and file names for the program, as in the following example:
par -f command_file
command_file is the name of the file that contains the command options and file names.
- To insert certain command options and file names within the command line, as in the following example:
par -f placeoptions -s 4 -f routeoptions design_i.ncd design_o.ncd
placeoptions is the name of a file containing placement command parameters.
routeoptions is the name of a file containing routing command parameters.
You create the command file in ASCII format. Use the following rules when creating the command file:
- Separate program options and file names with spaces.
- Precede comments with the pound sign (#).
- Put new lines or tabs anywhere white space is allowed on the UNIX or DOS command line.
- Put all arguments on the same line, one argument per line, or a combination of these.
- All carriage returns and other non-printable characters are treated as spaces and ignored.
- No line length limitation exists within the file.
Following is an example of a command file:
#command line options for par for design mine.ncd-n 10-w0l 5-s 2 #will save the two best results/home/yourname/designs/xilinx/mine.ncd#directory for output designs/home/yourname/designs/xilinx/output.dir#use timing constraints file/home/yourname/designs/xilinx/mine.pcf–h (Help)
When you enter a program name followed by –help or –h, a message displays that lists all the available options and their parameters as well as the file types for use with the program. The message also explains each of the options.
Following are descriptions for the symbols used in the help message:
Following are examples of syntax used for file names:
For architecture-specific programs, such as BitGen, you can enter the following to get a verbose help message for the specified architecture:
program_name –h architecture_name
You can redirect the help message to a file to read later or to print out by entering the following:
program_name –h > filename
On the UNIX command line, enter the following to redirect the help message to a file and return to the command prompt.
program_name –h > & filename
–intstyle (Integration Style)
You can limit screen output, based on the integration style that you are running, to warning and error messages only. When using the –intstyle option, one of three modes must be specified: ise, xflow, or silent. The mode sets the way information is displayed in the following ways:
–intstyle {ise | xflow | silent}
–intstyle ise
This mode indicates the program is being run as part of an integrated design environment.
–intstyle xflow
This mode indicates the program is being run as part of an integrated batch flow.
–intstyle silent
This mode limits screen output to warning and error messages only.
Note: The -intstyle option is automatically invoked when running in an integrated environment, such as Project Navigator or XFLOW.
–p (Part Number)
You can use the –p option with the EDIF2NGD, NGDBuild, MAP, and XFLOW programs to specify the part into which your design will be implemented. You can specify a part number at the following different points in the design flow:
- In the input netlist (does not require the –p option)
- In a Netlist Constraints File (NCF) (does not require the –p option)
- With the –p option when you run a netlist reader (EDIF2NGD) User Constraints File (UCF) (does not require the –p option)
- With the –p option when you run NGDBuild
By the time you run NGDBuild, you must have already specified a device architecture.
- With the –p option when you run MAP
When you run MAP, an architecture, device, and package must be specified, either on the MAP command line or earlier in the design flow. If you do not specify a speed, MAP selects a default speed. You can only run MAP using a part number from the architecture you specified when you ran NGDBuild.
Note: Part numbers specified in a later step of the design flow override a part number specified in an earlier step. For example, a part specified when you run MAP overrides a part specified in the input netlist.
A complete Xilinx part number consists of the following elements:
Note: The Speedprint program lists block delays for device speed grades. The -s option allows you to specify a speed grade. If you do not specify a speed grade, Speedprint reports the default speed grade for the device you are targeting. See "–s (Speed Grade)" in Chapter 15 for details.
The following table lists multiple ways to specify a part on the command line.
|
|
|
|
www.xilinx.com |