MarkSe

Newcomers
  • Content Count

    16
  • Joined

  • Last visited

About MarkSe

  • Rank
    Member

Recent Profile Visitors

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

  1. Not sure if it is helpful, but I wrote up my experience in this blog post.
  2. Thank you. That will help others I am sure.
  3. Hi @JColvin my issue turned out to be because of Microsoft Hyper-V. It was blocking access to the ports required by Vivado. Once I disabled Hyper-V everything worked as expected and I've been able to connect and program my Basys3. I think you should add a note for users somewhere about this because it was very difficult to identify this unexpected issue. Having this captured could save future users some significant time and frustration. It may be possible but I was unable to find a way to unblock the needed ports. Mark
  4. @JColvin @attila Thank you everyone for your help! It turned out that Windows Hyper-V was excluded the port ranges needed for Vivado. I disabled Hyper-V and now I am able to connect to the device. I don't know if there is a way to tune Hyper-V to relax the port restrictions. Either way you may want to post some sort of notice for others who may encounter this issue in the future. Now I can get back to Verilog coding with my Basys3. Yay!
  5. @attila Thank you for that suggestion. There are no rules set in my Firewall and I was never prompted by the Windows Firewall. I believe that is because I use Norton Security. I've disabled Norton to eliminate that as a possibility. I am wondering now if the virtual networks associated with Hyper-V could be interfering. I have Hyper-V enabled for mobile app development.
  6. @JColvin Following the Xilinx thread you linked I typed the following in the TCL command prompt: hw_server -s TCP::3121 -d This produced the following error message: INFO: hw_server application started INFO: Use Ctrl-C to exit hw_server application Cannot create listening port: Socket bind error. An attempt was made to access a socket in a way forbidden by its access permissions So something is definitely preventing the Vivado hw_server from running.
  7. @JColvin Yes, I just installed the newer version of Digilent Adept and when I run it I am able to find the device. I never tried to run an earlier version of Adept. Please let me know if there is some information from the Digilent app that I can provide to help. I am reviewing the Xilinx thread that you shared.
  8. @JColvin I also show Digilent USB Device in Device Manager under Bus reported device description. So it appears the board/cable connection is healthy and the drivers are there. I am at a loss for how to fix this, is there a way to change the ports used by Vivado? Mark
  9. @JColvin I am not sure if this is a valid check but if I try to run the hw_server.exe manually from Vivado\2020.1\bin\unwrapped\win64.o I get the following output: D:\Xilinx\Vivado\2020.1\bin\unwrapped\win64.o>hw_server.exe ****** Xilinx hw_server v2020.1 **** Build date : May 27 2020 at 20:24:38 ** Copyright 1986-2020 Xilinx, Inc. All Rights Reserved. INFO: hw_server application started INFO: Use Ctrl-C to exit hw_server application Cannot create listening port: Socket bind error. An attempt was made to access a socket in a way forbidden by its access
  10. @JColvin I tried uninstalling the drivers for "USB Serial Converter A", reboot and then reinstall the cable drivers. This installed an earlier version of the FTDI drivers than what had been on my machine. Same result 'connect_dw_server' failed. I then updated the drivers in Device Manager, which pulled down the latest Microsoft Hardware Compatibility FTDI drivers. Same result. The fact that the device enumerates suggests this is not a board/cable problem. But somehow there is an issue with getting the right cable drivers or with Vivado launching the hw server. I would really apprecia
  11. @JColvin thank you for that. I tried to install the drivers using the executable you mentioned from an Administrator Prompt. I appeared to succeed. When I look in the Device Manager under the Universal Serial Bus Controllers node I see both "USB Serial Converter A" and "USB Serial Converter B". However the device description on the Details tab for both says "USB Serial Converter A (or B)" Looking at the Events tab shows the following error during driver install. I have one of these events from the install using the .bat file and one from the executable you recommended. Here are the respec
  12. Should I see something enumerated in the Device Manager? If so, what node should I look under?
  13. Hi J, Thank you for your reply! I am hoping to get this up and running so I can port my Spartan-3E projects over. Yes, when I plug it into the USB and turn it on it powers up. The jumper is set to JTAG mode. And I just reinstalled the cable drivers per the link that you provided. It still says the same think when I click on "Open Target" from the HW manager and choose Autoconnect. The instructions in that link for the install_drivers_wrapper.bat appear to be wrong as it complained about the extra parameters. I ran the command prompt and Vivado both with Admin rights. Here is the
  14. MarkSe

    HS3 HW_Server trouble

    @Bianca I am having a similar issue with a Basys3 that I just received. What specifically should I look for in the Device Manager to help identify whether the Basys3 device is listed? Mark
  15. I just acquired a Basys3 to replace my old Spartan-3E board. I followed the instructions and setup Vivado 2020.1, the board files, and created a project. After finishing Synthesis when I open the HW Manager it is unable to connect to my device. This is the output that I receive. connect_hw_server -allow_non_jtag INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121 INFO: [Labtools 27-2222] Launching hw_server... INFO: [Labtools 27-2221] Launch Output: ****** Xilinx hw_server v2020.1 **** Build date : May 27 2020 at 20:24:38 ** Copyright 1986-2020 Xi