We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 5684

2.1i Design Manager - Non-timing driven implementation of Virtex/Virtex-E/Spartan-II can result in lower design performance


Keywords: Virtex, Virtex-E, Spartan-II, lower, performance, par, bad, results

Urgency: HOT

General Description:

To improve runtime for timing driven implementation, the PAR command line
defaults for the Virtex, Virtex-E, and Spartan-II families in M2.1i have
changed to NOT run Cost Based and Delay Based Clean-up passes. Because of
this change, you may notice lower design performance results from PAR when
targeting these families. This will occur on designs that are run in M2.1i with
no timing constraints applied (non-timing driven).


To get a more "realistic" estimate of how your design will perform without any
timing constraints applied, please follow this recommendation:

1. Implement your design until PAR has completed.
2. Open up the Flow Engine on your (Routed,OK) revision.
3. Under Setup-> FPGA Re-entrant Route, specify the number of
clean-up passes to be run.
4. Click OK
5. In the Flow Engine, select Flow->Step Back
6. Select Flow->Run

Check the Reports Browser (P&R Report/Post Layout Timing Report) for improved
performance results.
AR# 5684
Date Created 02/16/1999
Last Updated 06/13/2002
Status Archive
Type General Article