Cannot Use BBB After Updating

Hello,

I have recently bought two BeagleBone Black, one from Element14 and one from Adafruit (not the Element14 one). Both are rev C.

When I received my first BeagleBone Black, which was the Element14, I plugged it to the computer through usb to make sure it was working alright, which it was. Problem is, as soon as I updated to the last Debian version (Jessie for BBB, Latest Software Images - BeagleBoard), it rendered the BBB unusable through the micro USB port. The device is not recognized by any of my Windows, Mac and Linux computers. I then tried to redo the installation of the latest Debian version (tried 10 times maybe), and at the end, even plugging the FTDI to USB cable in the BBB would output nothing at all.

Then thinking the device was dead, I bought another one on Adafruit, a 4gb rev c, and about the same thing happened. I checked to see if it was working alright, then updated the distro on it, and now it can’t be recognized by any of my computers. It is worth nothing that both my BBB still seem to try to do something when inserting my SD card. Both devices will have their LEDs moving the way you would expect them when updating the device, and then at some point, they will all flash at the same time which is when I figure the update is over.

My latest BBB can still output something. Here’s the log:

U-Boot SPL 2016.01-00001-g4eb802e (Jan 13 2016 - 11:14:31)
Trying to boot from MMC
bad magic

U-Boot 2016.01-00001-g4eb802e (Jan 13 2016 - 11:14:31 -0600), Build: jenkins-github_Bootloader-Builder-313

Watchdog enabled
I2C: ready
DRAM: 512 MiB
Reset Source: Power-on reset has occurred.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net: not set. Validating first E-fuse MAC
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
Card did not respond to voltage select!
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1…
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt …
Checking for: /boot.scr …
Checking for: /boot/boot.scr …
Checking for: /boot/uEnv.txt …
gpio: pin 55 (gpio 55) value is 1
1684 bytes read in 16 ms (102.5 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt…
gpio: pin 56 (gpio 56) value is 1
Running uname_boot …
loading /boot/vmlinuz-4.1.15-ti-rt-r43 …
7800752 bytes read in 445 ms (16.7 MiB/s)
loading /boot/dtbs/4.1.15-ti-rt-r43/am335x-boneblack.dtb …
60524 bytes read in 40 ms (1.4 MiB/s)
loading /boot/initrd.img-4.1.15-ti-rt-r43 …
4096241 bytes read in 242 ms (16.1 MiB/s)
debug: [console=ttyO0,115200n8 root=UUID=5e77d2fb-74c9-499b-b8a1-1a027bb43611 ro rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable] …
debug: [bootz 0x82000000 0x88080000:3e80f1 0x88000000] …
Kernel image @ 0x82000000 [ 0x000000 - 0x7707b0 ]

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fc17000, end 8ffff0f1 … OK
Loading Device Tree to 8fc05000, end 8fc16c6b … OK

Starting kernel …

[ 3.486358] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 3.797674] cpu cpu0: cpu0 clock notifier not ready, retry
[ 3.943342] bone_capemgr bone_capemgr: slot #0: No cape found
[ 4.003308] bone_capemgr bone_capemgr: slot #1: No cape found
[ 4.063310] bone_capemgr bone_capemgr: slot #2: No cape found
[ 4.123306] bone_capemgr bone_capemgr: slot #3: No cape found
Loading, please wait…
fsck from util-linux 2.25.2
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1
fsck exited with status code 8
[ 11.881257] systemd-fsck[192]: BOOT: clean, 123277/233856 files, 774023/933632 blocks

