From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building uImage with multiple load addresses
Date: Thu, 22 Dec 2011 09:51:52 +0100 [thread overview]
Message-ID: <4EF2EFA8.9040007@denx.de> (raw)
In-Reply-To: <CAOMZO5D1e8VhfoRgCKasSCFSatDjq-CfRNdXhVwCsWU+vL-piQ@mail.gmail.com>
On 21/12/2011 22:24, Fabio Estevam wrote:
> Hi,
>
> When trying to build imx_v4_v5_defconfig, or mx3_defconfig, or
> mx5_defconfig on a 3.2-rc6 kernel I get:
>
> Kernel: arch/arm/boot/Image is ready
> Kernel: arch/arm/boot/zImage is ready
> multiple load addresses: 0x80008000 0x80008000 0x10008000
> This is incompatible with uImages
> Specify LOADADDR on the commandline to build an uImage
> make[1]: *** [arch/arm/boot/uImage] Error 1
> make: *** [uImage] Error 2
>
>
> I started a thread at the ARM kernel list:
> http://marc.info/?l=linux-arm-kernel&m=132343317014712&w=2
>
> ,but I think the U-boot list is the more appropriate one to discuss
> this kind of issue.
>
> So what is the correct way to build a uImage for i.MX now?
Well, I build setting LOADADDR=0x80008000 before make (I think your
example is for MX3).
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2011-12-22 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 21:24 [U-Boot] Building uImage with multiple load addresses Fabio Estevam
2011-12-21 22:20 ` Fabio Estevam
2011-12-22 0:26 ` Stephen Warren
2011-12-22 4:04 ` Marek Vasut
2011-12-22 8:53 ` Stefano Babic
2011-12-22 9:02 ` Wolfgang Denk
2011-12-22 9:18 ` Stefano Babic
2011-12-22 12:04 ` Wolfgang Denk
2011-12-22 12:31 ` Fabio Estevam
2011-12-22 8:51 ` Stefano Babic [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=4EF2EFA8.9040007@denx.de \
--to=sbabic@denx.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