How to install platform xilinx_20_02_aarch32

hello everyone:
I am currently using the 2.4.7 version, I vivado installed 2020.2, I follow this tutorial, when executing the command ocpiadmin install platform xilinx19_2_aarch32 ,the error is :

’test@ubuntu:~/han/opencpi-v2.4.7$ ocpiadmin install platform xilinx19_2_aarch32
The RCC platform “xilinx19_2_aarch32” is already defined in this installation, in /home/test/han/opencpi-v2.4.7/project-registry/ocpi.core/exports/rcc/platforms/xilinx19_2_aarch32.
Initializing OpenCPI CDK in /home/test/han/opencpi-v2.4.7
Finding target platform … Found ‘xilinx19_2_aarch32’ (/home/test/han/opencpi-v2.4.7/project-registry/ocpi.core/exports/rcc/platforms/xilinx19_2_aarch32)
Assuming development host platform ubuntu20_04 is already installed.
We will now globally install any packages from package repositories for the xilinx19_2_aarch32 platform.
Since there is no xilinx19_2_aarch32-packages.sh script in directory /home/test/han/opencpi-v2.4.7/project-registry/ocpi.core/exports/rcc/platforms/xilinx19_2_aarch32 for xilinx19_2_aarch32, no packages will be installed.
Xilinx RCC platform is: xilinx19_2_aarch32. Version is: 19_2. Architecture is: aarch32
/home/test/han/opencpi-v2.4.7/cdk/include/xilinx/xilinx-rcc-platform-definition.mk:39: *** Could not find a Xilinx SDK in /tools/Xilinx/SDK or /tools/Xilinx/Vitis for version 2019.2. Stop.

I thought it was because the version of vivado I installed was 2020.2, so I chose to execute the command ocpiadmin install platform xilinx20_2_aarch32

test@ubuntu:~/han/opencpi-v2.4.7$ ocpiadmin install platform xilinx20_2_aarch32
The platform “xilinx20_2_aarch32” is not defined in this installation yet.
ERROR: no project package-id was specified, and
platform “xilinx20_2_aarch32” is not in a built-in project.
Either the platform name is misspelled or you must supply a project package-id.

How can this problem be solved?
Thanks very much.

I watched Aaron Olivarez’s YouTube video from https://www.youtube.com/watch?v=yYprMUij4lo&ab_channel=AaronOlivarez

Because my system is ubuntu 20.04, in [* Compatibility: Valid choices of OS and Xilinx Vivado (#3520) · Issues · OpenCPI / OpenCPI · GitLab *] (Compatibility: Valid choices of OS and Xilinx Vivado (#3520) · Issues · OpenCPI / OpenCPI · GitLab) to find the vivado of ubuntu system at least 2020.1, so I installed 2020.2

You need to have both installed.

  • Vitis 2019.2 includes the cross compiler toolchain necessary to successfully install xilinx19_2_aarch32 RCC platform.

  • If you plan on using xsim for simulation on Ubuntu 20.04 you will need to a newer version of Vivado installed (2020.2) on your system to successfully use that hardware platform.

If you have other requirements that are forcing you to use 2020.2 you would have to create the RCC platform xilinx2020_2_aarch32 that uses the Xilinx 2020.2 tools. You will also need to use boot artifacts, i.e. SD card images, that use that specific version of the Linux kernel for your targeted Embedded platform. Those have to match in order to load the OpenCPI kernel module.

hi,aolivarez:
I have already installed vivado 2020.2, I tried to install xilinx2020_2_aarch32 using the command, but I get an error.

test@ubuntu:~/han/opencpi-v2.4.7$ ocpiadmin install platform xilinx2020_2_aarch32
The platform “xilinx2020_2_aarch32” is not defined in this installation yet.
ERROR: no project package-id was specified, and
platform “xilinx2020_2_aarch32” is not in a built-in project.
Either the platform name is misspelled or you must supply a project package-id.

I checked with the command and found that there is no such platform. How can I install the rcc platform adapted to vivado 2020.2?

test@ubuntu:~/han/opencpi-v2.4.7$ ocpidev show platforms

Platform Package-ID Directory
matchstiq_z1* ocpi.assets.matchstiq_z1 /home/test/han/opencpi-v2.4.7/projects/a…
ml605* ocpi.assets.ml605 /home/test/han/opencpi-v2.4.7/projects/a…
alst4x* ocpi.assets.alst4x /home/test/han/opencpi-v2.4.7/projects/a…
alst4* ocpi.assets.alst4 /home/test/han/opencpi-v2.4.7/projects/a…
xsim ocpi.core.xsim /home/test/han/opencpi-v2.4.7/projects/c…
riviera* ocpi.core.riviera /home/test/han/opencpi-v2.4.7/projects/c…
modelsim* ocpi.core.modelsim /home/test/han/opencpi-v2.4.7/projects/c…
x4sim* ocpi.core.x4sim /home/test/han/opencpi-v2.4.7/projects/c…
isim* ocpi.core.isim /home/test/han/opencpi-v2.4.7/projects/c…
xilinx18_3_aarch64* ocpi.core.xilinx18_3_aarch64 /home/test/han/opencpi-v2.4.7/projects/c…
centos8* ocpi.core.centos8 /home/test/han/opencpi-v2.4.7/projects/c…
xilinx17_1_aarch64* ocpi.core.xilinx17_1_aarch64 /home/test/han/opencpi-v2.4.7/projects/c…
macos12_6* ocpi.core.macos12_6 /home/test/han/opencpi-v2.4.7/projects/c…
macos11_3* ocpi.core.macos11_3 /home/test/han/opencpi-v2.4.7/projects/c…
macos11_1* ocpi.core.macos11_1 /home/test/han/opencpi-v2.4.7/projects/c…
ubuntu18_04* ocpi.core.ubuntu18_04 /home/test/han/opencpi-v2.4.7/projects/c…
macos11_6* ocpi.core.macos11_6 /home/test/han/opencpi-v2.4.7/projects/c…
xilinx19_2_aarch32* ocpi.core.xilinx19_2_aarch32 /home/test/han/opencpi-v2.4.7/projects/c…
xilinx13_3* ocpi.core.xilinx13_3 /home/test/han/opencpi-v2.4.7/projects/c…
macos10_14* ocpi.core.macos10_14 /home/test/han/opencpi-v2.4.7/projects/c…
macos10_15* ocpi.core.macos10_15 /home/test/han/opencpi-v2.4.7/projects/c…
centos7* ocpi.core.centos7 /home/test/han/opencpi-v2.4.7/projects/c…
xilinx19_2_aarch64* ocpi.core.xilinx19_2_aarch64 /home/test/han/opencpi-v2.4.7/projects/c…
rocky8* ocpi.core.rocky8 /home/test/han/opencpi-v2.4.7/projects/c…
macos12_3* ocpi.core.macos12_3 /home/test/han/opencpi-v2.4.7/projects/c…
macos12_2* ocpi.core.macos12_2 /home/test/han/opencpi-v2.4.7/projects/c…
ubuntu20_04 ocpi.core.ubuntu20_04 /home/test/han/opencpi-v2.4.7/projects/c…
xilinx17_2_aarch32* ocpi.core.xilinx17_2_aarch32 /home/test/han/opencpi-v2.4.7/projects/c…
xilinx17_2_aarch64* ocpi.core.xilinx17_2_aarch64 /home/test/han/opencpi-v2.4.7/projects/c…
macos12_4* ocpi.core.macos12_4 /home/test/han/opencpi-v2.4.7/projects/c…
macos12_0* ocpi.core.macos12_0 /home/test/han/opencpi-v2.4.7/projects/c…
xilinx13_4_arm* ocpi.core.xilinx13_4_arm /home/test/han/opencpi-v2.4.7/projects/c…
macos11_5* ocpi.core.macos11_5 /home/test/han/opencpi-v2.4.7/projects/c…
mint21_1* ocpi.core.mint21_1 /home/test/han/opencpi-v2.4.7/projects/c…
macos12_1* ocpi.core.macos12_1 /home/test/han/opencpi-v2.4.7/projects/c…
macos11_2* ocpi.core.macos11_2 /home/test/han/opencpi-v2.4.7/projects/c…
macos13_1* ocpi.core.macos13_1 /home/test/han/opencpi-v2.4.7/projects/c…
xilinx13_4* ocpi.core.xilinx13_4 /home/test/han/opencpi-v2.4.7/projects/c…
macos11_4* ocpi.core.macos11_4 /home/test/han/opencpi-v2.4.7/projects/c…
ubuntu22_04* ocpi.core.ubuntu22_04 /home/test/han/opencpi-v2.4.7/projects/c…
macos10_13* ocpi.core.macos10_13 /home/test/han/opencpi-v2.4.7/projects/c…
xilinx17_1_aarch32* ocpi.core.xilinx17_1_aarch32 /home/test/han/opencpi-v2.4.7/projects/c…
macos12_5* ocpi.core.macos12_5 /home/test/han/opencpi-v2.4.7/projects/c…
macos13_0* ocpi.core.macos13_0 /home/test/han/opencpi-v2.4.7/projects/c…
zed_ise* ocpi.platform.zed_ise /home/test/han/opencpi-v2.4.7/projects/p…
zed_ether* ocpi.platform.zed_ether /home/test/han/opencpi-v2.4.7/projects/p…
zed ocpi.platform.zed /home/test/han/opencpi-v2.4.7/projects/p…
zcu104* ocpi.platform.zcu104 /home/test/han/opencpi-v2.4.7/projects/p…
zcu106* ocpi.platform.zcu106 /home/test/han/opencpi-v2.4.7/projects/p…
picoevb* ocpi.platform.picoevb /home/test/han/opencpi-v2.4.7/projects/p…

  • An asterisk indicates that the platform has not been built yet.
    Assemblies and tests cannot be built until the platform is built.
    test@ubuntu:~/han/opencpi-v2.4.7$

Support for xilinx2020_2_aarch32 does not exist in OpenCPI.

These platforms are located in projects/core/rcc/platforms/

You would have create it if you really needed that specific version.

What embedded platform are you trying to interface with?

hi,aolivarez:
My FPGA development board is from MILINK company, it also uses xilinx chip, its chip is the same as ZCU102, but since I am using ubuntu, you told me last time that ubuntu does not support the version of vivado2019, so I installed vivado 2020.2

The limitation of 2019.2 was specific to “xsim” hdl platform.

Xilinx 2019.2 does work for xilinx19_2_aarch64 platform. and zcu102 on Ubuntu.

You will need to build the sd card for your platform with that same version. Does the platform come with a sd card boot artifacts? If so what version did the vendor use?

Alternatively you can use tools such as Petalinux to build the operating system compatible with the version that OpenCPI supports.

Thank you very much, aolivarez, thank you very much, I reinstalled vivado 2019.2 try it.

You’re welcome.

If you do end up needing to create the sd card boot artifacts. This guide contains an example of the procedures to create them using Petalinux.