>internal eMMC was listed as mmcblk0.
Most distros are NOT consistent, why they don't follow the uboot ordering, I am not sure
(uboots numbers in order found by bootrom)
That the last paragraphs about the SPI are how to zero, that is a gigantic clue
I am amazed at the compulsion to do this, with somewhat immature firmware
Bottom line, unless you are an expert (or almost), you shouldn't do this
Maybe next year
--edit--
You should NOT dd a running system to emmc, you can rsync, exclude proc, sys, dev, run
In a non-running system they should be empty directories
Do make sure fstab and extlinux.conf are right
Better to copy image to sd or usb stick, cd to image,(as root) xzcat compressed-image |dd of=/dev/emmc bs=1M status=progress
(emmc as appropriate)
Most distros are NOT consistent, why they don't follow the uboot ordering, I am not sure
(uboots numbers in order found by bootrom)
That the last paragraphs about the SPI are how to zero, that is a gigantic clue
I am amazed at the compulsion to do this, with somewhat immature firmware
Bottom line, unless you are an expert (or almost), you shouldn't do this
Maybe next year
--edit--
You should NOT dd a running system to emmc, you can rsync, exclude proc, sys, dev, run
In a non-running system they should be empty directories
Do make sure fstab and extlinux.conf are right
Better to copy image to sd or usb stick, cd to image,(as root) xzcat compressed-image |dd of=/dev/emmc bs=1M status=progress
(emmc as appropriate)