General Description: My design contains an RPM macro with F5/F6 mux configurations; it fails in placement because MAP puts some of the logic in the incorrect slice location even though the logic was RLOC'd correctly. The following placement error is reported:
"ERROR:Place:1750 - Structured logic associated with an F6 configuration could not be placed. This logic requires a very specific relative placement. The relative placement required by the logic was impossible to resolve. The structured logic could not be placed in the relative placement form required. This is due to the fact that the component $1I46/$1I8/$1I48/$1I148/O is already contained in an rpm that will not allow the logic to be placed in the legal form."
This problem is due to a bug related to "macro normalization". This normalization occurs when a macro is constructed with something other than the X0Y0 slice used as the lower leftmost logic. (The problem is not limited to the F5/F6 mux configurations that were involved in this example.)
This will be fixed in 4.2i Service Pack 1, which is currently scheduled for release in March, 2002.
Meanwhile, this problem can be avoided if all RPM macros are constructed so that the X0Y0 slice is used.