Development System Reference GuideChapter 8: MAP - The Technology Mapper
MAP Syntax
The following syntax maps your design.
map [options] infile[.ngd] [pcf_file[.pcf]]
Options can be any number of the MAP options listed in the MAP Options section. They do not need to be listed in any particular order. Separate multiple options with spaces.
Infile[.ngd] is the input NGD file. You do not have to enter the .ngd extension.
Pcf_file[.pcf] is the Physical Constraints File in PCF format. A constraints file name is optional on the command line, but if one is entered it must be entered after the input file name. You do not have to enter the .pcf extension. The constraints file name and its location are determined in this way.
- If you do not specify a physical constraints file name on the command line, the physical constraints file has the same name as the output file, with a .pcf extension. The file is placed in the output file's directory.
- If you specify a physical constraints file with no path specifier (for example, cpu_1.pcf instead of /home/designs/cpu_1.pcf), the .pcf file is placed in the current working directory.
- If you specify a physical constraints file name with a full path specifier (for example, /home/designs/cpu_1.pcf), the physical constraints file is placed in the specified directory.
- If the physical constraints file already exists, MAP reads the file, checks it for syntax errors, and overwrites the schematic-generated section of the file. MAP also checks the user-generated section for errors and corrects errors by commenting out physical constraints in the file or by halting the operation. If no errors are found in the user-generated section, the section remains the same.
For a discussion of the output file name and its location, see the -o (Output File Name) section.