>One last question, what are the mmcblk2boot0 and mmcblk2boot1 devices for?
I think, don't know for sure, remnants of android,
you will notice that they do not show up in fdisk/cfdisk/gdisk,,
so they are NOT in partition table
They can safely be ignored,, except they are always on emmc, never on SD
so gives a clue which blk dev is which
The bootrom expects idbloader and uboot to be specific places, cares nothing about partitions
It is a raw read,, 0x8000,, 0x800 000 (Bytes) If idbloader signature is not there, on to next
in understandable,, 64 sectors, 8M,, if there is a trust, 12M
(and it is different on SPI, 0x0 and 0x600 000 I think, not at all sure)
I think, don't know for sure, remnants of android,
you will notice that they do not show up in fdisk/cfdisk/gdisk,,
so they are NOT in partition table
They can safely be ignored,, except they are always on emmc, never on SD
so gives a clue which blk dev is which
The bootrom expects idbloader and uboot to be specific places, cares nothing about partitions
It is a raw read,, 0x8000,, 0x800 000 (Bytes) If idbloader signature is not there, on to next
in understandable,, 64 sectors, 8M,, if there is a trust, 12M
(and it is different on SPI, 0x0 and 0x600 000 I think, not at all sure)