更換u50的platform

[ray3210ray3210]

我們在Final project實作別人github的設計時，因為必須使用vitis 2021.1的版本。
遇到了以下的問題

02.Yhjyyx@HLS02:~/workspace_final$ vitis -version

****** Xilinx Vitis Development Environment
****** Vitis v2021.1 (64-bit)
**** SW Build 3245906 on 2021-06-09-18:10:55
** Copyright 1986-2021 Xilinx, Inc. All Rights Reserved.

02.Yhjyyx@HLS02:~/workspace_final$ platforminfo -p xilinx_u50_gen3x16_xdma_5_202210_1
Error parsing platform file: /opt/xilinx/platforms/xilinx_u50_gen3x16_xdma_5_202210_1/xilinx_u50_gen3x16_xdma_5_202210_1.xpfm
Line number:16. Mandatory element missing
Exception: failed to parse the XPFM file

上網查詢之後發現vitis2021.1無法支援這個u50的platform,here
想請問我們有辦法更換u50的platform嗎?

必須使用vitis2021.1的版本的原因是
他們的設計在2021.2之後的版本
做pipeline的時候會出現這個問題,here
我們已經在2022.1compile過，也會出現同樣的問題

Thank you.
許睿哲

[boledulab]

You can run two source commands to change to vitis 2021.1 on HLS02 machine. (default is vitis 2022.1)
source /opt/Xilinx/Vitis/2021.1/settings64.sh
source /opt/xilinx/xrt/setup.sh

[ray3210ray3210]

I followed the steps to change to the Vitis 2021.1 version, but I'm still encountering the same problem,

I found someone who asked a similar question.

Last year, the student used the "xilinx_u50_gen3x16_xdma_201920_3" Development Target Platform for their implementation of this github project.
However, the Xilinx official website only provides downloads for versions 2022.1 and 2022.2 .here(step3)

Is there a way to obtain an older version of the Development Target Platform?

Thank you.
許睿哲

[boledulab]

Hi,
Your default vitis have set to 2021.1 and you can find 201920_3.xpfm here.
/opt/xilinx/platforms/xilinx_u50_gen3x16_xdma_201920_3/xilinx_u50_gen3x16_xdma_201920_3.xpfm

[ray3210ray3210]

After solving the above problem, we encountered the following problem(Y2K22).
and I don't have permission to update and copy files to /opt/Xilinx/Vitis_HLS/2021.1/common/scripts/ and /opt/Xilinx/Vivado/2021.1/common/scripts/
Here is the error

We found this solution.
The solution is to download the "y2k22_patch-1.2.zip" file.
However, we found that the same folder already exists at /opt/Xilinx/y2k22_patch.
I followed the instructions in /opt/Xilinx/y2k22_patch/README. Here is the output.

but a successful output will look like this

I checked the two paths: /opt/Xilinx/Vitis_HLS/2021.1/common/scripts/ and /opt/Xilinx/Vivado/2021.1/common/scripts/

and found that the file "automg_patch_20220104.tcl" was not copied to those folders.

I think it is because I don't have permission to perform the copy operation.

Thank you.
許睿哲

[boledulab]

It should be updated, pls test your issue again.

hls02@HLS02:/opt/Xilinx$ export LD_LIBRARY_PATH=$PWD/Vivado/2021.1/tps/lnx64/python-3.8.3/lib/
hls02@HLS02:/opt/Xilinx$ Vivado/2021.1/tps/lnx64/python-3.8.3/bin/python3 y2k22_patch/patch.py
[2023-06-09] INFO: This script (version: 1.2) patches Xilinx Tools for HLS Y2k22 bug for the following release:
2014., 2015., 2016., 2017., 2018., 2019., 2020.* and 2021.*
[2023-06-09] UPDATE: /opt/Xilinx/Vivado/2021.1/common/scripts
[2023-06-09] COPY: /opt/Xilinx/y2k22_patch/automg_patch_20220104.tcl to /opt/Xilinx/Vivado/2021.1/common/scripts/automg_patch_20220104.tcl
[2023-06-09] UPDATE: /opt/Xilinx/Vitis_HLS/2021.1/common/scripts
[2023-06-09] COPY: /opt/Xilinx/y2k22_patch/automg_patch_20220104.tcl to /opt/Xilinx/Vitis_HLS/2021.1/common/scripts/automg_patch_20220104.tcl

[ray3210ray3210]

Hi, for our final project, we are using an open-source library called "hlslib". During hardware emulation, we made some parameter adjustments, but it appears that the expected results are not being displayed. We found information on the library's GitHub page suggesting that it might be necessary to install the libc6-dev-i386 package on Ubuntu for hardware emulation. Can you help us with downloading this package?

Thanks

[boledulab]

The hls02 already installed libc6-dev-i386 (newest version 2.31-0ubuntu9.9).