You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/src/tutorials/arch/heterogeneous_tiles.rst
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -7,27 +7,27 @@ This tutorial aims at providing information to the user on how to model sub tile
7
7
8
8
An *heterogeneous tile* is a tile that includes two or more site types that may differ in the following aspects:
9
9
10
+
- *Block types* (pb_type)
10
11
- *Fc* definition
11
12
- *Pin locations* definition
12
13
- *IO ports* definition
13
14
14
-
As a result, an *heterogeneous tile* has the possibility of having multiple block types at the same *x* and *y* location in the grid.
15
-
This comes with the introduction of a third spatial coordinate that identifies the placement of the block type within the x and y grid coordinate.
15
+
As a result, an *heterogeneous tile* has the possibility of having multiple block types at the same (*x*, *y*) location in the grid.
16
+
This comes with the introduction of a third spatial coordinate (sub-block) that identifies the placement of the block type within the x and y grid coordinate.
16
17
17
18
Moreover, the placer can choose and assign different locations for each block type within the same coordinates as well.
18
19
19
20
.. figure:: sub_tiles_grid.png
20
21
21
-
Device grid, with x, y and subblock coordinates. Each block can be moved by the placer in all the three spatial dimensions.
22
+
Device grid, with (x, y, sub-block) coordinates. Each block can be moved by the placer in all the three spatial dimensions.
22
23
23
24
To correctly model an architecture, each :ref:`arch_tiles` requires at least one sub tile definition. This represents a default
24
-
homogeneous architecture, composed of one or many capacity instances of the sub tile within the physical tile.
25
+
homogeneous architecture, composed of one or many instances of the sub tile within the physical tile (the number of such sub-tiles is referred to as the *capacity*).
25
26
26
27
To enhance the expressivity of VPR architecture, additional sub tiles can be inserted alongside with the default sub tile.
27
28
This enables the definition of the *heterogeneous tiles*.
28
29
29
-
With this new capability, the device grid of a given architecture does include a new ``depth`` coordinate that identifies
30
-
the type of sub tile used and its actual location, in case the capacity is greater than 1.
30
+
With this new capability, the device grid of a given architecture does include a new sub-block coordinate that identifies the type of sub tile used and its actual location, in case the capacity is greater than 1.
31
31
32
32
Heterogeneous tiles examples
33
33
----------------------------
@@ -84,8 +84,8 @@ Heterogeneous tiles come in hand to model this kind of tiles and an example is t
@@ -132,7 +132,7 @@ The above ``BUFG_TILE`` contains three types of sub-tiles (``BUFG_SUB_TILE_0``,
132
132
While each sub-tile type contains the same pb_type (equivalent_sites of ``BUFGCTRL``), they differ in two ways:
133
133
134
134
1. Each sub-tile has different pin locations. For example ``BUFG_SUB_TILE_0`` has the ``I1`` pins on the top side of the tile, while ``BUFG_SUB_TILE_1`` and ``BUFG_SUB_TILE_2`` have them on the right and left sides respectively.
135
-
2. Each sub-tile has a different 'capacity' (i.e. a different number of sites). ``BUFG_SUB_TILE_1`` and ``BUFG_SUB_TILE_2`` have capacity 1, while ``BUFG_SUB_TILE_1`` has capacity 14. As a result the ``BUFG_TILE`` can implement a total of 16 ``BUFG_SUB_TILE`` blocks.
135
+
2. Each sub-tile has a different 'capacity' (i.e. a different number of sites). ``BUFG_SUB_TILE_1`` and ``BUFG_SUB_TILE_2`` have capacity 1, while ``BUFG_SUB_TILE_1`` has capacity 14. As a result the ``BUFG_TILE`` can implement a total of 16 ``BUFGCTRL`` blocks.
0 commit comments