Technical Forum Moderator
  • Content count

  • Joined

  • Last visited

  • Days Won


malexander last won the day on February 11 2016

malexander had the most liked content!

About malexander

  • Rank
    Frequent Visitor

Profile Information

  • Gender

Recent Profile Visitors

881 profile views
  1. Artix-A7 non-GUI development

    Off the top of my head I'm not sure why it's failing. Hopefully one of the guys from the applications team or support team will chime in.
  2. Artix-A7 non-GUI development

    No you don't need to launch hardware server - the first line of the TCL script does that. You can use djtgcfg from the Adept Utilities package to program the FPGA. If I remember correctly the syntax is something like "djtgcfg prog -d <device_username> -i 0 -f config.bit". You can use "djtgconfig enum" to figure out the username string. I think the default for that board is CmodA7 so executing "djtgcfg prog -d <device_username> -i 0 -f config.bit" may do the trick, provided that config.bit is the name of the bitfile you want to load and that your current working directory contains that file.
  3. Artix-A7 non-GUI development

    Vivado has integrated support for the programming circuit on the CmodA7 so you can program both the FPGA and the flash using Hardware Manager. If you want to do this from the command line then the easiest way is with TCL scripts. I've attached the TCL scripts that we use to program the user demo into the flash during the manufacturing test. On a Windows machine you would use these by opening a command prompt, changing to the directory that contains both prof_flash_15t.tcl (or the other one in the case of the 35T) and CmodA7_User_Demo-15T.bin, and then executing "vivado -mode batch -source prog_flash_15t.tcl". The process should be very similar in Linux. If you want to program a bin file with a different name into the flash then you will need to modify the TCL script. prog_flash_15t.tcl prog_flash_35t.tcl
  4. Can't install windrvr6

    Hi Ryan, You can try running the Adept System inatller from the command line and passing in an argument that tells it the path to a log file. In order for this to work you must first create the file, as it will not create the file if it doesn't exist. For example, if you have an e: drive you could create an empty text document named "adept_install_log.txt" and then run the following command, which assumes the installer executable is also located at the root of the e: drive: "digilent.adept.system_v2.16.4.exe /LogFile="E:\adept_install_log.txt"" Be sure to use quotes around the filename that is specified for the log file. Hopefully the log will tell us something more than we already know. Thanks, Michael
  5. Can't install windrvr6

    Hi Ryan, Unfortunately that error code doesn't tell us anything other than that there were 3 driver packages present that couldn't be installed. It seems odd that neither our driver package nor Xilinx's WINDRV6 will install on your system. What operating system are you running? Is your user account a remember of the Administrators group? I feel like there was one person that had an issue like this before but I don't recall whether or not we found a solution. Maybe @attila remembers. Thanks, Michael
  6. Can't install windrvr6

    Hi Ryan, Try downloading and installing the latest version of the Adept System for Windows and installing it: That should give you the files that are missing. Once installed try using the auto connect option in Vivado's Hardware server and see if it will connect. You shouldn't need WINDRVR6 unless you have a Xilinx Platform USB cable or the equivalent on-board circuit. If for some reason you do need to use the Platform USB cable you will need to reach out to Xilinx's technical support team to see if they can help you install WINDRVR6. Thanks, Michael
  7. Can't install windrvr6

    Hi Ryan, WINDRV6 isn't part of our drivers package, it's actually the driver for Xilinx's Platform USB cables. As I recall the ZC706 uses a Digilent JTAG-SMT1 or JTAG-SMT2 module, and not Xilinx's Platform USB. However, I think the Vivado installer groups all driver installs together and runs the sub installers sequentially and that it attempts to install WINDRV6 before installing the remaining drivers and support files. I'm not sure if failure to install the first set of drivers results in the installer aborting or if it continues on to the next set. If you navigate to your Vivado folder do you see ".\lib\win64.o\FTD2XX.dll" and\or ".\lib\win32.o\FTD2XX.dll"? Also, if you go to control pannel, Programs and Features, do you see "Digilent Software" as an entry? Thanks, Michael
  8. @kpax It sounds like the Arty is working correctly on your desktop so we can rule out any EEPROM image issues, as well as any issues with the actual hardware. SInce this appears to be an issue with the FTDI driver not attaching correctly to the device re-installing Vivado over and over isn't going to help resolve the issue. I see you already tried updating the driver and that doesn't appear to have worked because Windows thinks it's the same driver that's already installed. Have you tried doing the following: 1. In the device manager under USB devices right click on “USB Serial Converter A” and click “Uninstall”. Do the same for “USB Serial Converter B”. 2. Disconnect the Arty from the PC 3. Reboot, reattach the board, and see if the driver gets properly installed/loaded If that doesn't work then another option is to disconnect the ARty board from your PC and then use FTDI's CDM Removable tool to uninstall the driver. They don't appear to have updated the tool in quite some time but it's still available for download from their website: If you want to try this disconnect the Arty board, run the application as an Administrator and put in “0403” for Vendor ID, “6010” for product ID and then click “Add”. After that click “Remove Devices”. Reboot and re-attach Arty board to PC with USB cable. This does a more thorough removable than just uninstalling the driver from the Device Manager, so I suspect you may get better results when reinstalling the driver. If none of the above works then perhaps try a different USB cable and/or different USB port. Thanks, Michael
  9. Command line utility for JTAG-SMT2-NC

    Hi Amirth, If you install the Adpet Runtime (System on Windows) and Adept Utilities package then you can execute "djtgcfg init -d JtagSmt2" and it will read back and display the ID codes. The software is available for download here: Thanks, Michael
  10. Waveforms SegFault

    @D@n So far I've been unable to reproduce the crash on my end. I opened hardware manager in Vivado and connected to the system monitor and even left it running. When I launch WaveForms without the DD plugged in it reports that no devices were detected but it doesn't crash. If I connect a Digital Discovery and launch WaveForms then it finds and properly configures it (see image). Please keep in mind that I installed the latest version of the adept Runtime and WaveForms using dpkg, and did not do any manual installation from the tar files. Can you execute "ldconfig -p | grep libftd2xx" at the terminal and paste the output here? Thanks, Michael
  11. Waveforms SegFault

    @D@n Can you tell me which version of Vivado you had the Nexys Video open in when Waveforms crashed? Also, does Waveforms crash if the NexysVideo is conencted and powered on but not open in Vivado? I setup a virtual machine running the same version of Ubuntu and am not experiencing any crashes with the Nexys Video attached. However, I have not tried it with Vivado running but will after you tell me which version you were using. Thanks, Michael
  12. Hi Vihang, I attached the schematic for the 14-pin adapter as well as a screenshot of the typical system board mating pin-out. I think the screenshot will answer most, if not all of your questions. Please note that the PS_SRST_B signal will only be present on Zynq boards. Also note that the JTAG-HS2 with 14-PA cannot drive PS_SRST_B and that if you need to drive that signal you will need a JTAG-HS3. Thanks, Michael JTAG 14PA.pdf
  13. Adept Utility for Windows and the 3A-DSP1800 device

    Hi Zygot, Having looked at the BSD files in ISE I do think it's possible that it's a typo. However, since I didn't add these devices to the list and since they've been there for many years I'm reluctant to modify jtscdvclist.txt that we publish in the installer. If you want to try changing it in your local copy there are two linesof the file that you will need to modify: 1. change "XC3SD$A 06800000h 0FE00000h" to "XC3SD$A 03800000h 0FE00000h" 2. change "1800 06840093h 0FFFFFFFh" to "1800 03840093h 0FFFFFFFh" Hopefully this will at least make it recognize the part. Thanks, Michael
  14. Adept Utility for Windows and the 3A-DSP1800 device

    HI zygot, Each FPGA series may have a different JTAG configuration algorithm and a different set of instruction codes. The Adept Utility (djtgcfg) and Adept Application were designed to configure CPLDs and FPGAs that are on Digilent system boards. It may or may not support parts that aren't on Digilent boards. That being said I do see the XC3SD1800A in the configuration file with an ID code of 0x06840093. Does the IDCODE reported by Adept match that one? On Windows the config file is located in "C:\Program Files (x86)\Common Files\Digilent\Data\jtscdvclist.txt". You may be able to add the IDCODE to the list if it's different from the one that's already there. Thanks, Michael
  15. DPTI: Synchronous Interface and JTAG

    Hi Stefan, That's correct you can't use the on-board JTAG programmer/debugger while using the synchronous DPTI interface. However, it should be possible to connect an external JTAG cable, such as the JTAG-HS2, to header J17 and use that to access the scan chain while simultaneously using DPTI. I haven't tried this myself but the on-board JTAG interface has tri-state buffers and is held in tri-state when not enabled so it should work. Thanks, Michael