What it does, is it goes through all the partitions on the eMMC, and then all the partitions on the uSD card, and adds them and their details (including names) into an array called "partition_entries".
Later on, it runs the aboot application, starting with aboot_init, which calls boot_linux_from_mmc().
Now THAT function does this;
Code:
if (!boot_into_recovery) { index = partition_get_index("boot"); ptn = partition_get_offset(index); if(ptn == 0) { dprintf(CRITICAL, "ERROR: No boot partition found\n"); return -1; } }
Obviously for us, we would prefer it to scan the uSD first, and if it finds a boot partition there, use it, otherwise fall back to eMMC.
I believe, that renaming the boot partition on the eMMC to... anything else, would allow you to boot from an sdcard with a GPT partition named "boot". For a bit of added flexibility, renaming it to "recovery" should boot normally from the eMMC when header pin25 is held low (because it will boot from the *first* partition named "recovery").
Leave a comment: