Manualy dd image files to eMMC when booted from sd card.

[brick 0]

Hi, I can not boot recovery.img from sd card and can not flash from computer.

If I prepare sd card following the instructions here, then flash.sh script gets stuck on: "< waiting for any device >" (visible in script debug mode), no usb device is found on my computer - lsusb shows nothing like Mendel or Tinker or Google device there. Multiple usb cables tested. Sd card is ok, because booting from it (sdcard_arm64.img) works well.

I'd like to flash the img files manualy from another flash drive using dd command from the shell when booted from sd card.

Please, what are the correct images and their /dev/??? targets to manualy dd images to emmc?

I expect these files to be flashed (taken from flash.sh script):

1. sudo dd BS=4M if=u-boot.imx of=/dev/???  (should it be: mmcblk0boot0 ?)
2. sudo reboot-bootloader
3. sudo dd BS=4M if=partition-table-8gb.img of=/dev/???  (mmcblk0 ?)
4. sudo reboot-bootloader
5. // somehow erase misc partition - where it is?
6. sudo dd BS=4M if=home.img of=/dev/???   (rest of mmcblk0 ?)
7. sudo dd BS=4M if=boot_arm64.img of=/dev/???    (should it be: mmcblk0boot1 ?)
8. sudo dd BS=4M if=rootfs_arm64.img of=/dev/???  (should it be: mmcblk0rpmb ?)

Problems:

• sudo reboot-bootloader gives me an error: can not find misc partition.
• sudo dd BS=4M if=u-boot.imx of=/dev/mmcblk0 works fine, but of=/dev/mmcblk0boot0 ends with an error: operation not permited.

I appreciate any help with this. 

[brick 0]

I've found some mapping:

• partition-table-8gb.img -> mmcblk0 (new /dev/mmcblk0p1-4 devices are created)
• u-boot.imx -> mmcblk0p1
• boot_arm64.img -> mmcblk0p2
• rootfs_arm64.img -> mmcblk0p3
• home.img -> mmcblk0p4

After this mapping the reboot-bootloader works and the Tinker Edge T splash screen is shown and it gets stuck there. But lsusb shows me: Bus 003 Device 013: ID 0b05:7771 ASUSTek Computer, Inc. USB download gadget.

The flash.sh script still waits for any device to be connected.

What is wrong here?

Edited January 11, 2022 by brick

[brick 0]

After swithing to boot from eMMC it finally boots until the error root file system not found.

[brick 0]

Update:

I did an 8GB empty image on my computer and then I did dd in following order. There are captions for partitions after ther first partition-table-8gb.img is put to it.

• partition-table-8gb.img -> mmcblk0 (new /dev/mmcblk0p1-4 devices are created)
• boot_arm64.img -> mmcblk0p1
• /misc is created -> mmcblk0p2
• home.img -> mmcblk0p3
• rootfs_arm64.img -> mmcblk0p4

I think, that this should work, but after boot the rootfs is not found and boot process stops there. I have no clue how to continue.

Edited January 11, 2022 by brick

[Henri 0]

Hello,

I am facing the same problem.

Is there any update or informations from anybody ?

Thanks !

[tooz 54]

hello @Henri / @brick, 

sudo dd BS=4M if=u-boot.imx of=/dev/mmcblk0boot0
sudo dd BS=4M if=partition-table-8gb.img of=/dev/mmcblk0
sudo dd BS=4M if=boot_arm64.img of=/dev/mmcblk0p1 
sudo dd BS=4M if=home.img of=/dev/mmcblk0p3
sudo dd BS=4M if=rootfs_arm64.img of=/dev/mmcblk0p4

the partition table of tinker edge t:

mmcblk0boot0 4M u-boot
mmcblk0      179:0    0  7.3G  0 disk
├─mmcblk0p1  128M boot
├─mmcblk0p2  1M misc
├─mmcblk0p3  2G home
└─mmcblk0p4  5.1G rootfs

u-boot.imx -> mmcblk0boot0
boot_arm64.img -> mmcblk0p1
home.img -> mmcblk0p3
rootfs_arm64.img -> mmcblk0p4

[brick 0]

Hi @brick, @Henri, @tooz,

do you have some news about this topic? Do you have some fork of the armbian? Do you have discord channel for this, like Armbian has?

Best Regards.

[tooz 54]

hello @brick, 

the partition table: 

what's the issue you're facing now? 

 

[gavin67890 0]

This helped me https://hub.mender.io/t/boot-from-emmc-on-coral-dev-board/2256/3

On a Coral Dev Board, I found that after booting the recovery.img from SD that the flash.sh would fail because the env variable was missing. But if you walk carefully through the flash.sh you can manually run each command one-by-one.