flashing eMMC are not working

Hello!

I modify a BBB (remove the USB Storage, when connecting to a PC, …) and made a backup with:
dd if=/dev/mmcblk1 bs=1M | ssh name@192.168.178.XX ‘dd of=/home/name/backup.img bs=1M’
This seems to be working … I´m able to flash it on a uSD Card with “Win32 Disk Image”

But when I try to flash a new BBB again, it don´t work.
I insert the uSD, press and hold the button and power up.

Maybe I delete some file, who it need to flash from uSD to eMMC?

Has someone a good tutorial how I can reflash a new BBB?

Thank you!

Look at your serial boot log... Should give you a hint of where things
went wrong..

Regards,

Hi Robert!

The Log output is:
<\n>U-Boot SPL 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06)<\r>
<\n><\n><\r>
<\n><\r>
U-Boot 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06), Build: jenkins-github_Bootloader-Builder-105<\n><\r>
<\n><\r>
Watchdog enabled<\n><\r>
I2C: ready<\n><\r>
DRAM: 512 MiB<\n><\r>
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1<\n><\r>
Using default environment<\n><\r>
<\n><\r>
Net: not set. Validating first E-fuse MAC<\n><\r>
cpsw<\n><\r>
Hit any key to stop autoboot: 1 <\b><\b><\b> 0 <\n><\r>
gpio: pin 53 (gpio 53) value is 1<\n><\r>
switch to partitions #0, OK<\n><\r>
mmc0 is current device<\n><\r>
gpio: pin 54 (gpio 54) value is 1<\n><\r>
Checking for: /uEnv.txt …<\n><\r>
Checking for: /boot.scr …<\n><\r>
Checking for: /boot/boot.scr …<\n><\r>
Checking for: /boot/uEnv.txt …<\n><\r>
gpio: pin 55 (gpio 55) value is 1<\n><\r>
817 bytes read in 22 ms (36.1 KiB/s)<\n><\r>
Loaded environment from /boot/uEnv.txt<\n><\r>
Checking if uname_r is set in /boot/uEnv.txt…<\n><\r>
gpio: pin 56 (gpio 56) value is 1<\n><\r>
Running uname_boot …<\n><\r>
loading /boot/vmlinuz-3.8.13-bone70 …<\n><\r>
5617184 bytes read in 336 ms (15.9 MiB/s)<\n><\r>
loading /boot/dtbs/3.8.13-bone70/am335x-boneblack.dtb …<\n><\r>
26098 bytes read in 32 ms (795.9 KiB/s)<\n><\r>
loading /boot/initrd.img-3.8.13-bone70 …<\n><\r>
2867214 bytes read in 184 ms (14.9 MiB/s)<\n><\r>
debug: [console=ttyO0,115200n8 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN root=UUID=319a7dc6-9ece-408a-877f-f7c38bebb825 ro rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd] …<\n><\r>
debug: [bootz 0x82000000 0x88080000:2bc00e 0x88000000] …<\n><\r>
Kernel image @ 0x82000000 [ 0x000000 - 0x55b620 ]<\n><\r>

Flattened Device Tree blob at 88000000<\n><\r>

