Hi Rodolphe - the implicit assumption is you don't any other USB devices plugged into the computer - other then the keyboard and the mouse.
And the Linux OS is running on bare metal and not running in a VM. Assuming the above is true, then to get from the USRP into the computer, you need to confirm that both the USB3 port is working and the USB3 wire is working. You've confirmed the USB3 port is working correctly, but you haven't confirmed the USB3 wire is working correctly. Also, if a connected device is sensed to be a low speed USB2 device, then it's unlikely the USB2 device is going to be using the high speed USB3 bus. -- Cinaed On 3/20/20 1:17 AM, Rodolphe Bertolini wrote: > Hello Cinaed, > > During the tests I use a USB 3.0 stick that behaves same as the USRP : > with an other computer, both are well recognized as 3.0, but not in > the erroneous machine. I don't think that neither USB stick, neither > USRP USB cable are faulty. > > The output for both USB stickand USRP gives is: > bcdUSB 2.10 > > Also for both : > Device can operate at SuperSpeed (5Gbps) > > USB ports are on bus 1. > However, something strange : when USB stick is plugged in (bus 1) at > boot time, it is often detected in bus 2 as SuperSpeed (so as 3.0), > then it is also detected in bus 1, and finally disconnected from bus > 2. I don't touch it during those 3 steps that span over half a second. > > I am completely lost. > > Thank you ! > Regards, > Rodolphe > > Le jeu. 19 mars 2020 à 20:15, Cinaed Simson <[email protected] > <mailto:[email protected]>> a écrit : > > Hi Rodolphe - you need to type > > lsusb > > and find your USRP device ID. > > For instance, for my HackRF lsusb indicates it's ID is: > > Bus 003 Device 003: ID 1d50:6089 OpenMoko, Inc. Great Scott > Gadgets HackRF One SDR > > Then I would type > > lsusb -v -d 1d50:6089 > > Once you have the output for you USRP device, look for the entry > > bcdUSB > > My HackRF has USB2 interface but it's plugged into a USB3 port and > lsusb indicates > > bcdUSB 2 > > It the problem persists, you may have to swap out the cable - it > could be a cable problem. > > -- Cinaed > > On 3/19/20 1:06 AM, Rodolphe Bertolini wrote: >> Cinaed, >> >> Thank you. >> Output is empty (except at FIXME warning : "FIXME: alloc bigger >> buffer for device capability descriptors"). >> However, without filtering I have something like this : >> >> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >> Device Descriptor: >> bLength 18 >> bDescriptorType 1 >> bcdUSB 3.10 >> ... >> bInterfaceProtocol 0 Full speed (or root) hub >> >> I think that this bus is USB 3.0 capable, but for some reason the >> "superspeed" is not activated. >> Also no information about data rate is given about this bus. >> >> Regards, >> Rodolphe >> >> Le mer. 18 mars 2020 à 20:29, Cinaed Simson via USRP-users >> <[email protected] <mailto:[email protected]>> >> a écrit : >> >> A USB3 port is SuperSpeed port. >> >> For a quick check, try >> >> lsusb -v | grep 5Gbps >> >> to confirm you have at least 1 working USB3 port. >> >> And then you can check the port speed where the device is >> connected using lsusb -v. >> >> -- Cinaed >> >> >> >> On 3/18/20 7:36 AM, Rodolphe Bertolini via USRP-users wrote: >>> Marcus, >>> USB plug is rotated (from row is at top), but yes I get the >>> exact same port as your. >>> Thank you >>> Regards, >>> Rodolphe >>> >>> Le mer. 18 mars 2020 à 16:20, Marcus Müller via USRP-users >>> <[email protected] >>> <mailto:[email protected]>> a écrit : >>> >>> Hi Rodolphe, >>> >>> considering this is as confusing to me as to you: I took >>> a picture of my >>> USB3 port. When looking at an oblique angle at yours, do >>> you see the >>> five front-row bronze/gold contacts shown in the >>> attached photo? >>> >>> Best regards, >>> Marcus >>> >>> On 18.03.20 14:33, Rodolphe Bertolini via USRP-users wrote: >>> > Thanks to both of you. >>> > >>> > The port is black, but it has been working for few >>> months until I >>> > shutdown / change session (I can't log back to >>> previous session for >>> > reasons) so I believe that the port by itself isn't >>> the bad guy. >>> > >>> > It keeps appearing as USB 2 ("high-speed") when I plug >>> it and also when >>> > I run uhd_find_devices >>> > >>> > @Cedric I made sure to plug at max both ends >>> > >>> > Thank you again >>> > Regards, >>> > Rodolphe >>> > >>> > Le mer. 18 mars 2020 à 15:02, Cedric Roux via USRP-users >>> > <[email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] >>> <mailto:[email protected]>>> a écrit : >>> > >>> > Hi, >>> > >>> > be also sure to plug the cable firmly on both >>> > ends. I've seen it more than once with a cable >>> > "half-plugged" and then it becomes usb2, not usb3. >>> > >>> > My 2 cents. >>> > >>> > Regards, >>> > Cédric. >>> > >>> > On 3/18/20 2:54 PM, Marcus Müller via USRP-users >>> wrote: >>> > > Hi Rodolphe, >>> > > >>> > > first of all, check whether you're actually >>> dealing with a USB3 >>> > port. I >>> > > know, sounds strange, but if it's not blue and >>> doesn't have more than >>> > > four visible contacts, it's not >>> standard-compliant USB3. The fact that >>> > > it's attached to a xHCI doesn't itself mean it >>> can do USB3. >>> > > >>> > > Then, I can't quite remember whether the USB >>> controller on the B200 >>> > > would even register as USB3 before the initial >>> firmware is loaded. Try >>> > > the following: In one terminal window, run >>> `dmesg -Hwx`. Plug in the >>> > > USRP, and see how it appears on the bus (it >>> seems, as USB2 high-speed >>> > > device). After that, in another terminal, you'd run >>> > `uhd_find_devices`, >>> > > and see whether the device re-enumerates as USB3 >>> SuperSpeed device. >>> > > >>> > > Best regards, >>> > > Marcus >>> > > >>> > > On 18.03.20 13:43, Rodolphe Bertolini via >>> USRP-users wrote: >>> > >> Hello Ron, (I resend the email, I forgot to >>> "reply to all") >>> > >> Thank you for your quick feedback. >>> > >> >>> > >> Ok I understand. More information, lspci gives me : >>> > >> 00:14.0 USB controller: Intel Corporation >>> Cannon Lake PCH USB 3.1 >>> > xHCI >>> > >> Host Controller (rev 10) >>> > >> So I don't get why doesn't Ubuntu enables USB >>> 3.0 with the B210. >>> > >> >>> > >> My problems looks like this one >>> > >> >>> > >>> >>> http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2018-July/057323.html >>> > >> >>> > >> The output of lsusb -t is similar, with >>> "Driver=(none)" >>> > >> A message of above mentioned thread suggests to >>> enable 3.0 option in >>> > >> BIOS, however I don't have such option. And >>> even if I had, I >>> > didn't not >>> > >> change anything between reboot / session switch >>> so I really don't >>> > >> understand where this regression is coming from. >>> > >> Also I did the "solution" mentioned by the author : >>> > >> >>> > >> uhd_image_loader --args="type=b200,reset" >>> > >> >>> > >> >>> > >> Which did not improve the situation. >>> > >> >>> > >> >>> > >> Thank you again >>> > >> >>> > >> Rodolphe >>> > >> >>> > >> Le mer. 18 mars 2020 à 12:02, Ron Economos via >>> USRP-users >>> > >> <[email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] >>> <mailto:[email protected]>> >>> > <mailto:[email protected] >>> <mailto:[email protected]> >>> > <mailto:[email protected] >>> <mailto:[email protected]>>>> a écrit : >>> > >> >>> > >> dmesg should say "new SuperSpeed USB device >>> number X using >>> > xhci_hcd" >>> > >> or "new SuperSpeed Gen 1 USB device number >>> X using xhci_hcd" >>> > if you >>> > >> have a newer kernel. >>> > >> >>> > >> "high-speed" means USB 2.0. >>> > >> >>> > >> Ron >>> > >> >>> > >> On 3/18/20 03:41, Rodolphe Bertolini via >>> USRP-users wrote: >>> > >>> Dear all, >>> > >>> >>> > >>> I have been using a USRP B210 on a laptop >>> for months now. For >>> > >>> reasons, I switched to another Linux >>> session, and using this >>> > >>> session UHD fails to talk to B210 over USB 3.0 >>> > >>> >>> > >>> dmesg tells me it is using the xhci_hcd >>> driver (which I >>> > believe is >>> > >>> the driver for USB 3.0), and is also >>> mentioning "new high-speed >>> > >>> USB", which leads me to think that USB 3.0 >>> link is well >>> > recognized >>> > >>> and active: >>> > >>> >>> > >>> [ 306.133028] usb 1-1: new high-speed USB >>> device number 16 >>> > using >>> > >>> xhci_hcd >>> > >>> [ 306.260349] usb 1-1: New USB device >>> found, idVendor=2500, >>> > >>> idProduct=0020 >>> > >>> [ 306.260351] usb 1-1: New USB device >>> strings: Mfr=1, >>> > Product=2, >>> > >>> SerialNumber=3 >>> > >>> [ 306.260352] usb 1-1: Product: USRP B200 >>> > >>> [ 306.260354] usb 1-1: Manufacturer: >>> Ettus Research LLC >>> > >>> [ 306.260355] usb 1-1: SerialNumber: 31B9289 >>> > >>> >>> > >>> However, when running any uhd command >>> line, it fails using >>> > USB 3.0: >>> > >>> >>> > >>> [INFO] [UHD] linux; GNU C++ version 5.4.0 >>> 20160609; >>> > Boost_105800; >>> > >>> UHD_3.15.0.0-release >>> > >>> [INFO] [B200] Detected Device: B210 >>> > >>> [INFO] [B200] Operating over USB 2. >>> > >>> >>> > >>> I have also tried with UHD 3.14.1, no >>> improvement. >>> > >>> >>> > >>> I remember having a similar issue (maybe >>> the same?) that had >>> > been >>> > >>> solved with something related to udev, but >>> I sadly didn't >>> > take any >>> > >>> note of this. >>> > >>> >>> > >>> Do you have any hint? >>> > >>> >>> > >>> Thank you. >>> > >>> Regards, >>> > >>> Rodolphe >>> > >>> >>> > >>> >>> _______________________________________________ >>> > >>> USRP-users mailing list >>> > >>> [email protected] >>> <mailto:[email protected]> >>> > <mailto:[email protected] >>> <mailto:[email protected]>> >>> > <mailto:[email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] >>> <mailto:[email protected]>>> >>> > >>> >>> > >>> >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> > >> _______________________________________________ >>> > >> USRP-users mailing list >>> > >> [email protected] >>> <mailto:[email protected]> >>> > <mailto:[email protected] >>> <mailto:[email protected]>> >>> > <mailto:[email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] >>> <mailto:[email protected]>>> >>> > >> >>> > >>> >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> > >> >>> > >> >>> > >> _______________________________________________ >>> > >> USRP-users mailing list >>> > >> [email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] >>> <mailto:[email protected]>> >>> > >> >>> >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> > >> >>> > > >>> > > _______________________________________________ >>> > > USRP-users mailing list >>> > > [email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] >>> <mailto:[email protected]>> >>> > > >>> >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> > > >>> > >>> > >>> > _______________________________________________ >>> > USRP-users mailing list >>> > [email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected] >>> <mailto:[email protected]>> >>> > >>> >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> > >>> > >>> > _______________________________________________ >>> > USRP-users mailing list >>> > [email protected] >>> <mailto:[email protected]> >>> > >>> >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> > >>> _______________________________________________ >>> USRP-users mailing list >>> [email protected] >>> <mailto:[email protected]> >>> >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> >>> >>> _______________________________________________ >>> USRP-users mailing list >>> [email protected] <mailto:[email protected]> >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >> _______________________________________________ >> USRP-users mailing list >> [email protected] <mailto:[email protected]> >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