0* ttyUSB1 5:45PM 17/Mar/2016
Scanning mmc 1:1…
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt …
Checking for: /boot.scr …
Checking for: /boot/boot.scr …
Checking for: /boot/uEnv.txt …
gpio: pin 55 (gpio 55) value is 1
1684 bytes read in 16 ms (102.5 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt…
gpio: pin 56 (gpio 56) value is 1
Running uname_boot …
loading /boot/vmlinuz-4.1.15-ti-rt-r43 …
7800752 bytes read in 445 ms (16.7 MiB/s)
loading /boot/dtbs/4.1.15-ti-rt-r43/am335x-boneblack.dtb …
60524 bytes read in 40 ms (1.4 MiB/s)
loading /boot/initrd.img-4.1.15-ti-rt-r43 …
4096241 bytes read in 242 ms (16.1 MiB/s)
debug: [console=ttyO0,115200n8 root=UUID=5e77d2fb-74c9-499b-b8a1-1a027bb43611 ro rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable] …
debug: [bootz 0x82000000 0x88080000:3e80f1 0x88000000] …
Kernel image @ 0x82000000 [ 0x000000 - 0x7707b0 ]

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fc17000, end 8ffff0f1 … OK
Loading Device Tree to 8fc05000, end 8fc16c6b … OK

Starting kernel …

[ 3.486358] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 3.797674] cpu cpu0: cpu0 clock notifier not ready, retry
[ 3.943342] bone_capemgr bone_capemgr: slot #0: No cape found
[ 4.003308] bone_capemgr bone_capemgr: slot #1: No cape found
[ 4.063310] bone_capemgr bone_capemgr: slot #2: No cape found
[ 4.123306] bone_capemgr bone_capemgr: slot #3: No cape found
Loading, please wait…
fsck from util-linux 2.25.2
fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1
fsck exited with status code 8
[ 11.881257] systemd-fsck[192]: BOOT: clean, 123277/233856 files, 774023/933632 blocks
[ 20.080297] remoteproc1: failed to load am335x-pru0-fw
[ 20.099648] remoteproc1: request_firmware failed: -2
[ 20.162547] pru-rproc 4a334000.pru0: rproc_boot failed
[ 20.572018] remoteproc1: failed to load am335x-pru1-fw
[ 20.592199] remoteproc1: request_firmware failed: -2
[ 20.752269] pru-rproc 4a338000.pru1: rproc_boot failed

Debian GNU/Linux 8 beaglebone ttyS0

BeagleBoard.org Debian Image 2016-01-24

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

beaglebone login: debian
Password:
Linux beaglebone 4.1.15-ti-rt-r43 #1 SMP PREEMPT RT Thu Jan 21 20:13:58 UTC 2016 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

There seems to be some kind of errors, but me not being the most knowledgeable guy when it comes to BBBs since I need it for a single purpose, I was wondering if someone here would be able to help me :smiley:

Please retest with the latest:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots

Which use the "4.1.18-ti-r52" kernel, some of the usb issues seem to
be caused by the RT patchset, so with the "2016-03-13" snapshot we
swapped back to the non-rt varient..

I personally know "g_serial" now works out of the box again..

Regards,

Please retest with the latest:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots

Which use the “4.1.18-ti-r52” kernel, some of the usb issues seem to
be caused by the RT patchset, so with the “2016-03-13” snapshot we
swapped back to the non-rt varient…

I personally know “g_serial” now works out of the box again…

Regards,

Looks like maybe I need to “whip up” a new guide for troubleshooting basic Linux driver issues ? Plus perhaps how to work with the various gadget drivers . . .

I think that would be awesome! especially if it finds its way to the elinux.org website.

I’ve been frustrated with the USB Ethernet gadget’s flaky start-up, especially on Linux hosts. But I haven’t tried 2016-03-13 image yet, 2016-02-21 seemed a bit flakier in limited use before I had to take a hiatus for other things.

Although 2015-11-12 (with upgrades) has been solid on my BBW running pretty much 24/7 since I installed it, rebooting only for kernel upgrade and to test the cold start of my application.

Wally, I’ll give you a hint. In most cases g_ether does not come up, because it was intended that way. But if you really really need it to work, you should learn how to troubleshoot driver modules, and a thing or two about USB gadget drivers. I’ve learned all this myself simply by googling, from knowing nothing about the subject a few years ago( when I started learning about it ).

Its clever, useful, and makes for great demos when it works, but Its not useful enough to be worth hours of Googling and dicking around for what should work out of the box as its purported to be a major feature when you shop for a Beaglebone… Reliability has been great on my BBW not so much on the BBB/BBG for whatever reason – it goes beyond simply a kernel version or image issue as I’ve used the same SD card on all three at various times.