I am trying to flash BBB-eMMC-flasher-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img and bone-debian-7.8-machinekit-armhf-2015-03-15-4gb into my BBB, it went into LEDs cycling fine, but then hangs in the middle.
I hook it up to the serial console, and it says (both images and after retry many times):
you dont have a 4gb emmc on your BBB ?
I believe I do, that’s what I ordered for.
Filesystem Size Used Avail Use% Mounted on
rootfs 3.5G 349M 3.0G 11% /
udev 10M 0 10M 0% /dev
tmpfs 100M 408K 99M 1% /run
/dev/disk/by-uuid/27660b1b-d533-4381-8b5c-a92add03ca3f 3.5G 349M 3.0G 11% /
tmpfs 249M 0 249M 0% /dev/shm
tmpfs 249M 0 249M 0% /sys/fs/cgroup
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 100M 0 100M 0% /run/user
Yet dmesg says:
[ 0.532485] bone-capemgr bone_capemgr.9: Baseboard: ‘A335BNLT,00C0,4414BBBK3366’
[ 0.532510] bone-capemgr bone_capemgr.9: compatible-baseboard=ti,beaglebone-black
[ 0.563190] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 0.600297] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 0.637404] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 0.674513] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 0.680760] bone-capemgr bone_capemgr.9: slot #4: specific override
[ 0.680784] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 4
[ 0.680801] bone-capemgr bone_capemgr.9: slot #4: ‘Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G’
[ 0.680869] bone-capemgr bone_capemgr.9: slot #5: specific override
Is this something I should worry? or is that just an generic name of the firmwre?
It's just the generic name..
"INFO: task mmcqd/0:70 blocked for more than 60 seconds." is usually a
sign of "picky" mmc microSD media for our ancient 3.8 kernel..
Try using a different microSD card.
I had a similar problem. Swapped cards and it worked fine. My old card (4GB) worked with 7.5*** but not with any image above that. Now i used a spare 8GB one and i was able to flash the BBB-eMMC-flasher-debian-8.0-console-armhf-2015-05-08-2gb.img to my BBB. Weird.