WRover-Kit Attach to Ubuntu 16.04LTS VirtualBox
Posted: Tue Apr 03, 2018 7:15 pm
Hi,
I just completed my virtual box install on Windows 10. Followed instructions from Espressif for the development environment/toolchain and successfully compiled hello_world (yay!). Now the difficulties start. How to connect the devices. Googled a bunch, but no success.
1. I set up a filter for the FTDI Dual RS232-HS [0700] in the Oracle VM VirtualBox Manager (tried both USB 2.0 and USB 3.0)
2. Start the VirtualBox (Linux Ubuntu 16.04LTS).
3. Plug in the Espressif ESP32 DevKit WRover (v3)
4. Go to the Devices menu entry for my running VirtualBox and try to select one of the FTDI interfaces.
5. No joy. Just a "Failed to attach the USB device FTDI..... to the virtual machine UbuntuBox"
6. The reason stated was that the device is busy with a previous request.
7. I checked the Control Panel..Device Manager in windows 10, and it sees the VirtualBox USB device as active and listed under Universal Serial Bus Controllers.
I decided to abandon my attempts at WSL (Windows Subsystem for Linux) since it couldn't see the JTAG stuff properly. It can only see /dev/ttyS8 etc...
What am I missing for my VirtualBox? It's my understanding that some of the users here have experienced success with this.
GJN
I just completed my virtual box install on Windows 10. Followed instructions from Espressif for the development environment/toolchain and successfully compiled hello_world (yay!). Now the difficulties start. How to connect the devices. Googled a bunch, but no success.
1. I set up a filter for the FTDI Dual RS232-HS [0700] in the Oracle VM VirtualBox Manager (tried both USB 2.0 and USB 3.0)
2. Start the VirtualBox (Linux Ubuntu 16.04LTS).
3. Plug in the Espressif ESP32 DevKit WRover (v3)
4. Go to the Devices menu entry for my running VirtualBox and try to select one of the FTDI interfaces.
5. No joy. Just a "Failed to attach the USB device FTDI..... to the virtual machine UbuntuBox"
6. The reason stated was that the device is busy with a previous request.
7. I checked the Control Panel..Device Manager in windows 10, and it sees the VirtualBox USB device as active and listed under Universal Serial Bus Controllers.
I decided to abandon my attempts at WSL (Windows Subsystem for Linux) since it couldn't see the JTAG stuff properly. It can only see /dev/ttyS8 etc...
What am I missing for my VirtualBox? It's my understanding that some of the users here have experienced success with this.
GJN