From: Robert Schwebel <r.schwebel@pengutronix.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Help building AT91 u-boot with Buildroot tools
Date: Fri, 10 Oct 2008 21:48:16 +0200 [thread overview]
Message-ID: <20081010194816.GF9852@pengutronix.de> (raw)
In-Reply-To: <1223478784.5733.11.camel@hpub>
On Wed, Oct 08, 2008 at 10:13:04AM -0500, Otto Caldwell wrote:
> I am porting Linux to an Atmel at91rm9200-EK board.
Uhm, as far as I know, Linux works perfectly well on the EK.
> I've built the cross-compile tool chain using Buildroot, choosing the
> armeb (arm embedded) option during the build.
I don't know the buildroot cross compile scripts, but usually armeb is
arm *big endian*, which is not what you need for the 9260.
> I downloaded the AT91 custodian branch of u-boot from
> http://git.denx.de/?p=u-boot/u-boot-at91.git;a=summary
> When I attempt to compile, I get following type of errors:
> armeb-linux-ld: failed to merge target specific data of file
> lib_arm/libarm.a(div0.o)
> armeb-linux-ld: drivers/mtd/nand_legacy/libnand_legacy.a(nand_legacy.o):
> compiled for a big endian system and target is little endian
>
> It finally stops with Error 1.
For the AT91SAM9260 you need a little endian toolchain, something like
arm-v4t oder arm-v5t. You can for example use the OSELAS.Toolchain from
our website (it has a v4t toolchain).
rsc
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
prev parent reply other threads:[~2008-10-10 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 15:13 [U-Boot] Help building AT91 u-boot with Buildroot tools Otto Caldwell
2008-10-10 19:48 ` Robert Schwebel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081010194816.GF9852@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox