MiniZED Vivado VM image ? the document really does not spell out where this VM image is ? Any help ?

Question

The MiniZED makes a special point of having you install the Oracle Virtual Box -- got that all done. Then it says there is a pre-loaded image for Vivado? Where is it?

clem57 · Accepted Answer

https://forums.xilinx.com/t5/Xilinx-Evaluation-Boards/ZCU104-pre-built-image-2018-2-VIvado-design-availability/td-p/8976…

Fred27 · Answer

There are quite a few broken links and URLs in the guide. There's also quite a few places where it still mentions version 2017.4 (I think).

I found that installing Vivado and SDK/Vitis directly on a Windows 10 machine was fine for following the Hardware and Software courses. No need for the VM. (I was also trying PetaLinux tools installed within WSL2 which initially seems OK, but I'm being bitten by the fact I installed 2019.2 at the moment.)

Fred27 · Answer

I managed to follow both the HW and SW tutorials using Vivado installed directly on Windows 10. No need for a VM. I managed to use 2019.2 and Vitis without too much trouble - the main different is how a project and BSP is started in Vitis compared to the SDK in 2019.1. I'm not sure exactly where in the labs you are, but if you've installed 2019.2 too then I suspect you might be at this point. The lab is probably expecting you to be running the SDK. You'll need to run Vitis, pick a workspace and "Create Application Project" and then create a new platform for hardware (XSA). To be honest it's a little too much to explain in a single post. You might find it useful to follow a guide that uses Vitis first such as https://www.hackster.io/adam-taylor/mini-but-mighty-the-minized-and-vitis-for-motor-control-9c376b I've just moved on the Petalinux stuff and trying to use 2019.2 which is confusing the hell out of me (again).

beacon_dave · Answer

" the document really does not spell out where this VM image is ? The Lab 0 setup document gives you a link: DOWNLOAD LINK FOR PRE-BUILT VM FILE (2GB size): http://avnet.me/Ubuntu_16_04_Virtual_Box_2019_1 It also warns you that this image doesn't include the recommended Vivado Design Suite 2019.1 tools for use with the labs: " Unfortunately Xilinx will not allow pre-installed tools to be distributed along with the pre-made Virtual Machine. This is due to licensing policies and export control requirements. "

ralphjy · Answer

In my brief experience with the Xilinx tools I've decided to take the path most traveled (which I think is Linux). I'm glad that you've got things working on Windows and I'll be interested hearing about your progress. I have a dedicated Linux box but I've gone the VM on Windows route because of all the different dependencies between the tool versions and OS versions and also because it seems like this path is pretty well supported by Xilinx and Avnet . I have different VMs for each combination that I use. I have learned to be very careful to not update the OS once it is installed. I hate that minor OS versions cause problems with the tools (e.g. I had problems using Ubuntu 16.04.6 with the 2018.3 tools when I was working with the Ultra96v2. I had to downgrade to 16.04.4 to get things to work). I was particularly worried about running PetaLinux with WSL as I haven't used WSL much and Ubuntu in VirtualBox seems to have a lot more mileage on it. I guess I'm a lot less adventurous in my old age . It would be nice if pre-built VM images were available for the different variants that are recommended (maybe the links just need to be fixed?). External disks are pretty cheap nowadays so I don't mind having having a plethora of VMs - just need a spreadsheet to keep track of what I put in them .

gregcasey · Answer

Thanks Ralph and Fred I assume from the thread that a 2019_2 Tutorial does not exist yet, and I should use the hackster link he provided. Do you know who to ask about a schedule when a corresponding 2019_2 training update would be available? By the way, I sure appreciate the detailed, excellent guidance both of you have provided. This subject is confusing enough for a novice, and to have a lab course ware, wrong, make it even more challenging. Greg

Fred27 · Answer

As Ralph said, this point is where 2019.1 (with SDK) and 2019.2 (where it's replaced by Vitis) diverge a bit. The guide I linked to is worthwhile but if you're brave you can try: In Vivado - Tools / Lanch Vitis Pick a workspace folder Create Application Project Pick a project name Create a new platform from hardware (XSA) Click "+" and find the XSA file that Vavado 2019.2 created for you. (XSA is the new HDF) The handling of BSPs is different in Vitis compared to SDK. Under Application Project Settings click "Navigate to BSP Settings" You should find you're in a similar place to the guide you're following for 2019.1 I've always found tools versions awkward with Vivado. Strangely for what seems like a point release, 2019.1 and 2019.2 are very different when it comes to this part. You may find installing 2019.1 to be worthwhile for you sanity if following this guide.

ralphjy · Answer

The problem you are having is trying to use a 2019_1 tutorial with the 2019_2 toolflow. Vitis has amongst other things replaced the SDK. Vivado_2019_1 generates a hardware archive file with the extension .hdf and that is used with the SDK. Vivado_2019_2 generates a hardware archive file with the extension .xsa and that is used with Vitis. You will have a hard time following the 2019_1 labs unless you know the differences required using Vitis. The look and feel of the tool is different but it has the required functionality. If you install the 2019_1 Vivado Webpack, that will install the SDK. In that case you will not be able to use Vitis. If you want to stay with 2019_2, I would find a tutorial that uses Vitis. The one that Fred provided a link for is a good one.

gregcasey · Answer

Thanks to Ralph and Fred - Got to Hello Word-- Yeah --- - I decided to delete 2019_2 and load 2019_1. - Just too many gaping holes in documentation on 2019_2 and lack of flow understanding on my part of the entire tool chain. - I look forward to an update of the Tutorial Series that embraces 2019_2 and Vitis in the future. I like the more integrated platform of 2019_2, but as a novice, lack of a error-free tutorial was too much. Greg

MiniZED Vivado VM image ? the document really does not spell out where this VM image is ? Any help ?

Top Replies