Skip to content

Latest commit

 

History

History
125 lines (83 loc) · 4.67 KB

Debug0_po.md

File metadata and controls

125 lines (83 loc) · 4.67 KB

AI Engine Debug Walkthrough Tutorial - From Simulation to Hardware

Migrate Command-Line Based Projects to Vitis IDE

This section documents the necessary steps to migrate command-line based projects to Vitis™ IDE.

Step 1 Create project

Step 2 Import project source code

Step 3 Configure project

Step 4 Configure system project in packaging options

Step 1: Create project

  1. Launch Vitis IDE by issuing the command, vitis.

  2. Create a project as illustrated by the following images. alt text alt text alt text alt text

  3. After the previously listed steps are completed, the created system project is expected to have AI Engine and hardware link sub-projects, as illustrated in the following image.

alt text

  1. Then you need to create PS and PL sub-projects under the system project. alt text alt text

  2. Fill in sysroot path, root FS, and kernel image information for PS application.

alt text

  1. Select Empty Application under Acceleration templates with PL and AIE accelerators" for PS sub-project.

After the previously listed steps are completed, you should have AI Engine, PS, PL and hardware link sub-projects under system project.

alt text

Step 2: Import project source code

  1. Import the source code for AI Engine sub-projects. alt text alt text

  2. Continue to import data for the AI Engine sub-project, source code for PS, PL, and hardware link sub-projects.

Note: If the PS sub-project requires the defer-aie-run option in packaging, you must import aie_control_xrt.cpp in the PS sub-project.

Step 3: Configure project

Step 3.1: Configure AI Engine sub-project

  1. Configure top level graph. ![alt text](images/po_graph.png">

  2. Configure include paths. alt text alt text

Step 3.2: Configure hardware link

  1. Configure the hardware link with the v++ option ![alt text](images/po_hw_config.png"> alt text

  2. Import the system.cfg file to the correct project/location. ![alt text](images/po_hw_config2.png">

Step 3.3: Configure hardware kernels

  1. Add hardware functions to project. ![alt text](images/po_hw_config3.png">

  2. Configure number of instances for each PL kernel. ![alt text](images/po_hw_config4.png">

  3. Update (comment out) nk=kernel:1:kernel_n line from the system.cfg file. This is because the Vitis IDE relies on the previous step to determine the number of instances for each PL kernel. Redundant configurations of the number of kernels in system.cfg results in compilation errors. ![alt text](images/po_hw_config5.png">

Step 3.4: Configure PS sub-project

  1. Right-click the PS sub-project. alt text

  2. Configure the PS application to include paths. alt text

  3. Configure the PS application link libraries. alt text

Step 4: Configure system project in packaging options

![alt text](images/po_system_config.png">

Note: This configuration is optional and depends on the design.

  1. If graph.init() is required, invoke graph.run() and graph.end() from PS, then use the --package.defer_aie_run option.

  2. If data files need to be packaged to the sd_card, then use the --package.sd_dir ${PROJECT_PATH}/data option.

Support

GitHub issues will be used for tracking requests and bugs. For questions go to support.xilinx.com.

License

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.

XD005 | © Copyright 2021-2022 Xilinx, Inc.