BBB version A6 issues

GoogleGroups
1

Hi,

I just got my BBB Rev A6 from Newark Element14.

Unfortunately it does not work on USB… followed all instructions to the dot…
Tried on three PCs with Win7-x64, WinXP-x32, Win-Vista on laptop… PC does not detect BBB at all…no usb drive seen for BBB…
However with a usb-ttl interface board, i get the serial terminal screen and BBB works in that mode.

The Arngstrom version is : 2012.12 kernel : 3.8.13
Tried to flash eMM with latest build but it does not update flash…
Tried booting from SD card with latest image but still no luck…

Though I have been designing DSP & Embedded systems HW & SW for over two and half decades, this is my first try with linux.
Disappointed with such a bad experience…
Any suggestions to fix these board/boot issues?

Thanks,
anbu

2

more info on these issues :

  1. Tried using 2.5A 5V power supply - same issues
  2. Flashed image using DiskImager after formating the SD card as suggested by some, still same issues.
  3. Tried booting with the SD card with latest Arngstrom image, still same.

Here are few screen dumps while normal booting from eMMC and while flashing :

Screendump during normal booting from eMMC :

U-Boot SPL 2013.04-dirty (Jul 10 2013 - 14:02:53)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img

U-Boot 2013.04-dirty (Jul 10 2013 - 14:02:53)

I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
mmc0(part 0) is current device
Card did not respond to voltage select!
No micro SD card found, setting mmcdev to 1
mmc_send_cmd : timeout: No status update
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 1
reading uEnv.txt
26 bytes read in 3 ms (7.8 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc …
gpio: pin 55 (gpio 55) value is 1
4385024 bytes read in 764 ms (5.5 MiB/s)
gpio: pin 56 (gpio 56) value is 1
24808 bytes read in 51 ms (474.6 KiB/s)
Booting from mmc …

Booting kernel from Legacy Image at 80007fc0 …

Image Name: Angstrom/3.8.13/beaglebone
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4384960 Bytes = 4.2 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK

Flattened Device Tree blob at 80f80000

Booting using the fdt blob at 0x80f80000
XIP Kernel Image … OK
OK
Using Device Tree in place at 80f80000, end 80f890e7

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.196290] omap2_mbox_probe: platform not supported
[ 0.206854] tps65217-bl tps65217-bl: no platform data provided
[ 0.283428] bone-capemgr bone_capemgr.8: slot #0: No cape found
[ 0.320535] bone-capemgr bone_capemgr.8: slot #1: No cape found
[ 0.357643] bone-capemgr bone_capemgr.8: slot #2: No cape found
[ 0.394752] bone-capemgr bone_capemgr.8: slot #3: No cape found
[ 0.414475] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.424084] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[ 0.444520] omap_hsmmc mmc.4: of_parse_phandle_with_args of ‘reset’ failed
[ 0.451814] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.518300] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[ 0.530038] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status -22
[ 0.537365] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 10.028611] g_multi: ' invalid for parameter C5’
systemd-fsck[86]: Angstrom: clean, 49262/112672 files, 275502/449820 blocks
[ 11.098934] libphy: PHY 4a101000.mdio:01 not found
[ 11.104027] net eth0: phy 4a101000.mdio:01 not found on slave 1

.—O—.

.-. o o

-----.-----.-----.| | .----…-----.-----.
__ | —'| ‘–.| .-’| | |

— || --‘| | | ’ | | | |
‘—’—’–‘–’–. |-----‘’----‘’–’ ‘-----’-‘-’-’
-’ |
‘—’

The Angstrom Distribution beaglebone ttyO0

Angstrom v2012.12 - Kernel 3.8.13

beaglebone login:

3

Since you tried flashing the eMMC and it’s unknown where or what happened, you probably should solve your problems there and get a valid/complete flashing done so you know you have a starting place. I think the instructions are here: http://beagleboard.org/Getting%20Started#update

it’s also a big deal how/when you hold down the button on the BBB. Once that is done, then it would be time to figure out if you have a cable problem, connector problem, or a Windows problem regarding the USB side. At the very least your computer should be seeing some kind of USB device connecting to it and given you used many different computers it could possibly be a hardware issue. That is if the system wasn’t currupted somehow in failed attempts.

Doug

4

As I mentioned, these were the procedures that were followed exactly. .
The user button was depressed fully till all LEDs came ON and I guess that is also seen from the screen dump as it senses the status.
The problem is that flashing does n’t happen as in many other cases mentioned here.
It should atleast boot from an SD card having the new image but even that does n’t happen I guess… strange.

I find many had faced these types of issues with this version of board… it may be due to hardware, drivers. QC or any design issue…
don’t know if all these similar issues reported here were fixed or boards replaced…

anbu

5

addressing just the flashing of the eMMC, it does take a very long time to flash and might be 40+ minutes IIRC the last time I did it and the speed of your SD card will effect this.
Since you held the button on boot to trigger flashing and had the flashing image on the SD and it blinked ‘for ever’ before lighting all LEDs( this is what is supposed to happen). What was the result when you ejected the SD card and cycled power? Did you list the serial output of booting after the flashing?

Doug

6

I just booted my BBB from eMMC with the serial console on it and checked close to line my line with what you posted above and it looks like it’s all there.
Do you have a display connected to the HDMI port and do you see Angstrom has booted? you should see the beaglebone logo for short period during boot, then some text booting log stuff and then the Angstrom desktop.

Back to your host computer not seeing the USB widgets:
I see my host showing up with both the USB network widget and USB Mass Storage device, that shows up right around when the word Angstrom is displayed on the console in ASCII font and pretty much the end of the boot process.

Doug

7

Yes, that’s what supposed to happen…but I did n’t see the updated version of the kernel after flashing…

Here’s an interesting fix that solved the usb issue :

My ethernet was ok, so I set the date & time then updated, upgraded the packages with opkg and after that my usb driver started working and I could open the browser and connect to beaglebone.
Still kernel is same old 2012 3.8.13 and have n’t tried flashing after the usb issue was fixed…

anbu

8

I don’t have the micro hdmi cable right now… all my hdmi & DVI cables are old ones… will have to get one and test monitor interface…
But now I could connect to BBB from my web browser on PC.(details in my other post)

anbu

9

I’m happy to hear you got it working but so very strange how you had to go about it. And still it seems there is something wrong with flashing… If it were me, I would want to figure out what is up with that because if anything borks your system, that is how you restore. That and you do want the ability to boot from mSD too and I guess that was a problem also.

Doug

10

I will figure it out soon as I need the latest kernel to run on my board… will keep posted…

anbu

11

Further on this :

Flashing eMMC in fact works if you use the correct image to flash and in order to verify if it has flashed an updated kernel check with “uname -a” and note the date, version etc

anbu