Forums › BB Series Discussions › Connecting BB60C to a Ubuntu Virtualbox
- This topic has 3 replies, 2 voices, and was last updated 1 week, 4 days ago by Andrew.
KYoungParticipantKYoung March 17, 2023 at 10:00 am
I’m running a Windows 10 host and trying to get my BB60C to connect to an Ubuntu VM, but can’t get the USB to connect.
The BB60C shows up as “Signal Hound BB60C-2” in the windows device manager, but shows up as “Cypres FX3” in VirtualBox.
Trying to pass the USB from the Windows Host to the Linux Guest fails every time. The USB attempts to connect, then immediately disconnects and returns to Windows.
Any help would be appreciated.
AndrewModeratorAndrew March 17, 2023 at 10:28 am
We have had success with VMWare products, such as VMWorkstation. In the VMWare products you have to enable high speed USB in the settings to control our products (or at least is used to be that way).
We have not used Oracle VMs before, nor have I heard of customer using them. I would say most customers have issues when running our products in VMs, and it’s almost always USB related.
I would recommend running native if possible, or trying VMWare if possible.
KYoungParticipantKYoung March 17, 2023 at 10:48 am
Yes, definitely some kind of USB problem.
In VirtualBox high-speed USB is enabled by installing the VIrtualBox Extension Pack and Guest Additions. Those, along with enabling the USB 3.0 (xHCI) Controller are ‘supposed’ to allow you control USB 3.0 devices.
I don’t know where this is going wrong, but I do see that Cypres FX3 device makes the BB60 LED blink red. So it is attempting to connect, but for some reason can’t hold on to it.
AndrewModeratorAndrew March 17, 2023 at 11:34 am
We are using the Cypress Fx3 chip, so showing up as a Cypress Fx3 device might be fine. We just use the default libusb library on Linux, so I’m not sure we’d show up as a BB60C anyways.
If you are blinking red when idling, then the firmware on the BB60 is power cycling the device because it wasn’t able to establish/enumerate as USB 3.0. We see this when customers connect the device to a USB 2.0 port, or use 2.0 cables, hubs, etc. Is there anything you can troubleshoot in this regard? It should be solid green when connected and idle.
You must be logged in to reply to this topic.