|
|
|
At this point, the input netlist is being translated (once again), and merged into a single design file. Furthermore, the design will be mapped into CLBs and IOBs. After mapping, the design will be placed and routed. The final step in the design flow is the Configure step in which a configuration bitstream is created for downloading to a target device or for formatting into a PROM programming file.
Map performs the following functions:
After the MAP step is done, the Flow Engine shuts down and the Implement Status dialog box appears, as shown in the following figure.
The following steps show you how to use the report browser.
| Report | Description |
|---|---|
| Translation Report | Includes warning and error messages from the translation process. |
| Map Report | Includes information on how the target device resources are allocated, references to trimmed logic, and device utilization. For detailed information on the Map report, refer to the Development System Reference Guide. |
| Logic Level Timing Report | Provides a summary analysis of your timing constraints based on block delays and estimates of route delays. This report is produced after Map and prior to PAR (Place And Route). |
Notice that the Design Manager project view displays the status of the revision as (Mapped, OK). Mapped refers to the state of the design and is updated throughout the tutorial as the different compilation stages are completed. OK refers to the status of the current state and indicates no errors in the design processing.
The design has now been mapped to the target architecture. The next step involves checking the design paths for block delays.