Booting using the fdt blob at 0x88000000<\n><\r>
Loading Ramdisk to 8fd43000, end 8ffff00e … OK<\n><\r>
Loading Device Tree to 8fd39000, end 8fd425f1 … OK<\n><\r>
<\n><\r>
Starting kernel …<\n><\r>
<\n><\r>
Uncompressing Linux… done, booting the kernel.<\r>
<\n>[ 0.373011] omap2_mbox_probe: platform not supported<\r>
<\n>[ 0.527892] tps65217-bl tps65217-bl: no platform data provided<\r>
<\n>[ 0.591231] bone-capemgr bone_capemgr.9: slot #0: No cape found<\r>
<\n>[ 0.628338] bone-capemgr bone_capemgr.9: slot #1: No cape found<\r>
<\n>[ 0.665447] bone-capemgr bone_capemgr.9: slot #2: No cape found<\r>
<\n>[ 0.702556] bone-capemgr bone_capemgr.9: slot #3: No cape found<\r>
<\n>[ 0.721167] omap_hsmmc mmc.5: of_parse_phandle_with_args of ‘reset’ failed<\r>
<\n>[ 0.782909] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8<\r>
<\n>[ 0.794575] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22<\r>
<\n>[ 0.801852] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single<\r>
<\n>Loading, please wait…<\r>
<\n>systemd-fsck[207]: rootfs: clean, 86289/233856 files, 569921/933632 blocks<\r>
<\n>[ 5.846980] libphy: PHY 4a101000.mdio:01 not found<\r>
<\n>[ 5.852071] net eth0: phy 4a101000.mdio:01 not found on slave 1<\r>
<\n><\r>
<\n>Musik 7 musik ttyO0<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>172.17.17.2<\r>
<\n>The IP Address for eth0 is: 192.168.0.142<\r>
<\n>musik login:

Is there anything you can read?

Thank you!

Well, so what exactly is the problem? Looks like it booted just fine ^^..

Regards,

Yes, but always from the eMMC.

I added a folder without the uSD card.

Then I insert the uSD, hold the USR Button and power up … the folder is still there … so it boot from eMMC.
Also try without USR Button and set in Windows the Partition 1 as active on the eMMC

He boot always from the eMMC.

Maybe on the uSD is a missing file? Autostart?

I want to flash the uSD to the eMMC, because I customized the linux system.

Thank you!

Crazy … now he boot once from the uSD … but tried after 5 times … always from eMMC :frowning:

From your log:

#mmc0 is current device

So it booted from mmc0 which is microSD

#debug: [console=ttyO0,115200n8
capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
root=UUID=319a7dc6-9ece-408a-877f-f7c38bebb825 ro rootfstype=ext4
rootwait fixrtc quiet init=/lib/systemd/systemd] ...

UUID=319a7dc6-9ece-408a-877f-f7c38bebb825 = eMMC..

You created a copy of the eMMC, so /boot/uEnv.txt is still pointing to
the UUID of the eMMC..

Modify /boot/uEnv.txt's uuid value to point to the UUID of the "microSD"..

Regards,

Now I can reproduce:
insert into windows, set partition 1 as active
insert into BBB, start normal (load from eMMC)
power off, power on normal (load from uSD)
reboot … load always from eMMC
After insert into Windows I see the partition is no longer active.

Maybe you have in idea?

Thank you!

Ok, I unterstand what you mean, but from where I get the UUID from the microSD?
I bootet now from the microSD … and open the uEnv.txt. But don´t know which UUID I have to set.

Or can I flash now with dd from the microSD to the eMMC? Then the UUID is correct, because I only use the microSD for the backup file.

I know there are scripts for Backup … but they don´t work here at me :frowning:

Ask the microSD:

sudo blkid /dev/sdb*

Regards,

Hello Robert,

guess this is to complicated for me … sdb is not available on my BBB.

I have the .img file from my backup.
I mean there are ready to use scripts to bring this image on the eMMC, right?

Maybe you can give me a link, where I can read how to generate the microSD and flash the Image?
Or should I try this again:
http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents

Last time I have problems with the autorun file

Hello Robert,

guess this is to complicated for me ... sdb is not available on my BBB.

Well then use: /dev/mmcblk0

I have the .img file from my backup.
I mean there are ready to use scripts to bring this image on the eMMC,
right?

Maybe you can give me a link, where I can read how to generate the microSD
and flash the Image?
Or should I try this again:
BeagleBone Black Extracting eMMC contents - eLinux.org

Last time I have problems with the autorun file

Regards,

Hello Robert,

so many thanks for your help.
I try now again with:
http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents

and now it works.
I has to set manual in windows the partition as active and generate the folder “dtbs”.

Now I can made the backup and restore

Thanks