Search the Community

Showing results for tags 'windows 10'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Calendars

  • Community Calendar

Found 9 results

  1. Hi, I am relatively new to FPGA programming and purchased recently the Zedboard. I am trying to implement a simple blinky Verilog design, written in Vivado, on the Zedboard. The Zedboard is connected via two ordinary USB cables to the Laptop - one from J17, one from J14. I am able to log into the Linux part of the Zynq and do all demos, but have no success implementing the blinky design into the FPGA part due to the "Program Device" option in Vivado staying grayed out after generating successfully the bitstream and trying to connect to the device. There seems to be an issue with the connection to the board (I am getting the message board not connected or not powered). The last step to "Program Device" is never available. I tried about 10 installations with different Vivado WebPack revisions and on 3 different laptops (2 with Windows 10, one with Windows 7). I tried also updating cable drivers and modifying the jumpers JP7 to 11 to different configurations. "Program Device" stays grayed out. I am out of ideas and am hoping someone can give me a hint what is going wrong. Thanks
  2. Hi folks, My current setup is Opensuse Tumbleweed, I am running Windows 10 under Virtualbox. Xilinx ISE / Impact runs fine under Linux, the Adept plugin recognizes Nexys 3 and the Adept utilities run fine: $ djtgcfg enum Found 1 device(s) Device: Nexys3 Product Name: Nexys3 User Name: Nexys3 Serial Number: 210182477273 $ djtgcfg -d Nexys3 init Initializing scan chain... Found Device ID: 34002093 Found 1 device(s): Device 0: XC6SLX16 Under Windows 10 inside virtualbox, after selecting the USB device to be owned by the Windows virtual machine, I get the following: C:\Users\Mr>djtgcfg enum Found 1 device(s) Device: Nexys3 Product Name: Nexys3 User Name: Nexys3 Serial Number: 210182477273 C:\Users\Mr>djtgcfg -d Nexys3 init ERROR: unable to open device "Nexys3" The USB device is recognized in the windows device manager as "Digilent USB Device". My intention was to use the Adept 2 GUI, which is way more convenient than the command line tools on Linux, but it is suffering from the same problem above. It does recognize I have a Nexys3 board connected, the Nexys 3 TM logo does appear, but when you tell it to initialize the chain, it says: "Initialization Failed. Check connections and try again." Inside the Adept status window I get: ===== Digilent Adept ===== Adept System Rev 2.7 Adept Runtime Rev 2.16 Adept Applicatin Rev 2.4.2 Copytight (c) 2010 Loading board information... Initializing Scan Chain... Board information loaded. Initialization Failed. Is there a way to debug this problem? Adding --vebose to djtgcfg makes no difference on the output. Thanks in advance, Marcelo.
  3. Is there anyone that has a direct link to download just the USB drivers for the Analog Discovery II (not part of Waveforms 2015)? We are having driver issues on Windows 10. We've tried every other solution that we could find on these forums. (Manually pointing to the drivers, rebooting, reinstalling waveforms including the Adept Runtime, etc.) We are looking for JUST the drivers that someone from tech support can send us while trying to fix this problem.
  4. Hey everybody, I am ready to start learning, but I have had a really hard time with a previous board and now it seems I have a curse of doubt on my shoulders... I will not give up but I could use a boost. I just need to know what I need to do to use a Basys 3 trainer board on a 64bit windows 10 machine (step by step). I'm not in school, my friends could care less about this stuff, and the professors I have contacted have not returned my emails. Pitiful, I know, and I don't like it. Bring me some joy through your patience, Please. I'm really excited, just really tiered and underwhelmed. The last board I had offered very little support. I am glad that with diligent there appears to be a community and hope to be part of the fun and tears. Best, JMP
  5. Nexys4 DDR windows 10 USB install problems

    What usb device drivers should be installed? What are their names? Where do they come from? Xilinx? Digilent? Microsoft? Arduino? When I plug nexys4_ddr board into windows 10 computer, it installs FTDI drivers called "usb serial converter" and has two ports A and B These drivers are obviously wrong because the computer makes a sound as if the USB driver is with drawing and reattaching, over and over again. In my experience this is because the board is drawing too much power or the cable is bad. The port works fine with other devices and the cable is the one that shipped with the nexys4 ddr. Here is a youtube video of the problem with more detail:
  6. Bought a new laptop with Windows 10 downloading original Waveforms to use with Discovery 1. It failed to recognize the devise. I removed waveform program and deleted any files relating to it and downloaded the new Waveforms 2015. This opened up but I got a message indicating that there was not enough power provided to the Discovery 1 devise. I tried using all USB ports which include USB 2.0 and 3.0 but had no such luck. Is there a fix for this issue?
  7. I am a sophomore in an electrical engineering program, and I would like to know what software I need for your starter kit/boards priced between 0 and $300. The boards and software must run on Windows 10 Pro and use VHDL. Note that Xilinx (Vivado) does not work on this computer; I don’t know why. As an FYI, my school uses the BASY 3, Artix-7 FPGA. Something similar to this would be appreciated. Thanks
  8. Vivado and Windows 10 Fix

    A lot of people haven't been able to upgrade to Windows 10 because Vivado will stop working.
  9. Tried this last night. Vivado can no longer find an implementation license. Now rolling back to 8.1.. EDIT by JColvin: Note that this thread was created back in August of 2015; newer versions of Vivado (2016.1 onward at the time of writing) officially support Windows 10