Unfortunately, for me, things are not as they seem...
So after using the B200mini on USB2, just now, I've just done a reboot
(paranoia setting in), and it's now stuck continuously rebooting, doing
an fsck rebooting, etc...
One one pass...
2fsck 1.42.13 (17-May-2015)
rootfs was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
[ 9.412622] random: crng init done=================== \
82.8%
rootfs: |================================================= |
87.4%
On Another:
Pass 2: Checking directory structure
[ 9.876457] random: crng init done===================== \
86.6%
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs: 124553/237568 files (0.4% non-contiguous), 783269/920192
blocks
fsck exited with status code 1
done.
[ 10.858006] EXT4-fs (mmcblk1p2): mounted filesystem without
journal. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
I've just unplug the b200mini, and it is still continuing to reboot and
check the fs, that's new, maybe more than one issue here?
I stop the reboot by hitting enter twice at the boot prompt (keeping my
finger on Enter!).
I power-cycle and it still reboots.
I suspect the flag that sets the rootfs as un-cleanly umounted is set
and won't re-set, as the fsck never appears to complete, the fsck seems
to get as far as 86% then a reboot occurs.
So I've now unplugged the SD card (assuming it's safe to do so at the
boot prompt) and plugged it into my main PC. Not recognised!
fdisk -l shows nothing.
Plug it back into the XU4 and ...
Exynos5422 # boot
there are pending interrupts 0x00000001
[ERROR] response timeout error : 00000104 cmd 17
** Can't read partition table on 0:0 **
there are pending interrupts 0x00000104
[ERROR] response timeout error : 00000104 cmd 17
** Unable to use mmc 0:1 for fatload **
there are pending interrupts 0x00000104
[ERROR] response timeout error : 00000104 cmd 17
** Can't read partition table on 0:0 **
** Bad partition 1 **
ext4load - load binary file from a Ext4 filesystem
Usage:
ext4load <interface> <dev[:part]> [addr] [filename] [bytes]
- load binary file 'filename' from 'dev' on 'interface'
to address 'addr' from ext4 filesystem
there are pending interrupts 0x00000104
[ERROR] response timeout error : 00000104 cmd 17
** Can't read partition table on 0:0 **
** Bad partition 2 **
ext4load - load binary file from a Ext4 filesystem
Usage:
ext4load <interface> <dev[:part]> [addr] [filename] [bytes]
- load binary file 'filename' from 'dev' on 'interface'
to address 'addr' from ext4 filesystem
>>> Load Boot Script from mmc 0:1 <<<
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
>>> Load Boot Script from mmc 0:2 <<<
** Unable to use mmc 0:2 for fatload **
>>> Run Default Bootcmd <<<
reading kernel..device 0 Start 1263, Count 16384
MMC read: dev # 0, block # 1263, count 16384 ... 16384 blocks read: OK
completed
reading RFS..device 0 Start 17647, Count 2048
MMC read: dev # 0, block # 17647, count 2048 ... 2048 blocks read: OK
completed
Bad Linux ARM zImage magic!
Now power cycling the XU4... and it's continually rebooting as before...
put the sd-card back into my main PC and it's not seen. Eh?
As you guys have had this working, it would be great to know what OS,
Kernel version, you used?
I'll get the Y-cable and better PSU, and (hopefully) re-flash the image
onto the sd-card, although I cant do that at the moment as it's no
longer being recognised, another ***** new sd-card? :-(, deep
breath...calm...
Maybe after a reboot the card will be seen with Ubuntu, maybe Windows..
Haven't got time now...
Regards,
Dave
On 02/09/17 22:02, Nate Temple 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.
_______________________________________________
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
