The figure below highlights the issue of kernel placement when migrating to a new target platform. In the example below:
- Existing kernel, kernel_B, is too large to fit into SLR2 of the new target platform because most of the SLR is consumed by the static region.
- The existing kernel, kernel_D, must be relocated to a new SLR because the new target platform does not have four SLRs like the existing platform.
Figure 1. Migrating Platforms – Kernel Placement
When migrating to a new platform, you need to take the following actions:
- Understand the resources available in each SLR of the new target platform, as documented in the Vitis Software Platform Release Notes (UG1742).
- Understand the resources required by each kernel in the design.
- Use the
v++ --configoption to specify which SLR each kernel is placed in, and which DDR bank each kernel connects to. For more details, refer to Assigning Compute Units to SLRs on Alveo Accelerator Cards and Mapping Kernel Ports to Memory.
These items are addressed in the remainder of this section.