• Content count

  • Joined

  • Last visited

About kpax

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. kpax

    Cannot talk to Arty board with Vivado 17.2

    Bianca, I tried manually installing the drivers, but nothing changed. The Device Manager looks exactly the same as before. One thing I'm curious about is the Jungo>WinDriver. This stays that way no matter if any USB cables are plugged in or not. I think Xilinx tools installs this as part of their installation.. I'm not sure. Can or should this be re-installed? Thanks for the help....
  2. kpax

    Cannot talk to Arty board with Vivado 17.2

    Hi Bianca, Thank you for responding…. I did what you said to do on my Laptop which is the computer I am trying to get the Arty board working on. The FTDIconfig program did not find the Arty board when “Find Devices” was pressed. I checked the dropdown box in step 2 but there was nothing there. I pressed “Get Info” and a box popped up saying “Failed FT_OpenEx”. I tried several other known good USB cables as well. Nothing seemed to work. I then tried doing this on my Desktop computer which originally also couldn’t find the Arty board. My Desktop Computer did find the Arty board and I managed to initialize it properly as per your instructions. I ran the Adept2 program and it does now seem to find the Arty board correctly. I also ran the hardware manager in Vivado 2017.2 and it also found the Arty board correctly. So, plugging the Arty board back into my Laptop, the laptop (Win7Prof-64bit, IntelI7 8core) now recognizes the Arty board with this message below. Monitoring “Device Manager” when plugging in the Arty board I see this: Note that “WinDriver”, “USB Serial Converter A” and “USB Serial Converter B” have the yellow sign on them. I am not sure where to go from here. Thank you very much for getting me this far. AT least I can get going on my desktop computer. -Kpax
  3. kpax

    Cannot talk to Arty board with Vivado 17.2

    Stephen, In both cases of "USB serial converter A and B", selecting update driver gives you the usual two options, Search automatically or Browse my computer. Searching automatically results in "The best software driver for your device is already installed". The other option I tried is ..\..\CDM v2.12.28 WHQL Certified\, this is where I un-archived the latest FTDI drivers. Selecting this results in the same message "The best software driver for your device is already installed”. I have tried installing (and re-installing) VIVADO on three different computers now and made sure I have a good USB cable without any luck. The crutch of the problem is as Jon mentioned is that the server cannot find the target. When bringing up ADEPT2 I see this: Both VIVADO 17.2 and SDK 17.2 find the hardware server Ok but the hardware server can’t find any targets. This is extremely frustrating as I have lost customers because I simply cannot get anything accomplished. This goes back to Zynq projects that never materialized because of these same issues. What was wrong in the way all this stuff used to work when we used a serial port or USB port? What is this added complexity with a “Hardware Server” anyways? Here’s a thought, can I go back to using my Xilinx “Platform Cable USB” cable to talk to the ARTY board? Does anyone know if Vivado works with it?
  4. kpax

    Cannot talk to Arty board with Vivado 17.2

    9/21/2017 Hi Stephen, That’s good to know, perhaps I have to uninstall everything and simply do a fresh install of Vivado 17.2. Did you have to install any of the FTDI drivers for the USB port? To answer your question: Before clicking on “Open target” After clicking on “Open target > Auto Connect” What I’m suspecting is happening here is that the local hardware server is connected properly with Vivado but the local hardware server is not properly connected with the target, meaning the USB connection to the Arty board. When I look at Device Manager as I plug in the Arty board I see… Before: After: It looks like 2 endpoints were established after the USB enumeration but the Local Hardware Server doesn’t recognize them. I believe the FTDI chip is the heart of the “Digilent USB-JTAG circuitry” and that the idea is to make the “Digilent USB-JTAG circuitry” appear like a serial port to the system. Not sure where to go from here…
  5. I have not been able to program anything on my ARTY board. I have re-installed Vivado 17.2 several times to make sure the "cable drivers" were installed. I am running the non-HLS version of Vivado 17.2.There is talk about this plug-in tool on the website: It implies that it allows Xilinx software tools to directly access Digilent USB-JTAG circuitry across Xilinx tool versions 11, 12, 13, and 14. So does that mean that newer versions of the Xilinx software tools (Vivado 17.2 lets say) will not drive any of the “Digilent USB-JTAG circuitry”? I assume that all the newer boards like Arty, Arty Z7, and Arty S7 also have this “Digilent USB-JTAG circuitry”. Or is this done differently? Then as a prerequisite to this install is to install “Adept 2”. This says it’s supported by Xilinx iMPACT (12.x, 13.x, 14.x only), Chipscope Pro, Xilinx Microprocessor Debugger (XMD), and EDK Software Development Kit (12.x, 13.x, 14.x only).What does this do?Then there is there is the driver for virtualizing the serial port which is part of the “Digilent USB-JTAG circuitry”. Can someone please tell me which of these are necessary to get Vivado 17.2 to talk to the Arty board? Can someone please tell me which order these have to be installed? Thanks everyone... Running: Win7 Professional. In particular, I cannot see the Arty board when I open the hardware manager in Vivado 17.2