User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
springremote [2020/06/02 09:26] nelson [Option #4: Run Xilinx Software on Lab Machines But Program Board with Mac] |
springremote [2020/09/02 17:06] (current) nelson [Option #5: Vivado on a Linux Virtual Machine] |
||
|---|---|---|---|
| Line 92: | Line 92: | ||
| ===== Option #3: Run Xilinx Software on Lab Machines But Program Locally Using openocd (Mac or Linux)===== | ===== Option #3: Run Xilinx Software on Lab Machines But Program Locally Using openocd (Mac or Linux)===== | ||
| - | If you have problems with Options #2 or #5 you can use this one. It is a hybrid of #2 and #3 and requires a much smaller download. | + | If you have problems with Options #2 or #5 you can use this one. It is a hybrid of #2 and #3 and requires a much smaller download (has the same pros and cons as Option #2). |
| - | This assumes you will use LabConnect as in Option #3. CAEDM does have a LabConnect option to allow you to work on the BYU lab machines - follow the instructions above but do the Mac version of the install. Most everything else is similar. Once you have LabConnect installed you will be able to do Vivado designs on a lab machine in the department. | + | This assumes you will use LabConnect as in Option #2. CAEDM does have a LabConnect option to allow you to work on the BYU lab machines - follow the instructions above but do the Mac version of the install. Most everything else is similar. Once you have LabConnect installed you will be able to do Vivado designs on a lab machine in the department. |
| The problem is that once you finish your design, you need a way to get the .bit file onto your local machine to program the board you have. The following instructions show how to set up that step. | The problem is that once you finish your design, you need a way to get the .bit file onto your local machine to program the board you have. The following instructions show how to set up that step. | ||
| Line 101: | Line 101: | ||
| -------------------- | -------------------- | ||
| - | Option #3: Run Xilinx Software on Lab Machines But Program Locally Using A Linux VM and Vivado_Labs (Mac) | + | =====Option #4: Run Xilinx Software on Lab Machines But Program Locally Using A Linux VM and Vivado_Labs (Mac)===== |
| - | If you have problems with the options above you can use this one. | + | This uses LabConnect like Options #2 and #3 but then uses a Linux Virtual Machine containing a stub of Vivado called 'Vivado_Labs' to actually program the board. You would only use this if Option #3 fails for you. It requires a much larger download and is much more complex than above. |
| - | This assumes you will use LabConnect as in Options #2 and #3. CAEDM does have a LabConnect option for both Windows and Mac computer. Follow the instructions in Option #2 above but do the Mac version of the install. Most everything else is similar. Once you have LabConnect installed you will be able to do Vivado designs on a lab machine in the department. | + | This assumes you will use LabConnect as in Options #2 and #3. Follow the instructions in Option #2 above but do the Mac version of the install. Most everything else is similar. Once you have LabConnect installed you will be able to do Vivado designs on a lab machine in the department. |
| The problem is that once you finish your design, you need a way to get the .bit file onto your local machine to program the board you have. The following instructions show how to set up that step. | The problem is that once you finish your design, you need a way to get the .bit file onto your local machine to program the board you have. The following instructions show how to set up that step. | ||
| Line 113: | Line 113: | ||
| - Once the VM boots, you need to run vivado_lab - that is the tool to actually program the board. Here [[https://byu.box.com/s/md5alzeon4vervn2e596x2xbvq1tv4qr|is a video of that]]. | - Once the VM boots, you need to run vivado_lab - that is the tool to actually program the board. Here [[https://byu.box.com/s/md5alzeon4vervn2e596x2xbvq1tv4qr|is a video of that]]. | ||
| - Later, you may need to be able to transfer things from your Mac to your Linux VM (like bitstreams if you upload them to your Mac). To do so, here [[https://byu.box.com/s/hocmgtxk2669t541hw7awaif5hd5i97d|is a video on that]]. | - Later, you may need to be able to transfer things from your Mac to your Linux VM (like bitstreams if you upload them to your Mac). To do so, here [[https://byu.box.com/s/hocmgtxk2669t541hw7awaif5hd5i97d|is a video on that]]. | ||
| - | |||
| - | So, the big picture is this: (a) use LabConnect to do FPGA design on the department lab machines, (b) copy the resulting .bit file from the department machine to your local machine (in the Linux machine), (c) program the .bit file into the FPGA using vivado_lab. | ||
| - | |||
| -------------------- | -------------------- | ||
| Line 123: | Line 120: | ||
| Using the VMWare software, you will boot and run a copy of the Linux operating system | Using the VMWare software, you will boot and run a copy of the Linux operating system | ||
| - | on your own computer. You can run this on either a Windows machine or a Mac, but this is the | + | on your own computer. You can run this on either a Windows machine or a Mac, but the main use for this is if you have a Mac. |
| - | only option for you if you have a Mac. | + | |
| PROS: | PROS: | ||
| Line 134: | Line 130: | ||
| * It can be a bit resource-intensive (you are running Linux and your own computer's operating systems at the same time). | * It can be a bit resource-intensive (you are running Linux and your own computer's operating systems at the same time). | ||
| * There is an extra layer of complexity with this operating- system-inside-an-operating-system. Having the virtual machine involved may require extra attention to some details to keep it working. | * There is an extra layer of complexity with this operating- system-inside-an-operating-system. Having the virtual machine involved may require extra attention to some details to keep it working. | ||
| - | * Will take up 30-60 GB of disk space on your machine as you install it, less once the install is done and you delete all the intermediate files. | + | * Will take up > 70 GB of disk space on your machine during the install. Once it is installed then it takes up about half that (after you delete the intermediate files). |
| + | |||
| + | Before you start be aware that you need to have sufficient RAM as well. I have 16 GB on my machine and 12 CPU cores. I give 8GB RAM and 6 cores and it runs well. What you only gave it 4GB? Don't know for sure but I believe students have been OK with that. | ||
| ==== Instructions==== | ==== Instructions==== | ||
