BBB-eMMC-flasher code or wishlist?

I’ve got a minor wishlist for the BBB-eMMC-flasher routines, as I’ve been re-flashing my BBB several times in the past few weeks.

What I’d really like is updates to the serial console of what it’s doing, and more importantly when it is completed. I’d also like to have some sort of time stamps on the messages so I can tell how long it took.

I don’t know if the code for the platform is in a place the public can easily contribute. and hadn’t been able to come up with information by searching for BBB-eMMC-flasher so decided to just ask the question here.

I’m currently flashing BBB-eMMC-flasher-2013.09.04.img.xz to my board, and the serial output gives me no feedback to confirm exactly what I’m doing.

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
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
14 bytes read in 4 ms (2.9 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc …
gpio: pin 55 (gpio 55) value is 1
4270840 bytes read in 769 ms (5.3 MiB/s)
gpio: pin 56 (gpio 56) value is 1
24125 bytes read in 62 ms (379.9 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: 4270776 Bytes = 4.1 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 80f88e3c

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.194404] omap2_mbox_probe: platform not supported
[ 0.205028] tps65217-bl tps65217-bl: no platform data provided
[ 0.281540] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 0.318648] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 0.355756] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 0.392864] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 0.412438] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.422032] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[ 0.428804] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.451361] omap_hsmmc mmc.4: of_parse_phandle_with_args of ‘reset’ failed
[ 0.516421] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[ 0.528132] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[ 0.535445] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
systemd-fsck[85]: eMMC-Flasher: clean, 12805/218592 files, 166507/873534 blocks

.—O—.

.-. o o

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

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

The Angstrom Distribution beaglebone ttyO0

Angstrom v2012.12 - Kernel 3.8.13

beaglebone login: [ 9.840730] libphy: PHY 4a101000.mdio:01 not found
[ 9.845827] net eth0: phy 4a101000.mdio:01 not found on slave 1

I've got a minor wishlist for the BBB-eMMC-flasher routines, as I've been re-flashing my BBB several times in the past few weeks.

What I'd really like is updates to the serial console of what it's doing, and more importantly when it is completed. I'd also like to have some sort of time stamps on the messages so I can tell how long it took.

login in and do:

watch systemctl status emmc

I don't know if the code for the platform is in a place the public can easily contribute. and hadn't been able to come up with information by searching for BBB-eMMC-flasher so decided to just ask the question here.

I’m still new to systemd…but I found this command was similar to the old syslog ‘tail -f /var/log/…’
journalctl -f _COMM=emmc.sh

-Dale