|
The Clique section lists the hierarchy path names of the members of clique and the type of clique. A clique specifies which logic functions must remain closely together, regardless of their exact location on the device. Cliques allow you to partition a project so that only a minimum number of signals travel between LABs, rows, and devices, and to ensure that no unnecessary delays exist on critical timing paths. The Clique section is located in the Entity Settings File (.esf).
You can assign logic functions to different types of cliques that ensure that they are implemented in the same LAB, row, or chip. You can also assign a "best" clique that specifies that the clique should be implemented in the smallest possible category of LAB, row, or chip.
The Clique section keyword is CLIQUE
(<clique name>).
The clique requires a unique name, which you can type as (
<clique>)
, in the Clique section.
The Clique section contains statements that follow these Usage Code definitions.
The following table shows the Clique section keywords allowed in the Clique section (which are underscore separated), descriptions, legal settings, and usage codes:
Keyword | Settings | Code |
---|---|---|
APEX20K_CLIQUE_TYPE |
LAB (Default = LAB) | A |
FLEX®6K_CLIQUE_TYPE |
LAB | Best | Row | Half Row (Default = LAB) | A |
FLEX10K_CLIQUE_TYPE |
LAB (Default = LAB) | A |
MAX7K_CLIQUE_TYPE |
LAB (Default = LAB) | A |
MEMBER_OF |
<hierarchy path name> | B, C |
MERCURY_CLIQUE_TYPE |
LAB (Default = LAB ) | A |
SUBCLIQUE_OF |
<clique name> | B, C |
- PLDWorld - |
|
Created by chm2web html help conversion utility. |