Uhd b100 usb problems - No UHD Devices Found

GNU Radio
1

usrp b100
Ubuntu 10.04.3 LTS
tried gnuradio install via script

$ uhd_find_devices
linux; GNU C++ version 4.4.3; Boost_104000; UHD_003.004.000-6795022

No UHD Devices Found

Tried manual compile and install of uhd binary driver. not working
either

dpkg -l | grep uhd
ii uhd 003.003.001 Ettus R. - USRP Hardware Driver

$ sudo lsusb
…
…
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 2500:0002 <- this is the usrp
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
…
…

$ cat /etc/udev/rules.d/uhd-usrp.rules

ACTION==“add”, BUS==“usb”, SYSFS{idVendor}==“fffe”,
SYSFS{idProduct}==“0002”, MODE:=“0666”
ACTION==“add”, BUS==“usb”, SYSFS{idVendor}==“2500”,
SYSFS{idProduct}==“0002”, MODE:=“0666”

did ldconfig , udev hup and a reboot still the same

Any ideas why the usb is not recognized?
when i unplug the usrp the Bus 001 Device 006: ID 2500:0002 goes away

2

On 12/31/2011 11:28 PM, dave k wrote:

usrp b100
Ubuntu 10.04.3 LTS
tried gnuradio install via script

$ uhd_find_devices
linux; GNU C++ version 4.4.3; Boost_104000; UHD_003.004.000-6795022

No UHD Devices Found

Does “sudo uhd_find_devices” discover a device? If so, might be a udev
issue.

Tried manual compile and install of uhd binary driver. not working either

For the manual compile, did the cmake configure verbose list B100 as a
enabled component?

-Josh

3

On Sat, Dec 31, 2011 at 11:28:07PM -0800, dave k wrote:

usrp b100
Ubuntu 10.04.3 LTS
tried gnuradio install via script

$ uhd_find_devices
linux; GNU C++ version 4.4.3; Boost_104000; UHD_003.004.000-6795022

No UHD Devices Found

First, you need to always try it twice. If the code loads my USRP1 with
firmware, it does not get found.

The USRP1 disconnects and re-connects when loaded. For some reason, my
Ubuntu 11.04 may reconnect it on a slow USB device. I have to re-plug
the USB connector without powering down the USRP1, and then check
‘dmesg’
to be sure it connected to the 2.0 port.

I do not have this problem on the FreeBSD machine so it is probably an
Ubuntu issue.

–
LRK
gr-user . ovillatx.sytes.net

4

On Tue, Jan 3, 2012 at 10:36 AM, Ben H. [email protected] wrote:

But you should not have to ‘try it twice’, unless something about your USB
driver or OS is broken.

FYI I was seeing the “try it twice” behaviour consistently with VMware;
probably because it has to reconnect the device to the VM.

5

First, you need to always try it twice. If the code loads my USRP1 with
firmware, it does not get found.

uhd_find_devices loads the firmware onto your device, at which point the
device re-enumerates and identifies. If the USB driver installed on
your
system, or the OS itself, handles re-enumeration slowly or in an
unexpected
manner, then you may get weird behavior.

But you should not have to ‘try it twice’, unless something about your
USB
driver or OS is broken.

Cheers,
Ben

6

On Tue, Jan 03, 2012 at 01:34:43PM -0500, [email protected] wrote:

My experience with a physical machine, and USRP devices is that Bens
observation is correct–the USB re-enumeration should cause zero
problems.

I have this problem with Ubuntu, I think thru my upgrades from 10.04
to 10.10 and now 11.04. It is about the device being connected by the
USB code to USB 1.1 even though it is a 2.0 device. It can happen on
boot up or re-connect. I don’t have this problem under FreeBSD but do
not have GnuRadio running UHD yet on FreeBSD. I use the UHD code when
running Ubuntu. No VM. The machine is a Dell but the price was right…

–
LRK
gr-user . ovillatx.sytes.net

7

On Tue, 3 Jan 2012 11:15:14 -0700, Matt M. wrote:

On Tue,
Jan 3, 2012 at 10:36 AM, Ben H. wrote:

But you should not
have to ‘try it twice’, unless something about your USB driver or OS is
broken.

FYI I was seeing the “try it twice” behaviour consistently
with VMware; probably because it has to reconnect the device to the
VM.

My experience with USB + VMware, through a Windows host system into
a Ubuntu VM, is that USB behaviour is bizarre and unreliable during
enumeration/reconnect.

I have to deal with this every day as an
Android developer, with various Android devices that use USB. I wouldn’t
expect the “bizarre” to improve with a USRP1/B100 in this situation.

My experience with a physical machine, and USRP devices is that Bens
observation is correct–the USB re-enumeration should cause zero
problems.

Links: