gentlemanJack

Newcomers
  • Content Count

    3
  • Joined

  • Last visited

About gentlemanJack

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Hi vincentiu and zygot, OK, this just in: Up and running now. I moved to my laptop and used a fairly nice looking 3 foot USB A to microB cable. It works both with a powered USB hub and with just the cable itself. Tried it about ten times to "open the hardware manager", and downloaded the blinky program from the Digilent "Getting Started with Vivado". Laptop has Vivado webpak 2019.1 loaded. On my laptop, the connected cable shows up in two ways on my Device Manager: (1) as a serial port at 9600, 8N1 with FTDI device driver 2.12.28.0, 8/16/2017 and (2) as Universal Serial Bus controllers with two entries, USB serial converter A and USB serial converter B. I also, per vincentiu, added a 100nF capacitor, 0603 size, unknown manufacturer before I started. As I get more Cmod A7 I will try with and without. I did design the Cmod A7 into my board, but before I go into production, I will look at the boards that have JTAG. I really, really like the Cmod A7 form-factor and that users don't have to buy a Xilinx cable. We'll see how the next few work. I just can't have this same problem affecting my customers. Don't know why my tower doesn't work but my laptop does. My guess would be something's wrong with the software on my tower, but it was kinda homemade with a Megatrends motherboard, my laptop is a very new Lenova. FYI, I found a fairly nice USB A to micro B cable, that I have not yet received from a certain retail mega-monolith whose name begins with "A", supposed to be good for 480Mbps, 24AWG, search for "iKits micro USB cable". I am getting both the half foot and 4 foot versions. I will report on results in a day or so. I have been an occasional user of FGPA for many years, and I remember the troubles that Xilinx had with Serial Parallel Cable 2, first a version with a black housing, then an improved version with a red housing so people could instantly know they had the good new one. So the cables have historically been difficult. Finally, zygot, I would like to email with you about my frequency counter project. As it has to deal with asynchronous input - nature of the beast - it will be a little tricky. Don't know if the moderator can set us up, or whatever. If not possible, that's OK. Let you know about these iKits cables in a few days. - gentlemanJack
  2. I have been trying to start my Cmod A7 today. Ran into this cable driver problem. Lots of discussions about it on the Diligent forums over maybe 3 or 4 years. My Vivado is 2017.4, Windows 10 64-bit. I went thru the "Getting Started with Vivado" tutorial, got the needed files, no problems with anything, generated a bitstream and …. when I tried to auto-connect with the Hardware Manager (by hitting "Open Target") It shows localhost(0) is Connected, but it also says: 'No hardware target is open' and "Program Device" in the Flow Navigator is still grayed-out. And yes, I tried 4 different microUSB cables, including a 1 foot long. My CmodA7 out of the box has the "DONE" light on, and the pushbuttons change the LED[2:0} indicating that the CmodA7 has a program already in it. I read that some people install Adept 2. I ran install_digilent.exe which I found under C:\XilinxFull\Vivado\2017.4\data\xicom\cable_drivers\nt64\digilent and it says I am up-to-date in a window that says "Digilent Adept Runtime Setup". I also read about windrvr6.inf and xusbdrv.inf being a problem for Vivado Versions 2017.4 and 2018.2. I see them under dlc10_win7 (which contains 18 files) but not under dlc10_vin10 (which only has 3 files) I did run install_drivers_wrapper.bat as described in the forum: https://www.xilinx.com/support/answers/59128.html, running the cmd window as admin, moving the prompt to C:\Xilinx\Vivado\2017.4\data\xicom\cable_drivers\nt64 install_drivers_wrapper.bat C:\Xilinx\Vivado\2017.4\data\xicom\cable_drivers\nt64 c:\Xilinx\Vivado\2017.4\install.log c:\Xilinx\Vivado\2017.4\ ... this is the log file results ...... NFO: InstallPath="C:\XilinxFull\Vivado\2017.4\data\xicom\cable_drivers\nt64\" windrvr6 is not installed. INFO: Installing Windows 10 pcusb driver... Microsoft PnP Utility Processing inf : xpcwinusb.inf Driver package added successfully. Published name : oem67.inf Total attempted: 1 Number successfully imported: 1 INFO: INF file C:\Xilinx\Vivado\2017.4\data\xicom\cable_drivers\nt64\dlc10_win10\xpcwinusb.inf was successfully installed for driver. INFO: Running digilent installer... <<<<< Digilent Adept Runtime Setup >>>>> Installer version: 1.4.6 release: 2015/12/08 Digilent Software Path: C:\Program Files (x86)\Digilent Your system is up-to-date with the components of this installer. INFO: Running SmartLynq installer... INFO: SmartLynq installed successfully .... So... going forward, should I: (1) install latest Vivado (maintenance fee?) (2) see why dlc10_win10 only has 3 files (3) get a download of Adept 2 and use it to download the .bit file from Vivado (4) put a large capacitor on the USB 5V Rail as described in https://forum.digilentinc.com/topic/4769-vivado-hardware-manager-disconnects-cmod-a7-target-in-win7/, Jan 10. (5) call today a bad investiment and find another FPGA board
  3. I tried to find the lastest forums on this often discussed CMOD A7 cable problem. I hope I choose the right one. I knew nothing of this problem, but designed-in a CMOD A7 on a project to do precision frequency counting. I started this morning, and hit this problem immediately. I only have one board. At the bottom of my story, I list 5 actions that I could take. Can people experienced with this problem comment? Particularly on Item 5, if there is a more robust Digilent board that has traditionaly Xilinx parallel cable 2. My Vivado is 2017.4, Windows 10 64-bit. I went thru the "Getting Started with Vivado" tutorial, got the needed files, no problems with anything, generated a bitstream and …. when I tried to auto-connect with the Hardware Manager (by hitting "Open Target") It shows localhost(0) is Connected, but it also says: 'No hardware target is open' and "Program Device" in the Flow Navigator is still grayed-out. And yes, I tried 4 different microUSB cables, including a 1 foot long. My CmodA7 out of the box has the "DONE" light on, and the pushbuttons change the LED[2:0} indicating that the CmodA7 has a program already in it. I read that some people install Adept 2. I ran install_digilent.exe which I found under C:\XilinxFull\Vivado\2017.4\data\xicom\cable_drivers\nt64\digilent and it says I am up-to-date in a window that says "Digilent Adept Runtime Setup". I also read about windrvr6.inf and xusbdrv.inf being a problem for Vivado Versions 2017.4 and 2018.2. I see them under dlc10_win7 (which contains 18 files) but not under dlc10_win10 (which only has 3 files) I did run install_drivers_wrapper.bat as described in the forum: https://www.xilinx.com/support/answers/59128.html, running the cmd window as admin, moving the prompt to C:\Xilinx\Vivado\2017.4\data\xicom\cable_drivers\nt64 install_drivers_wrapper.bat C:\Xilinx\Vivado\2017.4\data\xicom\cable_drivers\nt64 c:\Xilinx\Vivado\2017.4\install.log c:\Xilinx\Vivado\2017.4\ ... this is the log file results ...... NFO: InstallPath="C:\XilinxFull\Vivado\2017.4\data\xicom\cable_drivers\nt64\" windrvr6 is not installed. INFO: Installing Windows 10 pcusb driver... Microsoft PnP Utility Processing inf : xpcwinusb.inf Driver package added successfully. Published name : oem67.inf Total attempted: 1 Number successfully imported: 1 INFO: INF file C:\XilinxFull\Vivado\2017.4\data\xicom\cable_drivers\nt64\dlc10_win10\xpcwinusb.inf was successfully installed for driver. INFO: Running digilent installer... <<<<< Digilent Adept Runtime Setup >>>>> Installer version: 1.4.6 release: 2015/12/08 Digilent Software Path: C:\Program Files (x86)\Digilent Your system is up-to-date with the components of this installer. INFO: Running SmartLynq installer... INFO: SmartLynq installed successfully .... So... going forward, should I: (1) install latest Vivado (maintenance fee?) (2) see why dlc10_win10 only has 3 files (3) get a download of Adept 2 and use it to download the .bit file from Vivado (4) put a large capacitor on the USB 5V Rail as described in https://forum.digilentinc.com/topic/4769-vivado-hardware-manager-disconnects-cmod-a7-target-in-win7/, Jan 10. (5) call today a bad investment and find another FPGA board