Hi,
With prebuild image Angstrom version, we have uImage, MLO, u-boot.bin for sd1 and the system files for sd2, but with self build version as in http://elinux.org/BeagleBoardAndOpenEmbeddedGit, we only use uImage-beagleboard.bin for sd1 and console-image-beagleboard.tar for sd2. I don’t sure why we need u-boot here and what is the function of MLO. I also would like to know how to build it.
I am sorry if my question sounds stupid.
Best regards,
Thang Nguyen
Hi,
With prebuild image Angstrom version, we have uImage, MLO, u-boot.bin for
sd1 and the system files for sd2, but with self build version as in
BeagleBoardAndOpenEmbeddedGit - eLinux.org, we only use
uImage-beagleboard.bin
for sd1 and console-image-beagleboard.tar for sd2. I don't sure why we
need
u-boot here and what is the function of MLO. I also would like to know how
to build it.
I am sorry if my question sounds stupid.
Best regards,
Thang Nguyen
Hi Thang,
Information for obtaining and building MLO (xloader) and u-boot can be found
at:
http://elinux.org/BeagleBoard#X-Loader
The MLO file is a file the OMAP ROM-code searches for on the MMC card in
order to do MMC booting - See TRM (spruf98b.pdf) chapter 25.4.7.6. You
create the MLO file by signing the binary xloader image by the tool called
signGP
(Google Code Archive - Long-term storage for Google Code Project Hosting.)
Depending on xloader and u-boot versions in the POP NAND-flash you
might/might not need the files on the MMC card as well...
The newer versions of the xloader will use a MMC u-boot in case it exists -
Else it will use the version in NAND flash.
I think the change came with version 1.4.2. Before this u-boot in NAND flash
would be used by default...
I hope this helps
Søren
If you already have an up-to-date x-load.bin.ift and u-boot in the flash, then there is no need to put them on the SD card. MLO is just x-load.bin.ift renamed so that the ROM bootloader can find it. See the diagnostic code at http://beagleboard.org/support.