Answers Database
2.1i Virtex PAR - FATAL_ERROR:Route:xvkrtconn.c:116:1.1.2.4 - UNPLACED COMP ENCOUNTERED
Record #6999
Product Family: Software
Product Line: FPGA Implementation
Product Part: par
Product Version: 2.1i
Problem Title:
2.1i Virtex PAR - FATAL_ERROR:Route:xvkrtconn.c:116:1.1.2.4 - UNPLACED COMP ENCOUNTERED
Problem Description:
Urgency: Standard
General Description: When running a V300 design, the following error occurs in par
FATAL_ERROR:Route:xvkrtconn.c:116:1.1.2.4 - UNPLACED COMP ENCOUNTERED Process
will terminate. To resolve this error, please consult the Answers Database
at http://support.xilinx.com
This error will occur when a Virtex carry chain is mapped such that some, but
not all of the slices in the carry chain are included in a macro. The placer will
incorrectly fail to place the non-RLOC'd slices which leads to the router failure.
The following warning message from the placer gives an indication of where
in the design the failure is occuring:
WARNING:Place:1592 - RLOC constraints have been applied to a subset of the
slices in the carry chain. Locations of following components not guaranteed to
be in carry chain formation [list of components affected].
Solution 1:
A fix for the placer bug is scheduled for the 2.1i service pack. Although the
placer will then place the non-RLOC'd slices, it will not be able to allign the
carry chain. This is only possible if the carry chain is entirely RLOC'd or entirely
non-RLOC'd.
The work around for this problem in 2.1i is to make sure that the carry chain is
entirely RLOC'd or entirely non-RLOC'd.
In one case, this problem was caused by logic trimming. An RLOC'd slice had it's
entire contents trimmed except for an XORCY which had no RLOC attribute.
Because all of it's related RLOC'd logic was trimmed, the XORCY was mapped to a
non-RLOC'd slice. The problem was resolved by adding the appropriate RLOC
attribute to the XORCY.
End of Record #6999 - Last Modified: 07/23/99 10:48 |
