Creating a Custom Kria App - Part 2

albertabeef

10 Jan 2022

This blog is part of a series of blogs which describe the development steps for an in-depth project tutorial.

http://avnet.me/kv260-vvas-sms-2021-1-blog

This part of the tutorial describes how to create the Vitis Platform for our custom Kria App.

Building the Vitis Platform

In order to build the kv260_ispMipiRx_vcu_DP platform, simply invoke make as shown below:

$ cd $PROJ_DIR/kv260-vitis

$ make platform PFM=kv260_ispMipiRx_vcu_DP

After the build, the Vitis Platform will be located in the following location:

platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1

Understanding the Vitis Platform

We already mentioned that the Vitis platform is a wrapper that defines the available resources for use by Vitis. We can query these resources with the platforminfo command:

$ cd $PROJ_DIR/kv260-vitis

$ platforminfo platforms/xilinx_kv260_ispMipiRx_vcu_DP_202110_1/kv260_ispMipiRx_vcu_DP.xpfm

==========================

Basic Platform Information

==========================

Platform: kv260_ispMipiRx_vcu_DP

File: .../kv260_ispMipiRx_vcu_DP.xpfm

Description:

kv260_ispMipiRx_vcu_DP

=====================================

Hardware Platform (Shell) Information

=====================================

Vendor: xilinx

Board: kv260_ispMipiRx_vcu_DP

Name: kv260_ispMipiRx_vcu_DP

Version: 1.0

Generated Version: 2021.1

Hardware: 1

Software Emulation: 1

Hardware Emulation: 1

Hardware Emulation Platform: 0

FPGA Family: zynquplus

FPGA Device: xck26

Board Vendor: xilinx.com

Board Name: xilinx.com:kv260:1.1

Board Part: XCK26-SFVC784-2LV-C

=================

Clock Information

=================

Default Clock Index: 0

Clock Index: 0

Frequency: 299.997000

Clock Index: 1

Frequency: 599.994000

Clock Index: 2

Frequency: 99.999000

==================

Memory Information

==================

Bus SP Tag: HP1

Bus SP Tag: HP3

Bus SP Tag: HPC1

Bus SP Tag: LPD

=============================

Software Platform Information

=============================

Number of Runtimes: 1

Default System Configuration: kv260_ispMipiRx_vcu_DP

System Configurations:

System Config Name: kv260_ispMipiRx_vcu_DP

System Config Description: kv260_ispMipiRx_vcu_DP

System Config Default Processor Group: smp_linux

System Config Default Boot Image: standard

System Config Is QEMU Supported: 1

System Config Processor Groups:

Processor Group Name: smp_linux

Processor Group CPU Type: cortex-a53

Processor Group OS Name: linux

System Config Boot Images:

Boot Image Name: standard

Boot Image Type:

Boot Image BIF: kv260_ispMipiRx_vcu_DP/boot/linux.bif

Boot Image Data: kv260_ispMipiRx_vcu_DP/smp_linux/image

Boot Image Boot Mode: sd

Boot Image RootFileSystem:

Boot Image Mount Path: /mnt

Boot Image Read Me: kv260_ispMipiRx_vcu_DP/boot/generic.readme

Boot Image QEMU Args: kv260_ispMipiRx_vcu_DP/qemu/pmu_args.txt:kv260_ispMipiRx_vcu_DP/qemu/qemu_args.txt

Boot Image QEMU Boot:

Boot Image QEMU Dev Tree:

Supported Runtimes:

Runtime: OpenCL

We can see that the following clocks and interconnects are available for use by Vitis:

Clocks
- 300MHz
- 600MHz
- 100MHz
High-Performance Interconnect
- LPD
- HP1
- HP3
- HPC1

This information will be important when configuring a Vitis Example or Overlay to be built with this Vitis platform.

Next Steps

The following blogs cover the previous development steps for this in-depth project tutorial.

http://avnet.me/kv260-vvas-sms-2021-1-part1

The following blogs will cover the remaining development steps for this in-depth project tutorial.

Top Comments

Parents

schneisw over 3 years ago

Tip:

If you are getting some errors after running make, you might not have sourced the settings scripts for both Vivado and Vitis. I noticed this after doing neither, and then only Vivado, which incidentally gave me a successful return on “which vitis” resulting in my not sourcing the Vitis script until later.
- Cancel
- Vote Up +1 Vote Down
- Sign in to reply
- More
- Cancel
schneisw over 3 years ago in reply to schneisw
Also source the petalinux setup script and this bug fix per the instructions in part 1:
```
petalinux-upgrade -u 'petalinux.xilinx.com/.../' -p 'aarch64'
```
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel

Comment

schneisw over 3 years ago in reply to schneisw
Also source the petalinux setup script and this bug fix per the instructions in part 1:
```
petalinux-upgrade -u 'petalinux.xilinx.com/.../' -p 'aarch64'
```
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel

Children

juanyi over 3 years ago in reply to schneisw

hi, i'm new to vitis and vivado. I'm trying to follow this tutorial but already having difficulty to get started. I had installed the vitis & vivado in Ubuntu 18.04, had error when i run the first line

make platform PFM=kv260_ispMipiRx_vcu_DP

the error is:

make[2]: /bin/vivado: Command not found
Makefile:29: recipe for target 'project/kv260_ispMipiRx_vcu_DP.xsa' failed
make[2]: *** [project/kv260_ispMipiRx_vcu_DP.xsa] Error 127
make[2]: Leaving directory '/home/yyee/Desktop/Custom/kv260-vitis/platforms/vivado/kv260_ispMipiRx_vcu_DP'
Makefile:42: recipe for target 'vivado/kv260_ispMipiRx_vcu_DP/project/kv260_ispMipiRx_vcu_DP.xsa' failed

Can you show me how to source the setting scripts? Thanks in advance.

javagoza over 3 years ago in reply to juanyi

I think he refers to run the settings script with the source command

https://xilinx.github.io/kria-apps-docs/main/build/html/docs/build_petalinux.html
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
Jan Cumps over 3 years ago in reply to juanyi

Before my Ubuntu knows where the tools are, I first have to execute an environment setting script:

for Vivado:

source /tools/Xilinx/Vivado/2020.2/settings64.sh

for Vitis:

source /tools/Xilinx/Vitis/2020.2/settings64.sh

For Vitis HLS:

source /tools/Xilinx/Vitis_HLS/2020.2/settings64.sh
- Cancel
- Vote Up +1 Vote Down
- Sign in to reply
- More
- Cancel
Jan Cumps over 3 years ago in reply to Jan Cumps

(edit: it doesn't matter which of the 3 scripts you call, because they are identically and all work for vivado, Vitis and vitis_hls)
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel
javagoza over 3 years ago in reply to juanyi
As Jan Cumps indicated you need to first execute the environment settings script

Navigate to the kv260-vitis/platforms directory and then you can generate the extensible xsa

xilinx.github.io/.../build_vivado_design.html
```
ealbertos@xxx:~/kv260-vitis$ source /tools/Xilinx/Vitis/2021.1/settings64.sh
ealbertos@xxx:~/kv260-vitis/platforms$ make platform PLATFORM=kv260_ispMipiRx_vcu_DP
```
- Cancel
- Vote Up 0 Vote Down
- Sign in to reply
- More
- Cancel