I’m having problems with the LimeSDR under USB3 on Linux and Windows 10. At the moment I’m limited to 10Mhz for widows and 12Mhz for Linux using USB2. It looks like a USB initialization problem. I’m seeing the following in my system logs under Linux:
[ 3274.394280] usb 6-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 3274.411852] usb 6-2: LPM exit latency is zeroed, disabling LPM.
[ 3274.412853] usb 6-2: New USB device found, idVendor=1d50, idProduct=6108
[ 3274.412857] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3274.412860] usb 6-2: Product: LimeSDR-USB
[ 3274.412862] usb 6-2: Manufacturer: Myriad-RF
[ 3274.412864] usb 6-2: SerialNumber: 0009060B00462017
[ 3275.498919] usb 5-2: new high-speed USB device number 2 using xhci_hcd
[ 3275.700776] usb 5-2: New USB device found, idVendor=1d50, idProduct=6108
[ 3275.700780] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3275.700783] usb 5-2: Product: LimeSDR-USB
[ 3275.700785] usb 5-2: Manufacturer: Myriad-RF
[ 3275.700787] usb 5-2: SerialNumber: 0009060B00462017
[ 3279.612425] usb 6-2: can't set config #1, error -110
What is odd here is the double registering of the divice for usb 6-2 and 5-2, and the error -110 at the end. Assuming the error code is a standard error value, that would be ETIMEDOUT.
The PC I’m using should be able to more than handle much wider bandwidth than 12Mhz of USB2. I just need to get the card recognized.
For Windows, I’m assuming that you installed the Cypress drivers for USB 3.0 support, right? Also, recheck using LimeSuiteGUI and perform the Connect, and then use the Device Info feature from the modules to see if your Lime is running USB 3.0 or not (you can also do this from Linux using LimeSuiteGUI, too). If you only see USB 2.0, then you’re either plugged into a USB 2.0 port (no offense, it’s happened to me A LOT) or you have no USB 3.0 resources that the Lime can see. Just reload the driver for USB 3.0 and see if it corrects itself.
None taken Marty, I appreciate the reminder. Fortunately, the ports on the front of my PC were easily separated since I built the machine myself. Unfortunately, if I plug into either USB3 plug I get the same response.
Is there a known good URL to pull the latest Cypress driver from? What are you using?
@hTo137 The only USB3 cables I have are the supplied cables that came with my two LimeSDR boards and my wife’s cable that came with her Samsung G-6. I get the same behavior out of both boards using all of the cables.
This is odd. I’m seeing two devices when plugged into the USB3 port for ID 1d50:6108 (OpenMoko, Inc.). This jives with the system log. Both ports in the log show as xhci_hcd, which they should, but why two? Would someone with a Linux box confirm they are seeing the same in the logs and with ‘lsusb’?
Bus 002 Device 010: ID 0738:a215 Mad Catz, Inc.
Bus 002 Device 009: ID 0738:2215 Mad Catz, Inc.
Bus 002 Device 008: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 002 Device 007: ID 046d:082c Logitech, Inc.
Bus 002 Device 006: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver
Bus 002 Device 005: ID 0955:0007 NVidia Corp.
Bus 002 Device 004: ID 046d:c32b Logitech, Inc.
Bus 002 Device 003: ID 046d:c06b Logitech, Inc. G700 Wireless Gaming Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 005: ID 1d50:6108 OpenMoko, Inc. <---------
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 007: ID 1d50:6108 OpenMoko, Inc. <---------
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 03f0:ba02 Hewlett-Packard PhotoSmart 8100 series
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 007: ID 0b05:179c ASUSTek Computer, Inc.
Bus 001 Device 006: ID 046d:0a29 Logitech, Inc. H600 [Wireless Headset]
Bus 001 Device 005: ID 046d:c531 Logitech, Inc. C-U0007 [Unifying Receiver]
Bus 001 Device 003: ID 0fde:050a Oregon Scientific
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I’m running on an Asus Rampage IV Extreme. At the time it was one of the first very high end overclocking motherboards that had USB 3. It could be it was too early with USB 3. This is the first USB3 device that I have used that has not been recognized.
I noticed in the ‘lsusb -t’ output that earliest device (assuming the numbering increments) is seen as a USB 3.0 device (the bcdUSB value) while some of the fields are marked as “(error)” - specifically iManufacturer, iProduct, and iSerial. I wonder if it fails to be enumerated correctly (the error -110 - ETIMEOUT), and then retries as a USB 2 device. The second device does show bcdUSB as 2.10 and finds all the fields that failed before.
I assume the Cypress chip handles the USB handshaking, and I would have to look at the code there for the cause of the timeout. I’m wondering if I can resolve the timeout or increase the timeout length in the xhci_hcd driver.
@n5fpp could well be. I lost a lot of time trying to debug issues when using an older Thinkpad which was probably one of the first to have USB 3.0, which simply went away when I used more recent hardware.
@andrewback, as an alternative I have one of the PCIx USB boards that @SimonG4ELI pointed out above ordered, it should be here by the end of the week. Hopefully that resolves the problem without digging into code.
@SimonG4ELI I got my USB3 card in the mail today. It appears to be working. Below are the best settings I could get to work with gqrx. Anyone using anything different with gqrx?
@csete, Below is the output from htop on my 12 core hyperthreaded PC. The loads look a bit high, and I’m surprised to see so many gqrx processes running. Is this normal? This is with the settings above.
