Hardware Acceleration Tutorials

See Vitis™ Development Environment on xilinx.com

Using HBM¶

Version: Vitis 2022.1

Introduction¶

This tutorial covers essential steps on migrating an existing application using DDR memory to HBM memory. The tutorial begins by explaining the structural differences between DDR and HBM, as well as achievable theoretical bandwidth. The second section uses a simple example with necessary steps to migrate an application from DDR to HBM.

Before You Begin¶

TIP: This tutorial takes approximately two hours to complete.

The labs in this tutorial use:

BASH Linux shell commands.
2022.1 Vitis core development kit release and the xilinx_u200_xdma_201830_2 and xilinx_u50_gen3x16_xdma_201920_3 platforms. If necessary, it can be easily ported to other versions and platforms. Its also expected that you have a Xilinx® Alveo™ Data Center accelerator card that supports DDR and HBM to run this tutorial.

IMPORTANT:

Before running any of the examples, make sure you have installed the Vitis core development kit as described in Installation in the Application Acceleration Development flow of the Vitis Unified Software Platform Documentation (UG1416).

If you run applications on Xilinx® Alveo™ Data Center accelerator cards, ensure the card and software drivers have been correctly installed by following the instructions on the Alveo Portfolio page.

Accessing the Tutorial Reference files¶

Enter the command in a terminal: git clone http://github.com/Xilinx/Vitis-Tutorials.
Navigate to Hardware_Acceleration/Feature_Tutorials/04-using-hbm directory, and then access the reference-files directory.

Generating all the xclbins¶

The tutorial provides the results as you go through. But if you intend to generate the xclbins, this can take several hours to generate the multiple xclbin. Its recommended to build all of these upfront so that you can focus on tutorial without waiting on these builds. The following steps will build the necessary xclbins for next two modules.

Update the PLATFORM variable in the makefile/Makefile as shown below with the platform intended to be used.

ifeq ($(memtype), DDR)
PLATFORM :=xilinx_u200_gen3x16_xdma_2_202110_1
else
PLATFORM :=xilinx_u50_gen3x16_xdma_201920_3
endif

Run the following command to build three xclbins for module 2 (Migration from DDR to HBM). The expected time to build xclbins is about 7-8 hours or you can run these in parallel.

cd 04-using-hbm/makefile; make ddr_addSeq_build hbm_addSeq_2Banks_build hbm_addSeq_overlap_build
Run the following command to build ten xclbins for module 3 (HBM Bandwidth Results). The expected time to build xclbins is about 5-6 hours since the following command will run parallel jobs by default

cd 04-using-hbm/makefile; make build_without_rama build_with_rama

If your machine doesn’t have enough resources to run multiple build jobs in parallel, you can always run these serially using the following commands but it may take about several hours.

cd 04-using-hbm/makefile; make noramajob-64 noramajob-128 noramajob-256 noramajob-512 noramajob-1024 ramajob-64 ramajob-128 ramajob-256 ramajob-512 ramajob-1024;

Please refer to the ./makefile/Makefile for more information.

Tutorial Overview¶

HBM Overview: Provides a brief overview on the structural differences between DDR and HBM and theoretical maximum bandwidth by HBM.
Migration from DDR to HBM: Walks through the steps of migrating an existing DDR based application to HBM
HBM Bandwidth Explorations: Shows the achievable bandwidth using a single kernel port based on access pattern and transaction size.

¶

Start the next step: HBM Overview

Return to Start of Tutorial

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.