Static Routing across SLR Boundaries - 2022.2 English

Vivado Design Suite User Guide: Dynamic Function eXchange (UG909)

Document ID
Release Date
2022.2 English

In Versal, static nets cannot cross SLR boundaries within Reconfigurable Partitions, as these crossings require both Laguna and CLB resources to complete. If a Reconfigurable Partition Pblock spans or abuts an SLR boundary, only routes within Reconfigurable Modules within that RP can cross in that area. If non-NoC routes must traverse the SLR boundary, leave space on one or both sides of any RP Pblock to give space for route_design to find a solution.

The following figure shows a two-SLR VP1502 device with two Reconfigurable Partitions. The lower Pblock for RP0 aligns with the SLR boundary (shown in red), and care has been taken to leave space to either side to allow static routes to get from the bottom of the device to RP1 or any other logic in the top SLR. Even though the DFX expanded routing feature will expand to the left and right of RP0 to obtain more routing resources, it will not use the SLLs in the expanded region, leaving those resources for the static design.

Figure 1. Two-SLR VP1502 Device with Two Reconfigurable Partitions