Beagleboard-xm rev C and u-boot

Beagleboard-xm rev C and u-boot

[Robert Berger]

Hi,

Sorry for cross-posting something similar also on the beagleboard mailing list, 
but I think that some people here might be able to help.

I'm using a beagle-xm Rev C and trying to find a "proper" u-boot version, which 
is at least able to load a kernel and ideally also has network support from u-
boot.

So I saw this:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-bsp/u-boot/u-
boot_2011.06.bb

which gets u-boot from mainline with tag v2011.06

I compiled this and it did not work;)

So I saw this innocent comment in 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-bsp/u-boot/u-
boot.inc

# GCC 4.5.1 builds unusable binaries using -Os, remove it from 
OPTFLAGS 
EXTRA_OEMAKE = "CROSS_COMPILE=${TARGET_PREFIX} OPTFLAGS='-O2'" 

Which means yocto builds u-boot v2011.06 replacing -Os with -O2 and indeed this 
did the trick. 

Up to now I thought that the problem with -Os and -O2 existed only with PPC, but 
my experiments show that it also exists with ARM.

Trying any new version than v2011.06 creates some linker error at the end.

Did someone manage to get a newer version of u-boot to run on a beagle-xm Rev C?

How and with which toolchain?

Regards,

Robert

Re: Beagleboard-xm rev C and u-boot

[Robert Berger]

Hi,

On 01/17/2012 09:26 AM, Robert Berger wrote:
> 
> Did someone manage to get a newer version of u-boot to run on a beagle-xm Rev C?
> 
I did in the meantime without any special tricks like replacying -Os
with -O2.

Just use u-boot mainline v2011.12.

The trick is, that you need to use the MLO generated by u-boot mainline
and u-boot.img instead of u-boot.bin.

So I guess this could be also updated here.

Regards,

Robert...If you've found 3 bugs in a program, best estimate is that
there are 3 more.-Jack Ganssle

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1