Answers Database

M1.3/M1.4 PAR/MAP: TBUFs with RLOC Constraint Must be Part of RPM with RLOC_ORIGIN Constraint


Record #1861

Product Family:  Software

Product Line:  Merged Core

Problem Title:
M1.3/M1.4 PAR/MAP: TBUFs with RLOC Constraint Must be Part of RPM with
RLOC_ORIGIN Constraint



Problem Description:
Keywords: PAR, Map, tbuf, rloc, rloc_origin, 12181, 18283

Urgency: standard

General Description:
TBUFs with RLOC constraints must be part of an RPM with an RLOC_ORIGIN Constrain
t.

Platform(s) affected: All
Architecture(s): All
Design Step(s): MAP, PAR
Reference Number: 12181, 18283


Solution 1:

If you attach an RLOC constraint to a TBUF in your design,
the RPM containing the TBUF must have an RLOC_ORIGIN
constraint attached to it. If the RPM does not contain the
RLOC_ORIGIN constraint, you will receive the following
error in Map:

<input> ERROR:baste:199 - RPM "hset" contains three-state
   elements but has no RLOC_ORIGIN.  RPMs with three-state
   elements must be fixed to an exact die location.
</input>

Similarly, if you run PAR on the design, and do not include
the PCF file containing the resulting RLOC_ORIGIN "LOCATE'
constraint, PAR will generate an illegal placement error.



Solution 2:

You may alternatively constrain the wide decoders using
edge constraints T, B, L, or R for top, bottom, left, or
right edges.



End of Record #1861