Can´t flashing new Beaglebone

Hello,

I made a backup from my old Beaglebone Black and want to flash this on a complete new one.
I made this the last 3 years without problems:
Her is the autorun.sh:

`

#!/bin/sh
echo timer > /sys/class/leds/beaglebone:green:usr0/trigger

#un-comment the following line to perform a backup
#dd if=/dev/mmcblk1 bs=16M | gzip -c > /mnt/ENO.img.gz

#un-comment the following 6 lines to perform a restore (be sure to replace XXXXX with your image name)
gunzip -c /mnt/ENO.img.gz | dd of=/dev/mmcblk1 bs=16M
UUID=$(/sbin/blkid -c /dev/null -s UUID -o value /dev/mmcblk1p2)
mkdir -p /mnt
mount /dev/mmcblk1p2 /mnt
ed -i “s/^uuid=.*$/uuid=$UUID/” /mnt/boot/uEnv.txt
umount /mnt

sync
echo default-on > /sys/class/leds/beaglebone:green:usr0/trigger

`

But I get this errors:

`

Starting logging: OK<\r>
<\n>Initializing random number generator… done.<\r>
<\n>Starting network…<\r>
<\n>/etc/init.d/S93-am335x-pm-firmware-load: line 4: can’t create /sys/devices/ocp.2/44d00000.wkup_m3/firmware/am335x-pm-firmware.bin/loading: nonexistent directory<\r>
<\n>/etc/init.d/S93-am335x-pm-firmware-load: line 5: can’t create /sys/devices/ocp.2/44d00000.wkup_m3/firmware/am335x-pm-firmware.bin/data: nonexistent directory<\r>
<\n>/etc/init.d/S93-am335x-pm-firmware-load: line 6: can’t create /sys/devices/ocp.2/44d00000.wkup_m3/firmware/am335x-pm-firmware.bin/loading: nonexistent directory<\r>
<\n>Running /dev/mmcblk0p1/autorun.sh…<\r>
<\n>dd: writing ‘/dev/mmcblk1’: No space left on device<\r>
<\n>0+7863 records in<\r>
<\n>0+7862 records out<\r>
<\n>mount: mounting /dev/mmcblk1p2 on /mnt failed: No such file or directory<\r>
<\n>/etc/init.d/S99autorun: /mnt/autorun.sh: line 12: ed: not found<\r>
<\n>umount: can’t umount /mnt: Device or resource busy<\r>
<\n><\r>
<\r>
<\n>Welcome to Buildroot<\r>
<\n><\r>
beaglebone login:

`

I can see:
dd: writing ‘/dev/mmcblk1’: No space left on device

Is the flasher script to old for newer BeagleBone Black?
I have the backup as an image file and need to flash this on the new BeagleBone Black eMMC

Thank you for help!

Hello,

I set up the new Beaglebone black … so not clone from old one.

But now I have to made a backup and copy this to another new Beaglebone,

In the folder:
/opt/scripts/tools/eMMC

I have the script:
beaglebone-black-make-microSD-flasher-from-eMMC.sh

When I put a microSD in the BBB and start this script … it copy the eMMC to the microSD and at the next BBB I´m able to flash back to eMMC.

Right?

Thank you!

Correct...

Why what's happening?

Regards,

Hi,
I have problem with flashing emmc . History: 5 year ago I make image of running system and created “bootable” sd card with command:
dd if=/dev/mmcblk1 bs=16M | gzip -c > /mnt/BBB-eMMC-$RANDOM.img.gz

Next 5 years I clone BB with this card successfuly. This year no.
Parts of log:

Booting kernel from Legacy Image at 82000000 …

Image Name: Linux-3.8.13
Created: 2013-09-26 13:41:19 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 11748032 Bytes = 11.2 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK

Flattened Device Tree blob at 81ff0000

Booting using the fdt blob at 0x81ff0000
Loading Kernel Image … OK
Loading Device Tree to 8fff6000, end 8ffff133 … OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.813109] omap2_mbox_probe: platform not supported
[ 0.819635] tps65217-bl tps65217-bl: no platform data provided
[ 0.883036] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 0.920143] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 0.957252] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 0.994360] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 1.013254] omap_hsmmc mmc.5: of_parse_phandle_with_args of ‘reset’ failed
[ 1.074693] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[ 1.086361] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[ 1.093643] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 1.188012] mmc1: unrecognised EXT_CSD revision 8
[ 1.192973] mmc1: error -22 whilst initialising MMC card
Starting logging: OK
Initializing random number generator… done.
Starting network…
/etc/init.d/S93-am335x-pm-firmware-load: line 4: can’t create /sys/devices/ocp.2/44d00000.wkup_m3/firmware/am335x-pm-firmware.bin/loading: nonexistent directory
/etc/init.d/S93-am335x-pm-firmware-load: line 5: can’t create /sys/devices/ocp.2/44d00000.wkup_m3/firmware/am335x-pm-firmware.bin/data: nonexistent directory
/etc/init.d/S93-am335x-pm-firmware-load: line 6: can’t create /sys/devices/ocp.2/44d00000.wkup_m3/firmware/am335x-pm-firmware.bin/loading: nonexistent directory
Running /dev/mmcblk0p1/autorun.sh…
dd: writing ‘/dev/mmcblk1’: No space left on device

If I copy image to SD card with imagewriter, BB works.

Any idea or help? I search any help on internet, but without results.

Thanks

Peter

Dátum: utorok 20. marca 2018, čas: 19:56:50 UTC+1, odosielateľ: RobertCNelson

Newer hardware need two patches on that old 3.8.x kernel:

https://github.com/RobertCNelson/yakbuild/tree/master/patches/eMMC/3.8.x

Regards,