I understand that in the default boot priority, which is the eMMC followed by the microSD, the MLO and u-boot resides in the eMMC.In the case where the eMMC does not contain a valid boot image, the microSD gets booted.
Question: does a bootable microSD contain a copy of the MLO and uboot?
–Luther
I am assuming the answer is yes based on what was discussed in this thread[1].
Next question. If I flash the eMMC using the microSD card debian flasher script, and then dd out 1MB from the eMMC and microSD, do I expect both to have the same shasum? I expect yes, since they came from the same debian image, but unless I made a mistake or there are some false assumptions on my part, I seemed to be getting different checksums
[1] https://groups.google.com/forum/#!searchin/beagleboard/mlo$20microsd|sort:relevance/beagleboard/8fe5054qZss/xVX8hSPa7OoJ
I am assuming the answer is yes based on what was discussed in this
thread[1].
Next question. If I flash the eMMC using the microSD card debian flasher
script, and then dd out 1MB from the eMMC and microSD, do I expect both to
have the same shasum? I expect yes, since they came from the same debian
image, but unless I made a mistake or there are some false assumptions on my
part, I seemed to be getting different checksums
No... different drive geometries..
[1]
Redirecting to Google Groups
I understand that in the default boot priority, which is the eMMC followed
by the microSD, the MLO and u-boot resides in the eMMC.In the case where the
eMMC does not contain a valid boot image, the microSD gets booted.
Question: does a bootable microSD contain a copy of the MLO and uboot?
Yes..
Regards,