Download design flow tutorials - Lattice Semiconductor

Transcript
FPGA Process Flow
UGROUP Attribute Usage Guidelines
Use the UGROUP attribute to group blocks in different hierarchies or no hierarchy. UGROUP differs from
PGROUP in that pre-appending the hierarchy and the block instance does not change its identifier.
Observe the following conditions for proper UGROUP attribute usage:
•
•
•
•
All elements within the UGROUP’d block belong to that particular UGROUP.
Nested UGROUP blocks are considered as unique individual UGROUPs.
All blocks belong to the UGROUP attached to their nearest ancestor in the hierarchy.
Unlike PGROUP, the mapper will not append the hierarchical path plus the block instance name.
For example:
then,
REG1 and REG2 belong to UGROUP_1.
REG3 and REG4 belong to UGROUP_2.
Also, assuming REG1, REG2 are mapped to PFU_0 and REG3, REG4 are mapped to PFU_1, the resulting
preferences generated in the preference file are as follows:
PGROUP "UGROUP_1"
COMP PFU_0;
PGROUP "UGROUP_2"
COMP PFU_1;
If block1 has a UGROUP that is also located, PLOC = R1C1, then the additional preference,
LOCATE PGROUP "UGROUP_1" SITE "R1C1"
appears in the preference file.
If block1 has a PREGION=ONE, PRLOC=R1C1, PRBBOX=2,2 then the preferences generated are as
follows:
REGION "ONE" "R1C1" 2 2;
PGROUP "UGROUP_1"
COMP PFU_0;
PGROUP "UGROUP_2"
COMP PFU_1;
LOCATE PGROUP "UGROUP_1" REGION "ONE"
LOCATE PGROUP "UGROUP_2" REGION "ONE"
Note that UGROUPs also resolved into the PGROUP physical preference.
44
ispLEVER 4.0