[U-Boot-Users] objcopy

Charles Krinke ckrinke at istor.com
Sat Mar 17 19:21:55 CET 2007

My apologies. The error when specifying a --gap-fill of either 0x00 or 0xff is
File size limit exceeded
I have seen this with .section not completely defined, but not with a --gap-fill before and am wondering why the gap fill would cause this.
I also have a second question.
I can single step through the binary with a BDI2000, but only from the object viewpoint, that is stepi works, but step doesnt. I think there may be an incantation for the assembler to pass a debug flag similar to the -g for the compiler. Something like -Wa,-dwarf (sic). Can someone tell me what the incantation is?


From: Jerry Van Baren [mailto:gerald.vanbaren at comcast.net]
Sent: Sat 3/17/2007 9:59 AM
To: Charles Krinke
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] objcopy

Charles Krinke wrote:
> I have a need to run a small binary before u-boot runs on a PPC8541. With that in mind, I have the binary, it compiles & links, but has a behavior at the last step of compilation I dont quite understand and it relates to the behavior of objcopy as used in uboot/Makefile.
> This doesnt work
> $ ppc_85xx-objcopy --gap-fill 0xff -O binary microStart microStart.bin
> This works and creates the proper binary
> $ ppc_85xx-objcopy -O binary microStart microStart.bin
> So, my question is  "What is it about using a gap fill that would cause this error?"
> Charles

It would be helpful to include the error message.


More information about the U-Boot mailing list