[U-Boot-Users] Can't Compile u-boot-1.1.5_atmel_1.2!!

Daniel Hobi dhobi at gmx.net
Tue Feb 27 16:21:01 CET 2007


Argh, ignoring the plain-text restriction myself. Sorry about that!

On 27.02.2007 15:23, 25an wrote:
> I manged to solve the problem but now I get another one. The first
> problem was solved by edit the cpu/arm926ejs/at91sam926x/config.mk 
> file accordingly
> 
> #PLATFORM_CPPFLAGS += -mapcs-32 -march=armv5te -mtune=arm926ejs 
> PLATFORM_CPPFLAGS += -march=armv5te -Wa,-mapcs-32 -mtune=arm926ej-s

I suggest not using -mtune at all, it will most likely not produce
different (more efficient) code than using -march=armv5te alone when
compiling U-Boot.

The gcc flag -mapcs-32 was deprecated since gcc-3.4.0 and finally
removed in gcc-4.0.0 which unconditionally generates 32bit ARM code. You
should not need to pass this flag to the assembler either.

> Now the error that I am getting is
> 
> usb_ohci.c: In function 'usb_lowlevel_init': usb_ohci.c:1659: error:
> invalid lvalue in assignment make[1]: *** [usb_ohci.o] Error 1 
> make[1]: Leaving directory 
> `/opt/x-compile/eldk/workingarea/u-boot-1.1.5_atmel_1.2/cpu/arm926ejs/at91sam926x'
>  make: *** [cpu/arm926ejs/at91sam926x/libat91sam926x.a] Error 2

Again, update to a more recent version of U-Boot. Or, if that is not
possible, use an older toolchain/compiler (for example gcc-3.4.6 should
work with U-Boot 1.1.5).

U-Boot 1.1.5 DOES NOT WORK with gcc-4.x! Expect more (hidden) problems!

> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: base64

Please post plain-text messages to this list.

Regards,
Daniel




More information about the U-Boot mailing list