Search the Community

Showing results for tags 'virtualbox'.



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
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. 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.
  2. Hi FPGA gurus ! I am facing trouble while trying to attach my Atlys USB JTAG device to a Centos 6 virtualbox VM. I recently had no choice but to upgrade my computer from Windows 7 to Windows 10. As a Windows 10 version of ISE 14.7 was available, I decided I could do the upgrade before realizing that ISE 14.7 for Windows 10 was indeed ISE 14.7 for Linux running a VirtualBox... Nevermind. The problem is that it seems I can't attach Digilent USB JTAG to the VirtualBox. Here is my configuration : Windows 10 Pro VirtualBox 5.2.8 (I upgraded it so that I could install Extensions to enable USB 2 and USB 3 support) Adept2 is installed on Windows 10 and works fine, Atlys board is recognized and I can run the test application OK. Now, here is my problem : Let's turn on the computer first and do a fresh test ! Atlys Board is attached to USB ports (JTAG and UART) but is turned off. VirtualBox USB configuration is configured as shown in USB_parameters.jpg Now, let's turn VM on, Atlys board still off. The attachable USB device list in VB is shown in USB_devices_atlys_off.jpg As you can see, neither JTAG nor UART devices are listed, which is expected as Atlys board is off. Now, let's turn the Atlys board on and see if the listing has changed... It has ! as shown in USB_devices_atlys_on_1.jpg Also, you can see in Device_mgr.jpg that Windows has no driver problem with JTAG and UART devices. You may notice UART device is automatically attached. Looking at /dev/tty* shows that the UART device is now available through /dev/ttyACM0 as shown in TTY_devices.jpg Let's have a look at the JTAG device status (USB_devices_atlys_on_2.jpg), it reads "captured", whatever that means ... Now, let's try attaching it... It raises an error with message shown in Digilent_USB_JTAG_attachment_error.jpg "USB device is busy with a previous request" :/ This is sad ... Of course, no other device appears in /dev/tty* Greping dmesg for FTDI pattern returns Nothing. Only UART USB devices appears in dmesg log... I've tried the same test with USB 3 (xHCI) configuration selected. Do any of you have an idea on how I could attach the USB Digilent JTAG device to my Centos 6 VirtualBox machine ? Any help will be highly appreciated. Thanx a lot. Cheers
  3. Hi, I want to connect my zedboard to virtual machine (Ubuntu 16.04 64 bit in VirtualBox). When i try to connect throught XMD console to zedboard, it appears that the cable is not connected. Can anyone help me with some hints or advices ?
  4. Count0

    Moving to Linux

    Hi all, i'm moving my development environment to Ubuntu. Last things I'm struggling with are Xilinx WebISE and the JTAG-HS3 programmer. All worked fine under W7pro. But WebISE performs traumatically on Ubuntu. WebISE was designed to run on RedHat and SUSE but it runs there far from flawless. So I put up a W7 in VirtualBox on Ubuntu and got WebISE running fine again. But when forwarding the JTAG-HS3 to the VM, the VM got killed immediately. I can live with this situation if I knew how to operate JTAG-HS3 on Linux, to upload a bitstream to my FPGA. So my questions boil down to: Where can I find a user manual about how to use the Adept software for Linux. I haven't found it on the Digilent website?Does anyone know how to stop VirtualBox VM's crashing when connected to a JTAG-HS3 programmer? Thanks in advance
  5. Hi all. I just installed Ubuntu Gnome 14.04 on my notebook (all my life I used Windows). I installed VirutalBox on my PC and Windows 8.1 x64 on it. The problem is that I installed the Waveforms on the virtual machine and when I tried to use it, my analog doesn't measure well. I compared the same measure with a PC running Windows from the HDD and the Analog Discovery works fine. I don't know what happened. If anyone has any suggestion I would really appreciate it. Besides, is there a version of WaveForms for Linux (Ubuntu)? Thank you for your time