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# 35556

11.5 Route - Is there a way to lock the results of a successful route?


I have a few critical paths in my design that aren't always routed optimally. Is there a way to lock the successful route results for these nets.


The routing from a successful implementation run can be locked using Directed Routing constraints. In order for this to work the net connectivity must remain the same and the relative location of all of the pins in net must be maintained. The constraints to reproduce the routing and relative pin location are captured in FPGA Editor using the Tools-->Direct Routing Constraints pull-down menu which opens the following form:

Using this form, nets can be chosen to capture routing constraints as well as place or pack constraints to control the relative pin location. Choose "Use Absolute Location Constraint" to lock the logic to its current location. Choose "Use Relative Location Constraint" to create an RPM macro that will maintain the relative pin locations in a movable macro. The constraints generated will be written to a UCF file and look like this:

NET "u_qdr2_top/QDR_PHY0/READ_INST/rd_data_fall[35]"
INST "u_qdr2_top/QDR_PHY0/READ_INST/DLY_CAL_SM_INST_CQ_N_18/rd_data_fall_r_17" LOC=SLICE_X5Y88;
INST "u_qdr2_top/QDR_PHY0/READ_INST/DLY_CAL_SM_INST_CQ_N_18/rd_data_fall_r_17" BEL="CFF";
INST "u_qdr2_top/QDR_PHY0/READ_INST/PHY_EN_INST/rd_data_fall_out_35_mux00001" LOC=SLICE_X6Y64;
INST "u_qdr2_top/QDR_PHY0/READ_INST/PHY_EN_INST/rd_data_fall_out_35_mux00001" BEL="A6LUT";

These constraints constrain an ISERDES and its LUT and FF loads to their existing locations. The ROUTE constraint then reproduces the existing route in future revisions. The ROUTE constraint is not intended to be human readable.

Note: DIRT constraints are best used to constrain justa few critical nets. If overused they interfere with the router's ability to rip-up and re-route to accommodate other nets. There is also a problem associated with DIRT constraints due to the fact that the placer is not routing aware. The placer may place a component into a location where a routing path is blocked by a DIRT route. This most frequently occurs for Slice FFs using the direct inputs (AX, BX, CX, DX) where the input routing path is blocked by a DIRT route that uses a switchbox bounce off the pin used to access the direct input. The likelihood of this occurring goes up with the number of DIRT routes. This can be avoided with either PROHIBIT constraints or a combination of pack constraints that prevent the problem FF BEL site from being used.

AR# 35556
Date 03/03/2013
Status Active
Type General Article
  • Spartan-3
  • Spartan-3 XA
  • Spartan-3A
  • More
  • Spartan-3A DSP
  • Spartan-3AN
  • Spartan-3E
  • Spartan-6 LX
  • Spartan-6 LXT
  • Less
  • ISE Design Suite - 11.1
  • ISE Design Suite - 11.2
  • ISE Design Suite - 11.3
  • More
  • ISE Design Suite - 11.4
  • ISE Design Suite - 11.5
  • ISE Design Suite - 12.1
  • Less
Page Bookmarked