[USRP-users] USRP B210 Sometimes Not Appearing with lsusb
dwwkelly at gmail.com
Mon Jul 20 11:30:01 EDT 2015
I upgraded from 3.13 to 3.16 and that seemed to do the trick. Here's the
output from lspci -v for the USB controller just for reference.
00:14.0 USB controller: Intel Corporation ValleyView USB xHCI Host
Controller (rev 0c) (prog-if 30 [XHCI])
Subsystem: Intel Corporation Device 2056
Flags: bus master, medium devsel, latency 0, IRQ 103
Memory at d0700000 (64-bit, non-prefetchable) [size=64K]
Capabilities:  Power Management version 2
Capabilities:  MSI: Enable+ Count=1/8 Maskable- 64bit+
Kernel driver in use: xhci_hcd
On Wed, Jul 15, 2015 at 1:25 PM, Neel Pandeya <neel.pandeya at ettus.com>
> Hello Devin:
> Which USB controller are you using on this Intel Atom NUC single board
> It would probably be worth trying a kernel upgrade, and see if that helps.
> On 14 July 2015 at 19:21, devin kelly via USRP-users <
> usrp-users at lists.ettus.com> wrote:
>> I have several Intel NUC single board computers (the Atom based ones).
>> Sometimes I'll reboot them with my USRP B210 plugged in or just unplug and
>> plug in the USRP and the USRP will still behave as if it's unplugged.
>> There won't be any log messages in dmesg and lsusb won't find the USRP.
>> I have the right udev rules installed and un-plugging and replugging the
>> USRP (including the power supply) back in always seems to work. Once lsusb
>> can find the USRP everything works fine.
>> It seems like if we plug in the USB first and then the external power
>> supply the USRP comes up fine, when we swap the order it's not as reliable.
>> We have an external power supply that is at 5.6 V but gets loaded down to
>> 5.3 V with the USRP plugged in. After looking at the schematic it seems
>> like 5V should be fine.
>> Has anyone had any issue like this? How should we start debugging?
>> USRP-users mailing list
>> USRP-users at lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the USRP-users