Can not flash eMMC through convenient methods!

[ely.abo...@gmail.com]

Hi,

I have tried several ways to flash my BBB's eMMC including:

1) un-commenting the following line in /boot/uEnv.txt :

#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

2) pushing the S2 button in power-up . 

In both methods nothing happens and it boots on uSD card. The minicom output is as follows:

U-Boot SPL 2016.03-00001-gd12d09f (Mar 17 2016 - 16:16:15)

Trying to boot from MMC

bad magic

U-Boot 2016.03-00001-gd12d09f (Mar 17 2016 - 16:16:15 -0500), Build: jenkins-github_Bootloader-Builder-351

       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:   <ethaddr> not set. Validating first E-fuse MAC

cpsw, usb_ether

Press SPACE to abort autoboot in 2 seconds

switch to partitions #0, OK

mmc0 is current device

Scanning mmc 0: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

mmc0 is current device

gpio: pin 54 (gpio 54) value is 1

Checking for: /uEnv.txt ...

1179 bytes read in 12 ms (95.7 KiB/s)

gpio: pin 55 (gpio 55) value is 1

Loaded environment from uEnv.txt

Importing environment from mmc ...

Checking if uenvcmd is set ...

gpio: pin 56 (gpio 56) value is 1

Running uenvcmd ...

1197 bytes read in 69 ms (16.6 KiB/s)

debug: [/boot/vmlinuz-4.4.9-ti-r25] ...

7833256 bytes read in 501 ms (14.9 MiB/s)

debug: [/boot/initrd.img-4.4.9-ti-r25] ...

4761957 bytes read in 321 ms (14.1 MiB/s)

debug: [/boot/dtbs/4.4.9-ti-r25/am335x-boneblack.dtb] ...

60958 bytes read in 92 ms (646.5 KiB/s)

debug: [console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable] ...

debug: [bootz 0x82000000 0x88080000:48a965 0x88000000] ...

Kernel image @ 0x82000000 [ 0x000000 - 0x7786a8 ]

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Using Device Tree in place at 88000000, end 88011e1d

Starting kernel ...

[    2.006623] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle

[    2.177466] omap_voltage_late_init: Voltage driver support not added

[    2.184898] PM: Cannot get wkup_m3_ipc handle

[    2.293317] bone_capemgr bone_capemgr: slot #0: No cape found

[    2.337340] bone_capemgr bone_capemgr: slot #1: No cape found

[    2.381298] bone_capemgr bone_capemgr: slot #2: No cape found

[    2.425306] bone_capemgr bone_capemgr: slot #3: No cape found

Loading, please wait...

fsck: error 2 (No such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1

fsck exited with status code 8

[   10.416490] systemd-fsck[158]: rootfs: clean, 137855/217728 files, 813740/870144 blocks

[   17.392524]  remoteproc1: failed to load am335x-pru0-fw

[   17.529704]  remoteproc1: request_firmware failed: -2

[   17.534990] pru-rproc 4a334000.pru0: rproc_boot failed

[   18.040100]  remoteproc1: failed to load am335x-pru1-fw

[   18.081632]  remoteproc1: request_firmware failed: -2

[   18.086946] pru-rproc 4a338000.pru1: rproc_boot failed

[   21.591446] platform 48300180.eqep: Cannot lookup hwmod 'eqep0'

[   21.642885] platform 48302180.eqep: Cannot lookup hwmod 'eqep1'

[   21.691230] platform 48304180.eqep: Cannot lookup hwmod 'eqep2'

[   22.556778] eqep 48300180.eqep: failed to get clock

[   22.778073] eqep 48302180.eqep: failed to get clock

[   23.112100] eqep 48304180.eqep: failed to get clock

Debian GNU/Linux 8 beaglebone ttyS0

BeagleBoard.org Debian Image 2016-05-13

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

default username:password is [debian:temppwd]

The IP Address for usb0 is: 192.168.7.2

beaglebone login: 

when I run "lsblk" on my BBB it outputs like this:

mmcblk1boot0 179:16   0    1M  1 disk 

mmcblk1boot1 179:24   0    1M  1 disk 

mmcblk0      179:0    0  3.7G  0 disk 

��󿔔��─mmcblk0p1  179:1    0  3.3G  0 part /

mmcblk1      179:8    0  1.8G  0 disk 

��└��─mmcblk1p1  179:9    0  1.8G  0 part 

which shows that eMMC storage is 1.8G. very surprised!

don't know where to go from here!  

[Robert Nelson]

Notice you don't see
"init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh" here?

That means, you didn't un-comment:

#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
->
cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

PS, you have a 2gb bbb, use the 2gb images, as teh 4gb won't fit.

Regards,

--
Robert Nelson
https://rcn-ee.com/