Kintex UltraScale KCU1500 Acceleration Development Board
47
UG1234 (v2017.1) June 20, 2017
www.xilinx.com
Chapter 6:
Install, Bring-Up, and Use
The following information can also be helpful when targeting the
xilinx_kcu1500_4ddr-xpr_4_0.dsa
from the SDx Environments installation, or as
built from the Xilinx Acceleration KCU1500 4DDR Expanded Partial Configuration platform
reference design.
Device Identification
The vendor, build, name, version (VBNV) identifier for the DSA is
xilinx:kcu1500:4ddr-xpr:4.0
, so an
XOCC
script (which invokes the SDAccel System
Compiler) includes the following argument:
--xdevice xilinx:kcu1500:4ddr-xpr:4.0
If attempting to target the DSA that is built from the platform reference design rather than
one from the SDx Environments installation, it is necessary to specify the absolute path to
the directory containing the built
.dsa
file, also known as the
device_repo_path
. Such
.
dsa
files are used with priority over the installation .
dsa
files in the event of duplication.
The
XOCC
script would contain:
--xp prop:solution.device_repo_paths=<path_to_dir_containing_dsa>
User-Specified Connectivity
The Programmable Region has four AXI memory-mapped master interfaces, each of which
connect to one of the four DDR4 IP memory controllers. As described in
Sparse Memory
Connectivity in Chapter 2
, the kernel to global memory accessibility is based on
user-defined connectivity.
The means of specifying that connectivity is through the use of the
map_connect
XOCC
property, in the following format:
--xp
misc:map_connect=add.kernel.<kernel_name>.<kernel_MI>.core.OCL_REGION_0.<ocl_region_MI>
For example, to allow the AXI master interface
MY_MI_AXI
of kernel
my_kernel
access to
global memory from the fourth of four DDR4 channels (
M03_AXI
, as described in
Chapter 3, Hardware Platform
), the XOCC script would contain:
--xp misc:map_connect=add.kernel.my_kernel.MY_MI_AXI.core.OCL_REGION_0.M03_AXI
These commands are additive, such that any master interface of any kernel can be
connected to any Programmable Region master interface, in many-to-many fashion, thus
allowing arbitrary kernel-to-global memory accessibility; however, more connectivity
implies more resource utilization, and can challenge timing closure.
RECOMMENDED:
Users are recommended to consider this trade-off and implement only the
connectivity which is necessary for their application and performance requirements.
Send Feedback
