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
Is your feature request related to a problem? Please describe.
Currently, when a tile consists of a number of subtiles, each subtile has an independent set of ports. For example, an I/O tile consists of 4 subtiles, each of which contains 8 clocks.
This leads to serious physical design problems when we performing P&R on a tile. All these pins have to be placed on the boundary of a tile. However, when the number of pins is large, the tile perimeter may not be sufficient. In such case, we have to increase the physical dimension of a tile in order to accommodate all the pins. This comes with a serious degradation on the area and low utilization rate (I/O tiles do not carry a lot of logics typically).
Describe the solution you'd like
Actually, some of the ports can be merged without impacting functionality. Take the example above, all these clocks and reset can be merged across all the subtiles in an I/O tile.
The net merging can be applied in side an I/O tile. The resulting netlist may look like:
Is your feature request related to a problem? Please describe.
Currently, when a tile consists of a number of subtiles, each subtile has an independent set of ports. For example, an I/O tile consists of 4 subtiles, each of which contains 8 clocks.
Here is a short example on the architecture:
On the I/O tile, we see the following
This leads to serious physical design problems when we performing P&R on a tile. All these pins have to be placed on the boundary of a tile. However, when the number of pins is large, the tile perimeter may not be sufficient. In such case, we have to increase the physical dimension of a tile in order to accommodate all the pins. This comes with a serious degradation on the area and low utilization rate (I/O tiles do not carry a lot of logics typically).
Describe the solution you'd like
Actually, some of the ports can be merged without impacting functionality. Take the example above, all these clocks and reset can be merged across all the subtiles in an I/O tile.
The net merging can be applied in side an I/O tile. The resulting netlist may look like:
To offer flexiblity to users, the following syntax can be added to tile annotation:
Note that the merging can be ONLY applied to the ports whose Fc is 0!!!
The text was updated successfully, but these errors were encountered: