Answers Database

M1.3 MAP, PAR: ERROR - Resolved that macro M12X12/BR5/hset is unable to be placed due to other locked logic or prohibited sites.


Record #2290

Product Family:  Software

Product Line:  Merged Core

Problem Title:
M1.3 MAP, PAR: ERROR - Resolved that macro M12X12/BR5/hset is unable to
be placed due to other locked logic or prohibited sites.



Problem Description:
Keywords: RLOC, LOC, FFS, FMAP, HMAP, MAP, zipper

Urgency: Standard

Reference Number: 14980 (sw/kl)

General Description:

In the error message below PAR flags one RPM called
"M12X12/BR5/hset" consisting mainly of FMAPs and
HMAPs, and another called "M12X12/PT2R6" containing RLOC'd
FFS.  Elements of both RPMs have been constrained in the
design to the same CLB locations.  Since RPMs are supposed to
be permeable, the overlapping of constraints should be valid.

However, the problem is that Map converts each RPM (defined
by a shared H_SET property) early on into physical
macros, instead of trying to merge them first.	Physical
macros are by definition impermeable, so this prevents two
RPMs constrained to the same location from being merged
together.  The error issued by PAR is thus actually being
issued against two physical ("hard") macro elements being
constrained to the same CLB location.

<OUTPUT>
ERROR - Resolved that macro M12X12/BR5/hset is unable to be
placed due to other locked logic or prohibited sites.
   Refsite CLB_R30C3 unavailable.  Site CLB_R31C3 has CLB
M12X12/PT2R6 located.
   Refsite CLB_R30C3 unavailable.  Site CLB_R30C3 has CLB
M12X12/PT2R7 located.
ERROR - Resolved that macro M12X12/BR3/hset is unable to be
placed due to other locked logic or prohibited sites.
   Refsite CLB_R28C2 unavailable.  Site CLB_R29C2 has CLB
M12X12/PT1R6 located.
   Refsite CLB_R28C2 unavailable.  Site CLB_R28C2 has CLB
M12X12/PT1R7 located.
</OUTPUT>


Solution 1:


Currently, the only workaround is to redefine the RPMs
in terms of groups (H_SETs) of _complete CLBs_, instead of
overlapping H_SETs of BEL (Basic Element) level resource
units like flip-flops and LUTs.  (H_SET groupings are usually
implied by the hierarchical structure of the design.)

For example, given an XTF file excerpt for part of an RPM
corresponding to a single CLB:

<OUTPUT>
SYM, M12X12/PT2R/S3/$1I5, DFF, LOC=CLB_R30C3.FFY, HIERG=85,
RLOC=R9C0.FFY, H_SET=M12X12/PT2R/hset, INIT=R, LIBVER=2.0.0
PIN, C, I, CLK
PIN, D, I, M12X12/PT2R/S3/D_Y
PIN, Q, O, M12X12/PT2R7
END
SYM, M12X12/PT2R/S3/3A_2A, FMAP, LOC=CLB_R30C3.G, HIERG=85,
RLOC=R9C0.G, H_SET=M12X12/PT2R/hset, MAP=PUC, LIBVER=2.0.0, TRIM
PIN, I1, I, M12X12/BR4
PIN, I2, I, M12X12/AR2
PIN, I3, I, M12X12/AR3
PIN, I4, I, M12X12/PT2R/S3/CO_G
PIN, O, I, M12X12/PT2R/S3/3A_2A
END
SYM, M12X12/PT2R/S3/A_0A, FMAP, LOC=CLB_R30C3.F, HIERG=85,
RLOC=R9C0.F, H_SET=M12X12/PT2R/hset, MAP=PUC, LIBVER=2.0.0, TRIM
PIN, I1, I, M12X12/BR4
PIN, I2, I, M12X12/AR3
PIN, O, I, M12X12/PT2R/S3/A_0A
END
SYM, M12X12/PT2R/S3/D_Y, HMAP, LOC=CLB_R30C3.H, HIERG=85,
RLOC=R9C0.H, H_SET=M12X12/PT2R/hset, MAP=PUC, LIBVER=2.0.0
PIN, I1, I, M12X12/BR5
PIN, I2, I, M12X12/PT2R/S3/A_0A
PIN, I3, I, M12X12/PT2R/S3/3A_2A
PIN, O, I, M12X12/PT2R/S3/D_Y
END
SYM, M12X12/BR5/Q1, DFF, LOC=CLB_R30C3.FFX, HIERG=16,
RLOC=R0C0.FFX, H_SET=M12X12/BR5/hset, INIT=R, LIBVER=2.0.0
	       ^^^^^^^^^^^^^^^^^^^^^
PIN, C, I, CLK
PIN, D, I, B5
PIN, Q, O, M12X12/BR5
END
</OUTPUT>

Notice that the DFF, M12X12/BR5/Q1 (the last SYM record in
this block of the .XTF fragment), is constrained to CLB_R30C3
but does not belong to the same H_SET as rest of the BELs (SYM
records) at the same CLB location.  It belongs to the H_SET,
"M12X12/BR5/hset", instead of "M12X12/PT2R/hset".

To work around this problem, all BELs in the RPM defined by
the H_SET called M12X12/BR5/hset should be reassigned to H_SET
"M12X12/PT2R/hset":

<OUTPUT>
SYM, M12X12/BR5/Q1, DFF, LOC=CLB_R30C3.FFX, HIERG=16,
RLOC=R9C0.FFX, H_SET=M12X12/PT2R/hset, INIT=R, LIBVER=2.0.0
	       ^^^^^^^^^^^^^^^^^^^^^^^
PIN, C, I, CLK
PIN, D, I, B5
PIN, Q, O, M12X12/BR5
END
</OUTPUT>



End of Record #2290