From: Jerry Van Baren <gerald.vanbaren@comcast.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] objcopy
Date: Sat, 17 Mar 2007 16:44:18 -0400 [thread overview]
Message-ID: <45FC5322.5030205@comcast.net> (raw)
In-Reply-To: <9F3F0A752CAEBE4FA7E906CC2FBFF57C069B49@MERCURY.inside.istor.com>
Charles Krinke wrote:
> 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?
>
> Charles
We knew that, that was a teaching exercise. :-) Next lesson is bottom
posting on emails. :-O
The reason for your --gap-fill problem is because you have an enormous
gap somewhere in your memory map/elf file. When you --gap-fill, it
creates a file filled with 0x00/0xFF which turns into an enormous file.
When you don't --gap-fill, the file simply has a gap. Look at your
memory map and the elf file (non --gap-filled ;-) - obdump is your
friend) and see where and why you have an enormous gap in your linked
file. Usually the solution is fairly obvious once you understand why.
It may be as simple as not using --gap-fill because it hurts to
--gap-fill, it may be because you have something wrong in your linker
configuration file - *.lds).
My speculation (based on 82xx experience, not 85xx) is that you have a
HRCW defined at offset zero or at the start of your flash (0xFE000000 or
something like that) and are "booting high" (start of program at
0xFFF00100) which is an enormous gap. If you make a bin without filling
the gap, your HRCW is in the "wrong place" but it is ignored and life
works. If you --gap-fill, you make an enormous file and your file
system isn't happy.
WRT you single step question, I'm not sure (don't do it). If you are
trying to step through u-boot, see
<http://www.denx.de/wiki/DULG/DebuggingUBoot>
There are hints on how to step through the linux kernel as well, but I'm
too lazy to google it right now.
Best regards,
gvb
next prev parent reply other threads:[~2007-03-17 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 5:30 [U-Boot-Users] Hiiii....Everyone kushal ahuja
2007-03-15 17:04 ` pharaoh
2007-03-16 15:02 ` Greg Lindberg
2007-03-16 20:16 ` Wolfgang Denk
2007-03-16 22:15 ` Greg Lindberg
2007-03-17 15:34 ` [U-Boot-Users] objcopy Charles Krinke
2007-03-17 16:59 ` Jerry Van Baren
2007-03-17 18:21 ` Charles Krinke
2007-03-17 20:44 ` Jerry Van Baren [this message]
2007-03-16 6:57 ` [U-Boot-Users] Hiiii....Everyone kushal ahuja
2007-03-16 9:21 ` ThomasB
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=45FC5322.5030205@comcast.net \
--to=gerald.vanbaren@comcast.net \
--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