The following syntax creates a bitstream from your NCD file.
bitgen [options] infile[.ncd] [outfile] [pcf_file]
options is one or more of the options listed in the “BitGen Options” section.
Infile is the name of the NCD design for which you want to create the bitstream. You may specify only one design file, and it must be the first file specified on the command line.
You do not have to use an extension. If you do not, .ncd is assumed. If you do use an extension, it must be .ncd.
Outfile is the name of the output file. If you do not specify an output file name, BitGen creates one in the input file's directory. If you specify -l on the command line, the extension is .ll (see -l command line option). If you specify -m (see -m command line option), the extension is .msk. If you specify -b, the extension is .rbt. Otherwise the extension is .bit. If you do not specify an extension, BitGen appends one according to the aforementioned rules. If you do include an extension, it must also conform to the rules.
Pcf_file is the name of a physical constraints (PCF) file. BitGen uses this file to determine which nets in the design are critical for tiedown (see the “-t (Tie Unused Interconnect)” section). BitGen automatically reads the .pcf file by default. If the physical constraints file is the second file specified on the command line, it must have a .pcf extension. If it is the third file specified, the extension is optional; .pcf is assumed. If a .pcf file name is specified, it must exist, otherwise the input design name with a .pcf extension is read if that file exists.
A report file containing all of BitGen's output is automatically created under the same directory as the output file. The report file has the same root name as the output file and a .bgn extension.
