ZUB1CG Board design unusable on Vivado 2022.1

Ratin 10 months ago

After much hassle to build me a ref design with the Script/make_zub1cg_sbc_base.tcl on Linux with many versions of Vivado, I ditched linux and finally got it to work on Windows. However after opening the project on Vivado, I'm not able to do anything on the the design, none of the buttons work and Vivado becomes unresponsive. is there a reason why its behaving like this? This is hapening both on WIndows and on Linux (same project file)

Thanks

Ratin

Parents

0 iksevas 10 months ago

The reason you would have issues in building the design on Linux is that your Linux workstation does not have all of the proper dependencies installed on the workstation. This information is usually provided by AMD in the Petalinux User Guide for the tool version you are trying to use.

Setting Up Your Environment • PetaLinux Tools Documentation: Reference Guide (UG1144) • Reader • AMD Technical Information Portal

The scripts on Avnet Github and the BSP on Avnet Sharepoint target Linux Workstation or Virtual Machine.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ratin 10 months ago in reply to iksevas

Hi, The script uses tcl and I got the script to work on Windows 10. It went thru creating a design , synthesize, P&R, create bitstream all that is completed successfully. But my question is when I open the generated project file (xpr) on Vivado, it chokes., nothing works. Why is that? I am using Vivado 2022.1 and I have a powerful desktop with 32 GB ram, 16 core Xeon processor.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 iksevas 10 months ago in reply to Ratin

Hmm.....I see a couple of things tools related:

Vivado hangs due to sigasi cache utilizing significant space

000034290 - Vivado GUI hangs while opening Block Design on some machines with CentOS 8, RHEL 8 and above

You may want to update to a newer version.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ratin 10 months ago in reply to iksevas

I had to open it in 2023.1 version and then when I opened it in 2022.2 it worked
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Ratin 10 months ago in reply to iksevas

I had to open it in 2023.1 version and then when I opened it in 2022.2 it worked
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 iksevas 10 months ago in reply to Ratin

That’s a weird one. I have had times where it locked up like that and then closing and reopening allowed it to work. At least you are progressing.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ratin 10 months ago in reply to iksevas

Thank you.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel