Answers Database
1.5i/2.1i 4K Map - ERROR:OldMap:532 - Unable to obey design constraints which require the following symbols into a single CLB. . .
Record #7083
Product Family: Software
Product Line: FPGA Implementation
Product Part: map
Product Version: 2.1i
Problem Title:
1.5i/2.1i 4K Map - ERROR:OldMap:532 - Unable to obey design constraints which require the
following symbols into a single CLB. . .
Problem Description:
URGENCY: standard
GENERAL DESCRIPTION:
Error in MAP:
ERROR:OldMap:532 - Unable to obey design constraints which require the
combination of the following symbols into a single CLB:
HMAP symbol "Viterbi_0_ACS_ENGINE_INST1_MEMORY_MEM_BLK/B546" (output
signal=Viterbi_0_ACS_ENGINE_INST1_MEMORY_MEM_BLK/N144)
FMAP symbol "FMAP_3285" (output signal=N943)
FMAP symbol "Viterbi_0_ACS_ENGINE_INST1_MEMORY_MEM_BLK/B541" (output
signal=Viterbi_0_ACS_ENGINE_INST1_MEMORY_MEM_BLK/N9255)
FDCE symbol "Viterbi_0_ACS_ENGINE_INST1_MEMORY_MEM_BLK/B579" (output
signal=Viterbi_0_ACS_ENGINE_INST1_MEMORY_MEM_BLK/N139)
FMAP symbol "Viterbi_0_ACS_ENGINE_INST1_MEMORY_MEM_BLK/B578" (output
signal=Viterbi_0_ACS_ENGINE_INST1_MEMORY_MEM_BLK/N9748)
No function generator is available. These symbols share the same RLOC
parameter. Consider using the "-ir" command line switch.
Solution 1:
Map packing errors can occur for a variety of reasons, from user generated packing
directives that are impossible to meet, to bugs in the mapper where legitimate packing
directives can not be followed. The recommendation in the error message to use the
"-ir" switch is not always the optimal solution.
One common source of packing errors occurs when map pulls an undirected
FMAP into a CLB because it drives the HMAP in the CLB, without regard to
whether the CLB has an FMAP available. In this case, the packing error will
list three FMAPs among the components involved.
In the 1.5i software, an environment variable was made available that disables
this behavior:
setenv XIL_MAP_NO_FMAP_PACK 1 (Work Stations)
set XIL_MAP_NO_FMAP_PACK=1 (PCs)
In the 2.1i release, the intent was to make the default behavior turn the FMAP
pack off and introduce a new variable to turn it back on if needed. This change
was not implemented properly, so in 2.1i, the new variable needs to be set to
disable the FMAP pack:
setenv XIL_MAP_FMAP_PACK 1 (Work Stations)
set XIL_MAP_FMAP_PACK=1 (PCs)
Solution 2:
End of Record #7083 - Last Modified: 10/20/99 17:48 |
