public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ricardo <ricardo.ribalda@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MAKEALL ml507_flash return "Not enough room for programheaders" error
Date: Mon, 3 Nov 2008 09:25:33 +0100	[thread overview]
Message-ID: <aa76a2be0811030025s2e7d5825i9c4e6b02dfb260e8@mail.gmail.com> (raw)
In-Reply-To: <51DD8AFE36DED843B50F1C56E06F74166F8C21@gpexcbne01.gpnet.local>

Hello Benny

  I have just checkout the build of the ml507_flash and works ok for me

ricardo at aragorn:~/curro/qtec/u-boot$ ./MAKEALL ml507_flash
Configuring for ml507 board...
   text	   data	    bss	    dec	    hex	filename
 202132	  10476	  30032	 242640	  3b3d0	./u-boot


  I remember that when I was using another toolchain the final link
failed (but showing different error). Try with another toochain, I am
using one produced by OpenEmbedded, but you will get the same results
with the ELDK


  Best regards



On Mon, Nov 3, 2008 at 07:59, Benny Chen <benny.chen@groundprobe.com> wrote:
> Hi there,
>
> I am trying to build a U-Boot image for the ML507 board running from
> FLASH and got the "Not enough room for program headers" error.
>
>
>
> The main difference for my setup is the toolchain.  I am using the
> powerpc-eabi-ld linker from Xilinx's EDK tool chain to build the
> ml507_flash design for U-Boot.
>
>
>
> I have seen a patch on the linker script for the mpc8555cds board and
> tried adding the patch to the Xilinx/ppc440-generic/u-boot-rom.lds but
> got the "relocation truncated to fit R_PPC_REL24" error.
>
> Before going further with debugging this problem, I would like to check
> if this problem is due to the powerpc-eabi tool chain from Xilinx?
>
>
>
> Thanks for your help.
>
>
>
> Regards,
>
> Benny
>
>
>
> $ ./MAKEALL ml507_flash
>
> Configuring for ml507 board...
>
> powerpc-eabi-ld: u-boot: Not enough room for program headers (allocated
> 2, need 5)
>
> powerpc-eabi-ld: final link failed: Bad value
>
> make: *** [u-boot] Error 1
>
> size: './u-boot': No such file
>
>
>
>
>
>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>



-- 
Ricardo Ribalda
http://www.eps.uam.es/~rribalda/

  reply	other threads:[~2008-11-03  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  6:59 [U-Boot] MAKEALL ml507_flash return "Not enough room for program headers" error Benny Chen
2008-11-03  8:25 ` Ricardo [this message]
2008-11-04  5:11   ` [U-Boot] MAKEALL ml507_flash return "Not enough room for programheaders" error Benny Chen
2008-11-04  9:13     ` Ricardo
2008-11-05  5:10       ` Benny Chen
2008-11-05 18:13         ` [U-Boot] =?us-ascii?Q?Re=3A=20=5BU=2DBoot=5D=20MAKEALL=20ml507=5Fflash=20return=20=22Not=20enough=20room=20for Michal Simek
2008-11-06  6:27           ` Benny Chen
2008-11-06  6:47             ` [U-Boot] ?Q?Re=3A=20=5BU=2DBoot=5D=20MAKEALL=20ml507=5Fflash=20return=20=22Not=20enough=20room=20for Michal Simek
2008-11-10 23:03         ` [U-Boot] MAKEALL ml507_flash return "Not enough room forprogramheaders" error Benny Chen

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=aa76a2be0811030025s2e7d5825i9c4e6b02dfb260e8@mail.gmail.com \
    --to=ricardo.ribalda@gmail.com \
    --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