UPGRADE YOUR BROWSER

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

4.1i Modular Design - Route results are poor when module boundaries do not coincide with tile boundaries

Description

Keywords: module, modular, route, routing, results, bad, poor, overlap, conflict

Urgency: Standard

General Description:
Several cases have been seen where poor routing results were found to be caused by the use of module boundaries that did not coincide with tile (CLB) boundaries. It was found that PAR was defining the allowable routing area by snapping to the closest tile boundary outside the module boundary.

The results is that adjacent modules can have overlapping router resource utilization, which leads to conflicts during final assembly.

Solution

To avoid this problem, always define module boundaries so that they coincide with tile (CLB) boundaries. To do this, always define the module boundary to start (lower left) on an even component site and end on an odd site.
AR# 13252
Date Created 11/26/2001
Last Updated 08/20/2003
Status Archive
Type General Article