Hello, Is there any support for this board for Vivado / Vitis 2019.2 version?
I found some ref design / board files in the repo but they are from 2017 and 2018 versions.
Thanks much
Ratin
Hello, Is there any support for this board for Vivado / Vitis 2019.2 version?
I found some ref design / board files in the repo but they are from 2017 and 2018 versions.
Thanks much
Ratin
Hi @Ratin, From the Avnet/hdl github repo you can walk through different branches (for different Vivado versions) and look for reference designs and board files.
I can see the repo with reference designs (base, dualcam) with the correct board name from Vivado 2021.2 toolchain below
hdl/boards/zub1cg_sbc at 2021.2 · Avnet/hdl (github.com)
The board definition files can be found in the master branch of the following.
Hi There Manihatn, Thanks for replying my question. I actually checked out 2019.2 branch of the github repo and did not find any board file for the ZU board.
https://github.com/Avnet/hdl/tree/2019.2
Unfortunately 2019.2 is the version I have to develop with since everything else is based around this version (but for other platform) so the those designs can be imported for the CG. I tried to run the script in 2021.2 anyway but its erroring out very early on:
ratin@Ubuntu18:~/avnet_hdl_2021.2/scripts$ source make_zub1cg_sbc_base.tcl
bash: make_zub1cg_sbc_base.tcl: line 49: syntax error near unexpected token `}'
bash: make_zub1cg_sbc_base.tcl: line 49: `} else {'
Should I be able to create a new design in 2019.2 branch with make.tcl if I copy the board files from 2021.2 and put into 2019.2 board directory? What other files need to be copied over?
Thanks
Ratin
Hi Ratin, sorry for the delay. I have done this previously for the ultra96_v2 board using Vivado 2021.2 version. Refer to "Second Approach" section in the following blog (+) Path to Programmable 3 - Training Blog 2 - In search of a simplistic hardware design, PS configuration and tool automation. - element14 Community
You might need some additional files and repos. Just follow the below file structure if it helps, then you can trace back at what files are being called by the scripts.
$ cd ~
$ mkdir zub1cg_2021_2
$ cd ~/zub1cg_2021_2
$ git clone https://github.com/Avnet/bdf
$ git clone -b 2021.2 https://github.com/Avnet/hdl
$ git clone -b 2021.2 github.com/.../petalinux
ratin@Ubuntu18:~/zub1cg_2021_2/hdl/scripts$ source vivado -mode batch -source make_zub1cg_sbc_base.tcl -notrace -tclargs zub1cg_sbc base
Migrating the design from 2021.2 to 2019.2 should be doable, as long as you check what IP's have changed across the two versions and make sure you look at the critical warnings and warnings in the migrated design.
And also (+) Avnet Boards Forums - element14 Community might be more appropriate for more support.