Analyzing Post-Map Static Timing

ISE

You can analyze the timing results of the Map process by opening the static timing report and the NCD file in Timing Analyzer. Post-map timing reports can be very useful in evaluating timing performance. Although route delays are not accounted for, the logic delays can provide valuable information about the design. If logic delays account for a significant portion (> 50%) of the total allowable delay of a path, the path may not be able to meet your timing requirements when routing delays are added. Routing delays typically account for 45% to 65% of the total path delays. By identifying problem paths, you can eliminate potential problems before investing time in place and route.

You can redesign the logic paths to use fewer levels of logic, tag the paths for specialized routing resources, move to a faster device, or allocate more time for the path. If logic-only delays account for much less (<35%) than the total allowable delay for a path or timing constraint, then the place and route program can use very low placement effort levels. In these cases, reducing effort levels allow you to decrease runtimes while still meeting performance requirements.

To Analyze Post-Map Static Timing

In the Design panel, select Implementation from the Design View drop-down list.
In the Hierarchy pane, select the top module .
In the Processes pane, expand Implement Design, and expand Map.
Right-click Generate Post-Map Static Timing, and select Process Properties. Make the appropriate selections for the report details in the Post-Map Static Timing Report Properties.
Expand Generate Post-Map Static Timing, and double-click the Analyze Post-Map Static Timing process.

The static timing report (TWX file) and NCD file opens in Timing Analyzer.

Note For more information on using Timing Analyzer, see the Timing Analyzer Help. In the Help Viewer, click the Synchronize TOC button

to view all related Help topics.