In such cases I tend to hard-wire the 5V pin of the USB connector, and the issues usually are gone - when the external power supply is strong enough. The USB port may originally be connected to the internal power distribution of the PCB and cause hick-ups from high power drain...
Ralph. > -----Original Message----- > From: USRP-users [mailto:[email protected]] On Behalf Of > Nate Temple via USRP-users > Sent: Saturday, September 2, 2017 11:03 PM > To: David > Cc: [email protected] > Subject: Re: [USRP-users] B200mini & XU4 problem > > Hi Dave, > > This is certainly an interesting issue. I suspect the core of the issue may be > power draw on the USB interface during boot. One of the common issues with > the XU4 that I've seen reported is that the USB3 ports do not provide USB3 spec > power levels. > > Using a powered USB3 hub may resolve the issue. > > Another option would be a Y power cable such as this > http://www.ebay.com/itm/262045046196 which would allow you to use an > external power adapter to feed power to the USRP. > > Another test you could try -- Try using the USB2 on the XU4. Does it result in the > same boot up problems? > > I have a early rev 0.1 20151201 XU4 that I often use paired with a B205mini > and have not seen any issue such as this. > > Regards, > Nate Temple > > > > > > On Sep 2, 2017, at 1:44 AM, David via USRP-users <usrp- > [email protected]> wrote: > > > > Hi All, > > > > I'm trying to get XU4 and B200mini to work together, but having a serious > issue: the SD card gets trashed! > > > > I'm using Ubuntu 16.04 image from the Odroid site, kernel 4.9.28-38, and > latest GIT clone of UHD (as of two weeks ago). Two uSD cards I had are now > totally trashed. I'm on my last card. They seem to get totally trashed after I run > uhd-fft a few times. > > > > The main symptom is that if the B200mini is connected and I reboot, an fsck > is done every time, and also has the effect of continually rebooting, and > continually corrupting the card. > > > > Unplug the B200mini and all is fine (after a couple of fscks). I managed to > work out that if I remove the udev rule that starts up UHD (uhd-usrp.rules) I am > also able to reboot with no issues. So a driver issue? > > > > Without the udev rule I get the following, which I'm assuming is normal?: > > > > [ 24.555119] usb 3-1.1: device descriptor read/64, error -110 > > [ 29.995114] usb 3-1.1: device descriptor read/64, error -110 > > [ 45.675119] usb 3-1.1: device descriptor read/64, error -110 > > [ 56.685085] usb 3-1.1: device not accepting address 5, error -62 > > [ 67.565082] usb 3-1.1: device not accepting address 6, error -62 > > [ 67.569976] usb 3-1-port1: unable to enumerate USB device > > > > Hope you can help, thanks, > > > > Dave. > > > > > > _______________________________________________ > > USRP-users mailing list > > [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 _______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
