03-22-2020, 11:51 AM
At present, both "mmcblkXboot0" & "mmcblkXboot1" serve no purpose. Our U-Boot is located directly on the normal eMMC storage. Basically U-Boot starts at sector 64, for 3 sections, (8MB, 4MB & 4MB), and then normal partitions can start after that.
Below is an example where I've created reserved partitions entries for U-Boot. Followed by "/boot", swap and "/". (Note that U-Boot expects "/boot" to be the first partition, so I have it installled that way.)
This means that the exact same U-Boot code and layout works for SD cards as it does for eMMCs. And also SPI flash as well.
Below is an example where I've created reserved partitions entries for U-Boot. Followed by "/boot", swap and "/". (Note that U-Boot expects "/boot" to be the first partition, so I have it installled that way.)
Code:
Device Start End Sectors Size Type
/dev/mmcblk1p1 32768 557055 524288 256M Microsoft basic data
/dev/mmcblk1p2 64 16383 16320 8M Linux reserved
/dev/mmcblk1p3 16384 24575 8192 4M Linux reserved
/dev/mmcblk1p4 24576 32767 8192 4M Linux reserved
/dev/mmcblk1p5 557056 8945663 8388608 4G Linux swap
/dev/mmcblk1p6 8945664 65544144 56598481 27G Linux root (ARM-64)
This means that the exact same U-Boot code and layout works for SD cards as it does for eMMCs. And also SPI flash as well.
--
Arwen Evenstar
Princess of Rivendale
Arwen Evenstar
Princess of Rivendale