[USRP-users] USB 3.0 connection problems (USRP 205mini + ODROID XU4)

Nate Temple nate.temple at ettus.com
Wed Jul 5 20:26:05 EDT 2017


Hi Román,

I've seen previous mailing list / forum posts where users have had issues
with the XU4 USB controller. I've personally had success using the XU4 with
a B205mini, and others have as well.

Your uhd-usrp.rules file is fine to copy. However I suspect it might be a
power issue. I would suggest trying a USB3 Y cable that will allow an
additional power input to power the USRP, that may help.

Regards,
Nate Temple

On Thu, Jun 1, 2017 at 5:25 AM, Román Rodríguez Pérez via USRP-users <
usrp-users at lists.ettus.com> wrote:

> Hi,
>
>
>
> We are having connectivity problems through USB 3.0 with an USRP 205 mini.
> We have successfully tested it in a laptop, and it is our intention to
> control the USRP with a Raspberry-like mini computer. We have chosen ODROID
> XU4 because it has USB3.0 ports available, and runs Ubuntu 16.04.
>
>
>
> The problem is that uhd_find_devices command does not find the USRP when
> connected to an USB3.0 port. It does find it when connected to a USB2.0
> port and works correctly (but obviously with limited velocity).
>
>
>
> I found out in ODROID forums that many XU4 devices came with an excess of
> flux in the USB 3.0 signal pads (https://forum.odroid.com/
> viewtopic.php?f=95&t=15302) but nothing changed after cleaning with
> alcohol.
>
>
>
> When I run ldusb and ldusb –t commands, I get the following output:
>
> roman at odroid:~$ lsusb
>
> Bus 006 Device 002: ID 0bda:8153 Realtek Semiconductor Corp.
>
> Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>
> 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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> roman at odroid:~$ lsusb -t
>
> /:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
>
>     |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152,
> 5000M
>
> /:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
>
> /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
>
> /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
>
> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M
>
> /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M
>
> roman at odroid:~$ uhd_find_devices
>
> linux; GNU C++ version 5.3.1 20151219; Boost_105800;
> UHD_003.009.002-0-unknown
>
>
>
> No UHD Devices Found
>
>
>
>
>
> On the other hand, I found this stackoverflow thread where Marcus Müller
> answered (https://stackoverflow.com/questions/33304828/when-
> trying-to-use-my-usrp-in-gnu-radio-i-get-a-no-devices-found-for), which
> states that “Some USB3 host controllers don't behave standards-conforming,
> and connectivity cannot be achieved. If your USRP is detected when plugged
> into a USB2 port (anyone that isn't blue, usually), you should be fine.”
>
>
>
> I also found this thread from this very same mailing list (http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2015-June/014598.html) which states that “*there are USB-3.0 controllers that simply won't work with any FX3-based device, like the B210”. *ODROID user manual suggests that the USB 3.0 controller is a Genesys GL3521 , which I don’t know it it is compatible with USRP 205mini.
>
>
>
> Finally, following the instructions of the USRP manual (http://files.ettus.com/manual/page_transport.html#transport_usb) , I looked for uhd-usrp.rules file in /etc/udev/rules.d/, but did not find it. I tried copying the one at my Ubuntu laptop were I tested the USRP, which contains the following information:
>
>
>
> #USRP1
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="fffe", ATTRS{idProduct}=="0002",
> MODE:="0666"
>
>
>
> #B100
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="2500", ATTRS{idProduct}=="0002",
> MODE:="0666"
>
>
>
> #B200
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="2500", ATTRS{idProduct}=="0020",
> MODE:="0666"
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="2500", ATTRS{idProduct}=="0021",
> MODE:="0666"
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="2500", ATTRS{idProduct}=="0022",
> MODE:="0666"
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="3923", ATTRS{idProduct}=="7813",
> MODE:="0666"
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="3923", ATTRS{idProduct}=="7814",
> MODE:="0666"
>
>
>
> Nevermind, it did not work either.
>
>
>
> Any suggestion of how to proceed?
>
> Best regards
>
> P Please consider the environment before printing this e-mail.
>
> ------------------------------
> This message including any attachments may contain confidential
> information, according to our Information Security Management System, and
> intended solely for a specific individual to whom they are addressed. Any
> unauthorised copy, disclosure or distribution of this message is strictly
> forbidden. If you have received this transmission in error, please notify
> the sender immediately and delete it. Thank you.
> ------------------------------
> Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> contener información clasificada por su emisor como confidencial en el
> marco de su Sistema de Gestión de Seguridad de la Información siendo para
> uso exclusivo del destinatario, quedando prohibida su divulgación copia o
> distribución a terceros sin la autorización expresa del remitente. Si Vd.
> ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y
> proceda a su borrado. Gracias por su colaboración.
> ------------------------------
> Esta mensagem, incluindo qualquer ficheiro anexo, pode conter informação
> confidencial, de acordo com nosso Sistema de Gestão de Segurança da
> Informação, sendo para uso exclusivo do destinatário e estando proibida a
> sua divulgação, cópia ou distribuição a terceiros sem autorização expressa
> do remetente da mesma. Se recebeu esta mensagem por engano, por favor avise
> de imediato o remetente e apague-a. Obrigado pela sua colaboração.
> ------------------------------
>
>
> _______________________________________________
> USRP-users mailing list
> USRP-users at lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20170705/492a2a40/attachment-0002.html>


More information about the USRP-users mailing list