bakalei dweller tomasyne
Nadia Summerhill
Is there a way to specify which version of Xilinx Compilation Tools to use when compiling an FPGA VI? I want to try the Vivado version of the tools rather than the ISE version to see if there is any improvement. I've listed some information about my setup below.
In the past I have used the 'LabVIEW 2014 FPGA Module Xilinx Tools 14.7' to compile my code. But I also want to try the Vivado version, 'LabVIEW 2014 FPGA Module Xilinx Tools Vivado 2013.4', to see if it gives better results.
Based on the 'Compatibility between Xilinx Compilation Tools and NI FPGA Hardware' page here:
-between-xilinx-compilatio...
It looks like the PXIe7966 FPGA should be compatible with the Vivado 2013.4 tools.
I have tried uninstalling the ISE 14.7 version of the tools, and installing the Vivado 2013.4 tools (so that the Vivado 2013.4 tools are the only xilinx tools installed on the computer). But LabVIEW still complains that the ISE 14.7 tools are not installed and does not compile the FPGA VI.
Thanks for the additional reference link! Although I am going to mark the other reply as the solution because this was really due to the fact that vivado does not support any virtex 5 FPGAs (not really a LabVIEW concern).
I have a Basys-3 board that I would like to program and debug using the Vivado HW Manager. Unfortunately, Vivado does not recognize the Board at all. I tried several different versions of Vivado and they all cannot recognize the board. I also tried Impact, which cannot connect to the cable. Since I received the board from a former colleague I am not sure if he did something with the FTDI on the board or if it is still programmed correctly. It may also be some windows driver problem (I am using Windows 10 64 Bit). Please help me with this issue. Thank you very much in advance.
Have you gotten to try a different USB cable or USB port on your computer? Some cables do not properly transmit data and focus on charging. I'm presuming that when you connect the USB cable to the Basys 3 on J4 and turn the board, the power good LED turns on.
I tried several different Micro-USB cables on different ports (front usb, backside usb and usb hub). I tried a different PC with Windows 7 as well. I also reinstalled the drivers. The board is powered on and I tried all jumper positions (shouldn't matter since the manual says that JTAG programming is always possible and the jumper only prevents startup from flash etc.). The USB Serial Converter A and B are listed in the device manager, but Vivado can't see the cable at all. Neither can Impact or the chipscope analyzer.
In the interest of better determining the potential root cause, do the USB Serial Converters in the Device Manager have a Bus Reported Device Description (Details tab in their Properties) of Digilent USB Device, or have something else listed? If you can, I'd like to know if Digilent's Adept system, , is able to detect the Basys 3; the reason for this is because Xilinx uses Adept's underlying drivers to detect and connect Digilent hardware through the FTDI solution, making this a "from source" option.
Out of curiosity, when the jumpers are set to have the Basys 3 boot from flash memory, does the board seemingly do anything (switches turn on LEDs, activity on a serial terminal, etc)? If the board does do something that would at least indicate that the on-board FPGA is functional, though of course if nothing is observed that isn't a guarantee that the FPGA is broken (maybe the flash is empty or programmed with a non-visual .bin file).
thank you very much for the answer. The bus reported device description is indeed "Digilent USB Device" on both serial converters. The Adept system was unable to detect anything unfortunately. The board does boot up correctly (the demo design is loaded and the leds are flashing and so on), if the jumper is set to QSPI. Everything seems ok, but it somehow doesn't want to detect the board. Could be a driver conflict or the FTDI not being programmed correctly.
@JColvin Hello, I read all conversations above. I am also dealing with same issues. I am using Nexys A7 FPGA board. This board is not detecting at all. I changed USB cable, still not works. With the same cable, Zybo Z7 board is connecting well. But issue is with Nexys A7.
Hello! I am also having the same problem. I am using a Basys 3 board. I've done all the instructions above but the board still cannot be detected. I would really appreciate some help.
Thank you!
Hi there,
I found this thread in search of the solution to the similar problem. I have just purchased Basys 3 board.
It is on windows 11 machine with correct microusb cable with Vivado 2022.
The problem appears to be with driver installation as I can only see USB Serial Converter B and a COM port as USB Serial Port [as shown in figure attached, with red arrows]. From many answers that I have read, normal behaviour of the board would show USB Serial Converter A and B under USB controllers section in device manager. In my case USB Serial Converter A is missing!
I have tried reinstallation of the Vivado as well but no luck. Vivado only connects to the localhost and then does not detect any fpga board when I press autoconnect.
Should I attempt to reprogram FTDI as some suggesting in this thread.
Any help will be greatly appreciated!
I am having the same problem, USB Serial Converter A and B are listed in the device manager, description is "Digilent USB Device" on both serial converters. But, in my case, the adept system does detect my board.
From what you have described, the Basys 3 is properly detected by both Adept, the Windows OS, and other computer systems, but other working Basys 3's are not being detected on your system (presumably you mean the Vivado software in this instance since you did not clarify what you meant by not working, i.e. not powering on, not detected by the operating system, not detected by Adept, not detected by Vivado, something else), this indicates to me that the Vivado software is the most likely source of this issue.
- Restart Vivado
- Check that the hw_server isn't still running in the background while Vivado is closed
- Make sure the drivers that Xilinx wants to use are installed in the place where Xilinx wants to look for them ( -US/ug973-vivado-release-notes-install-license/Install-Cable-Drivers)
- Make sure that Artix 7 architecture is installed with your Xilinx install via Manage Devices in the Xilinx Information Center (shouldn't affect the driver installation status and likely isn't the issue but writing it down anyways)
- Restart computer
- Uninstall and reinstall Vivado
I am using basys3 and it is not seen by the hardware manager and adept also. Same issue that @Martin2000 described. could you help me please in the device manager The USB Serial converter A is missing.
Hello, I read all conversations above. I am also dealing with same issues. I am using digilent Arty 7 FPGA board. This board is not detecting at all. I changed USB cable, still not works. With the same cable, other board is connecting well.
I have a ZedBoard (Zynq XC7Z020) on which I wish to prototype some software on a MicroBlaze that will eventually be moved to a ZCU-102, and ultimately to a custom IO card. I was given the ZedBoard and installed the Xilinx software that came with it, but ISE 14.1 seems to have some trouble with Windows 10 (file selection dialogs don't always appear, and it can't seem to talk to the network very well), so I've installed Vivado 2021.1. Unfortunately, none of the directions I've found for installing the board files work properly under this version of the tools - it seems the stuff on GitHub (XilinxBoardStore / XilinxCEDStore) are not supported (I can't get them to work following the directions I've found, at least), and when I tried editing the Vivado start-up tcl script, the XML files appear available on the Diligent site seem to be incompatible (it breaks Vivado), so I cannot seem to create a project for the ZedBoard using Vivado 2021.1.
I beg to differ. In fact Vivado is no good for doing PCIe based designs for the NetFPGA-1G-CML board that Digilent sells. I know, because I've tried. The Vivado support for PCIe simply doesn't work ( at least on Vivado 2019.1 forward ) for the XC7K325T-1FFG676 part for this board because it only has 4 transceiver lanes, because of the lanes that the board designers chose to use, and because Vivado refuses to let you select the correct GTX bank. If anyone has discovered how to do this I'd like to know the secret.
So, I've been using ISE on WIN10 for over a year for devices that aren't supported by Vivado and for the aforementioned platform. I didn't use the latest archived version of ISE 14.7 from Xilinx to install it, but used an old DVD from Xilinx.. from back when the tools installer fit one DVD. Installation wasn't straightforward for sure but that version of ISE 14.7 supports Spartan 3, unlike the archived version available from the Xilinx download site. But the tools needed to create a bitstream do work on WIn10.
I haven't tried ChipScope or IMPACT, and ISIM has issues on Win10, but on occasion ISE is the only option for some projects. The ISE installer is less than 4 GB. Compare that to Vivado. ISE has bugs but not to the extent that every new version of Vivado has.
I would suggest that an earlier version of Vivado, say 2018.4, might be the best option for the Zedboard. I've done Vivado development for that board on Win10. One thing to you need to do is figure out if the version of your board is supported by Vivado. I have an older one had to spend some time trying to figure out what board version to choose and what the revision changes were because the Vivado installations that I have on Win10 don't support my board explicitly.
In some ways ISE is easier to work with than Vivado. I haven't seen any dramatic improvement in synthesis or P&R with Vivado. IMPACT can be a pain in the neck but I use the very useful Adept Utility for Windows to configure the FPGA. The one thing that Vivado does improve on is the integration of the debug tools into the GUI. ChipScope is clunky and you need a license to use it.
c01484d022