BBB wireless eMMC flash problem

Seems my BBB wireless quit booting from eMMC. I fired up bone-debian-9.5-iot-armhf-2018-10-07-4gb.img from SD card and set uEnv.txt to flash. Fail :frowning:

The following appears to be the offending part of the log. Here is the entire log on my pastebin as captured by TeraTerm.

Is there anything to try to initialize / format / recover for flashing the emmc?

Thanks, - Jeff

`

In this thread @RobertCNelson suggests to try old image. Here is the log from that unsuccessful attempt;

`
U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img

U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)

I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

Net: not set. Validating first E-fuse MAC
Could not get PHY for cpsw: addr 0
cpsw, usb_ether
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
1672 bytes read in 5 ms (326.2 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 …
reading zImage
4103240 bytes read in 227 ms (17.2 MiB/s)
reading initrd.img
2957458 bytes read in 166 ms (17 MiB/s)
reading /dtbs/am335x-boneblack.dtb
25926 bytes read in 9 ms (2.7 MiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x3e9c48 ]

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Using Device Tree in place at 88000000, end 88009545

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.378382] omap2_mbox_probe: platform not supported
[ 0.532986] tps65217-bl tps65217-bl: no platform data provided
[ 0.596730] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 0.633839] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 0.670947] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 0.708056] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 0.722735] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.732349] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[ 0.739097] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.756676] omap_hsmmc mmc.5: of_parse_phandle_with_args of ‘reset’ failed
[ 0.819666] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[ 0.831347] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[ 0.838647] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 1.042656] Unhandled fault: external abort on non-linefetch (0x1008) at 0xe089c000
[ 1.050780] Internal error: : 1008 [#1] SMP THUMB2
[ 1.055850] Modules linked in:
[ 1.059092] CPU: 0 Not tainted (3.8.13-bone50 #1)
[ 1.064436] PC is at cpsw_probe+0x348/0x960
[ 1.068858] LR is at ioremap_page_range+0x95/0xf8
[ 1.073827] pc : [] lr : [] psr: a0000033
[ 1.073827] sp : df071e18 ip : 00000000 fp : df0d3400
[ 1.085950] r10: c081de48 r9 : de28d000 r8 : de28d590
[ 1.091457] r7 : de28d000 r6 : de28d540 r5 : 00000000 r4 : e089c000
[ 1.098334] r3 : 80000000 r2 : 00000000 r1 : e089d000 r0 : e089c000
[ 1.105226] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA Thumb Segment kernel
[ 1.113114] Control: 50c5387d Table: 9e284019 DAC: 00000015
[ 1.119181] Process swapper/0 (pid: 1, stack limit = 0xdf070240)
[ 1.125518] Stack: (0xdf071e18 to 0xdf072000)
[ 1.130118] 1e00: 00000000 c00b5629
[ 1.138754] 1e20: c086b9b8 c086b9b8 de28d540 de28d298 df0d3410 de5fc8c8 00000000 df071e90
[ 1.147395] 1e40: df071e90 c00fdd53 22222222 22222222 00000000 c086b9b8 de5fc8c8 de5f9ec0
[ 1.156038] 1e60: de5fc8c8 c00fdc8f de5fc8c8 00000000 df071e90 de5fc948 df0d5d48 c00fe507
[ 1.164673] 1e80: df0494b8 c00492af 00000000 df0d3444 00000020 00000008 df0d3410 c09189ec
[ 1.173305] 1ea0: df0d3410 c088aa58 00000000 c0800925 00000100 c081de48 00000000 c02c6e19
[ 1.181935] 1ec0: c02c6e09 c02c62bb 00000000 df0d3410 c088aa58 df0d3444 00000000 c02c641b
[ 1.190559] 1ee0: c088aa58 c02c63d1 00000000 c02c53ef df049478 df0ce600 c088aa58 c087fe90
[ 1.199196] 1f00: de5f9ec0 c02c5daf c072dc7c c088aa58 c088aa58 df070000 c08ab580 00000000
[ 1.207829] 1f20: c0800925 c02c671d 00000000 c080b080 df070000 c08ab580 00000000 c0800925
[ 1.216463] 1f40: 00000100 c000867f 00000007 00000007 c0863b18 c080b07c c080b080 00000007
[ 1.227702] 1f60: c080b060 c08ab580 c07e51c9 c081de48 00000000 c07e56a3 00000007 00000007
[ 1.238911] 1f80: c07e51c9 c0d35fc0 00000000 c04c4e29 00000000 00000000 00000000 00000000
[ 1.250121] 1fa0: 00000000 c04c4e2f 00000000 c000c8fd 00000000 00000000 00000000 00000000
[ 1.261345] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1.272589] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 ffffffff fffdffff
[ 1.283871] [] (cpsw_probe+0x348/0x960) from [] (platform_drv_probe+0x11/0x14)
[ 1.296039] [] (platform_drv_probe+0x11/0x14) from [] (driver_probe_device+0x53/0x168)
[ 1.308936] [] (driver_probe_device+0x53/0x168) from [] (__driver_attach+0x4b/0x4c)
[ 1.321559] [] (__driver_attach+0x4b/0x4c) from [] (bus_for_each_dev+0x27/0x48)
[ 1.333885] [] (bus_for_each_dev+0x27/0x48) from [] (bus_add_driver+0xe3/0x168)
[ 1.346203] [] (bus_add_driver+0xe3/0x168) from [] (driver_register+0x3d/0xc4)
[ 1.358437] [] (driver_register+0x3d/0xc4) from [] (do_one_initcall+0x1f/0xf4)
[ 1.370682] [] (do_one_initcall+0x1f/0xf4) from [] (kernel_init_freeable+0xc3/0x158)
[ 1.383452] [] (kernel_init_freeable+0xc3/0x158) from [] (kernel_init+0x7/0x98)
[ 1.395767] [] (kernel_init+0x7/0x98) from [] (ret_from_fork+0x11/0x34)
[ 1.407382] Code: f000 81d2 f8c7 05c0 (6803) f44f
[ 1.415235] —[ end trace 9c753e3b5081fdde ]—
[ 1.423064] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 1.423064]
[ 1.438275] drm_kms_helper: panic occurred, switching back to text console

`

On Tue, 18 Jun 2019 20:22:20 -0700 (PDT), Jeff Albrecht
<jeffrey.h.albrecht@gmail.com> declaimed the
following:

!==> Error: [/dev/mmcblk1] does not exist
writing to [/dev/mmcblk1] failed...

  Off hand -- I'd say the eMMC is dead...

  Or you are booting with a device tree that has taken control of the
eMMC signal lines or disabled the eMMC (make sure you do NOT have...
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices

I wonder if I can find a through hole replacement? :wink:

I do have a hot air rework station though…Has anyone ever successfully done a field repair of eMMC?

  • Jeff

Before you go do that, give this latest image a shot:

https://rcn-ee.net/rootfs/bb.org/testing/2019-06-16/buster-iot/bone-eMMC-flasher-debian-buster-iot-armhf-2019-06-16-4gb.img.xz

Regards,

:frowning: nope. Bummer. I’m willing to try any other suggestions. Pastebin of the log for this attempt with bone-eMMC-flasher-debian-buster-iot-armhf-2019-06-16-4gb.img.xz

Looking at the board I’m assuming the Kingston chip is the eMMC. Doesn’t look like anything I can replace in my lab with my tools.

  • Jeff