Comment 14 for bug 871650

On Mon, Oct 17, 2011 at 5:29 AM, Robert Pollak <email address hidden> wrote:
>> Robert, there's a chance that u-boot might also be the culprit, so can
>> you also check using natty's x-loader and u-boot?
>
> Isn't that what I already did on Paolo's suggestion, see comments 9 and
> 10?

Could be, don't know which ones he copied for you, but it should
probably be from natty.

>> Just grab both MLO and u-boot.bin from the x-loader and u-boot-linaro
>> packages for omap4 and try to boot your board with them.
>
> Ricardo, you surely meant omap3?

Yeah, sorry, my brain was confused by the time I commented at this bug :-)

> And since I am an ARM newbie, I have to ask: Where can I get those files?
>
> In launchpad I found
> https://launchpad.net/ubuntu/+archive/primary/+files/x-loader-omap3-beagle_1.5.0%2Bgit20110325%2Bb6bbfe7-1ubuntu1_armel.deb
> via https://launchpad.net/ubuntu/+source/x-loader,
> and https://launchpad.net/ubuntu/+archive/primary/+files/u-boot-linaro-omap3-beagle_2011.04.2-0ubuntu1_armel.deb
> via https://launchpad.net/ubuntu/+source/u-boot-linaro.

Exactly, if you run 'dpkg -X <package> .' you should have the files
you need, like:
./usr/lib/u-boot/omap3_beagle/u-boot.bin
and
./usr/lib/x-loader/omap3530beagle/MLO

In case you're not able to get anything from your serial, as you
reported with paolo's binaries, you may need to recreate your first
partition filesystem.

For that just mount it at your host, copy all the files from the first
partition, create a new vfat fs (mkfs.vfat -F 32 /dev/sdX1), mount it
again and copy all the files back, copying the MLO first.

Please give it a try and let me know if it works for you.