Answers Database
** DUPLICATE of 2337 ** M1.2/M1.3/M1.4 MAP: Map complains about incompatible site types when expanding wildcard constraints--ERROR:x4kma - IBUF symbol `$ 1I89' is unable to combine with IO RESET
Record #2914
Product Family: Software
Product Line: Merged Core
Problem Title:
** DUPLICATE of 2337 ** M1.2/M1.3/M1.4 MAP: Map complains about
incompatible site types when expanding wildcard constraints--ERROR:x4kma - IBUF symbol
`$
1I89' is unable to combine with IO RESET
Problem Description:
Keywords: MAP, x4kma, place instance, wildcard, CLB, IOB,
incompatible site types
Urgency: Standard
General Description:
MAP returns the following error messages about constraints of
the form:
"place instance *: [CLB_R2C1 CLB_R10C3];"
ERROR:x4kma - IBUF symbol `$1I89' (output signal=RESET_NET)
is unable to combine with IO RESET. The two symbols have
incompatible site types.
This error may be seen when Map expands a constraint (usually
specified in a .UCF file) that contains an asterisk wildcard
("*") in the block name or net name field. The locations
specified by the constraint refer to CLB logic only,
but Map expands the asterisk to also include IOBs.
Solution 1:
Modify the UCF file constraint so that the 'LOC' constraints
only include CLB components when expanded. For example, if
all the CLB components can be grouped together by specifying
a string like "decode_blk*", then you would modify the .UCF
to look like:
place instance decode_blk*: [CLB_R2C1 CLB_R10C3];"
Alternatively, you could specify 'CONFIG PROHIBIT'
constraints on CLBs which should NOT be used.
Refer to Chapter 13 of the online Xilinx Libraries Guide
for information on syntax and usage on the 'LOC' and 'CONFIG
PROHIBIT' constraints.
Reference #: 17298
End of Record #2914
| For the latest news, design tips, and patch information on the Xilinx design environment, check out the Xilinx Expert Journals! |
