search

krtkl / snickerdoodle-board-files

14 stars 9 forks source link

Board files not recognized in Vivado 2018.2 #2

Open hwroot opened 6 years ago

hwroot commented 6 years ago

New Vivado doesn't recognize any of the snickerdoodle board files. This wasn't the case with Vivado 2017 I don't believe this is an issue with my Vivado because it was a fresh install on fresh system also I have 3rd party board files from Digilent for example and they are being recognized correctly by Vivado 2018.2

rgmorrison commented 6 years ago

I am also having this same issue. Any updates on how to fix this? The latest version I can run is 2017.2 (2017.4 also did not work). As a side note, if you use 2017.2 on windows 10, I had to follow this tutorial to get it working: https://www.xilinx.com/support/answers/69908.html

rgmorrison commented 6 years ago

hwroot, I have been told that the snickerdoodle team is working on a fix.

russbush commented 6 years ago

Can you describe this issue a bit further. I just went through a fresh install process for 2018.2 (both Windows 10 and Debian Linux) to find any issues but was unable to. Are you simply not seeing the board selection options when creating a new project? Do you see any errors in the TCL console when starting Vivado?

hwroot commented 6 years ago

OK interesting looks like issue was that I didn't have XSDK installed and Zynq-7000 package which I installed last night: image

I would still consider this a bug partially because I could see Digilent and Xilinx boards of Zynq family thus I didn't have Zynq-7000 package installed. Hopefully it will help others.

One other thing part0_pins.xml is empty none of the pins are described like what it is in Digilent board files: https://github.com/Digilent/vivado-boards/blob/master/new/board_files/zedboard/1.3/part0_pins.xml as a result it's not possible to assign them in Block Designer

rgmorrison commented 6 years ago

I am using a windows 10 system. I am not seeing the snickerdoodle boards show up at all. There are no errors in the Tcl console when Vivado 2018.2 starts up. I will try a fresh install and see if that fixes things.

rgmorrison commented 6 years ago

A reinstall did the trick. I needed to run the Vivado installer first and have that install both Vivado and the SDK. I believe I installed the SDK package first and put it in a different directory then Vivado the first time I installed 2018.2.