Thanks All,
So on USB2 I get the following:
odroid@odroid:~$ uhd_fft -f 935e6 -s 1e6
linux; GNU C++ version 5.4.0 20160609; Boost_105800;
UHD_003.010.002.000-0-gbd6e21dc
-- Detected Device: B200mini
-- Operating over USB 2.
-- Initialize CODEC control...
-- Initialize Radio control...
-- Performing register loopback test... pass
-- Performing CODEC loopback test... pass
-- Setting master clock rate selection to 'automatic'.
-- Asking for clock rate 16.000000 MHz...
-- Actually got clock rate 16.000000 MHz.
-- Performing timer loopback test... pass
-- Asking for clock rate 32.000000 MHz...
-- Actually got clock rate 32.000000 MHz.
-- Performing timer loopback test... pass
UHD Error:
An unexpected exception was caught in a task loop.
The task loop will now exit, things may not work.
EnvironmentError: IOError: usb rx8 transfer status:
LIBUSB_TRANSFER_NO_DEVICE
terminate called after throwing an instance of 'uhd::usb_error'
what(): RuntimeError: USBError -4: usb tx4 submit failed:
LIBUSB_ERROR_NO_DEVICE
Aborted
and the GUI appears for a fraction of a second. However, running the
following causes no errors:
odroid@odroid:~$ uhd_rx_cfile -r 1e6 -f 935e6 blob.raw
linux; GNU C++ version 5.4.0 20160609; Boost_105800;
UHD_003.010.002.000-0-gbd6e21dc
-- Detected Device: B200mini
-- Operating over USB 2.
-- Initialize CODEC control...
-- Initialize Radio control...
-- Performing register loopback test... pass
-- Performing CODEC loopback test... pass
-- Setting master clock rate selection to 'automatic'.
-- Asking for clock rate 16.000000 MHz...
-- Actually got clock rate 16.000000 MHz.
-- Performing timer loopback test... pass
-- Asking for clock rate 32.000000 MHz...
-- Actually got clock rate 32.000000 MHz.
-- Performing timer loopback test... pass
[UHD_RX] Defaulting to mid-point gains:
[UHD_RX] Channel 0 gain: 38.0 dB
^Codroid@odroid:~$
odroid@odroid:~$
odroid@odroid:~$ ls -ltr
total 31212
drwxrwxr-x 8 odroid odroid 4096 Aug 20 14:17 uhd
drwxrwxr-x 33 odroid odroid 4096 Aug 25 15:59 gnuradio
-rw-rw-r-- 1 odroid odroid 31951808 Sep 4 16:05 blob.raw
I'll get the Y-cable Nate suggested, probably a beefier PSU too, and go
from there...
Thanks All,
Dave
On 03/09/17 22:45, Nate Temple wrote:
Hi Dave,
What is the error when uhd_fft fails over the USB2 port?
The routing is different between the USB2 and USB3 ports on the XU4. The USB3
ports are routed through a USB3 hub (GL3521) and also have a RTL8153 1GbE
ethernet controller on the #1 channel. They also provide their own bus power
through the NCP380HM switch. I don't know where the issue is at with the XU4
power via the USB3 ports, but any of these could be the culprit. I know Odroid
will recommend a powered hub for USB3 devices that don't have an external power
option. The schematics will show all the details:
https://dn.odroid.com/5422/ODROID-XU4/Schematics/
Regards,
Nate Temple
On Sep 3, 2017, at 5:46 AM, David via USRP-users <usrp-users@lists.ettus.com>
wrote:
Hey all,
Thanks for the replies, didn't realise it would work on USB2... so I...
- plugged into USB2 port
- no boot up problems with the udev rule enabled
- get similar device read errors, until the device is unplugged & plugged back
in
- then uhd_usrp_probe works, no corruption of the fs :-)
- takes much longer to load fw!
- can't run uhd_fft however (...LIBUSB_ERROR_NO_DEVICE...)
So using USB2 port seems OK, but need to unplug, plug in the device after each
reboot, can do a
uhd_usrp_probe with no issues, and reboot OK, but uhd_fft fails (is that
expected?).
Why the difference between USB2 and USB3, thought the power (500mA) was the
same?
I've been wondering about power, esp. since reading the odroid forums, I think,
as you say Nate, a powered hub, or Y adaptor (I didn't know about that) is the
next step...
Marcus, is there a location for the Arch image please? I saw a previous post
from you about using b2x0's with XU4... :-)
Many Thanks,
Dave
On 02/09/17 23:30, Marcus D. Leech via USRP-users wrote:
On 09/02/2017 05:02 PM, Nate Temple via USRP-users wrote:
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-users@lists.ettus.com>
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.
I run a *PAIR* of b205-minis on an Odroid XU4, but I use an external, powered,
USB-3.0 hub. I don't recall ever having a filesystem trashing problem, but
I use an Arch image.
Modulo kernel bugs, there's no way for UHD applications or hardware to "trash your
filesystem". So, if this is an issue, then the issue is with the
underlying OS+drivers implementation. None of the UHD code runs in kernel
space, and runs as an ordinary user.
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
