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

10.1 Floorplanner - RPM Macro generated by Floorplanner causes MAP "ERROR:Pack:679 - Unable to obey design constraints"


I have created an RPM macro from Floorplanner using the function "Write RPM to UCF," then generated the NGC for my macro.

When I instantiate the macro in the top level and implement the design, the MAPPER fails with several of the following error messages:

"ERROR:Pack:679 - Unable to obey design constraints

(MACRONAME=module_name/hset, RLOC=X25Y72) which require the

combination of the following symbols into a single SLICE component:

XORCY symbol "module_name/submodule_name/BU2638" (Output Signal = module_name/submodule_name/N26793)

LUT symbol "module_name/submodule_name/BU2841" (Output Signal = module_name/submodule_name/N27665)

MUXCY symbol "module_name/submodule_name/BU2842" (Output Signal = module_name/submodule_name/N27636)

LUT symbol "module_name/submodule_name/BU2851" (Output Signal = module_name/submodule_name/N27690)

MUXCY symbol "module_name/submodule_name/BU2852" (Output Signal = module_name/submodule_name/N27635)

FLOP symbol "module_name/submodule_name/BU2844" (Output Signal = module_name/submodule_name/N16255)

XORCY symbol "module_name/submodule_name/BU2853" (Output Signal = module_name/submodule_name/N27693)

FLOP symbol "module_name/submodule_name/BU2854" (Output Signal = module_name/submodule_name/N16254)

The XORCY symbol module_name/submodule_name/BU2638 is unable to

be placed in either XORF or XORG sites. Please correct the design

constraints accordingly."

How can I solve this problem?


This problem is a result of RLOC constraints generated by the Floorplanner tool forcing the MAPPER to MAP more resources of the same type into a single SLICE than it is possible to put into that SLICE.

The resource causing the conflict should be specified at the end of the message.

In the example error message above, an XORCY symbol is causing the problem.

To work around this problem, disable the RLOC constraint on the symbol causing the conflict:

INST "module_name/submodule_name/BU2638" USE_RLOC = FALSE ;

NOTE: If several messages are generated, a constraint should be used for every conflicting symbol.

AR# 19199
Date 12/15/2012
Status Active
Type General Article