* [U-Boot] u-boot.bin
@ 2009-10-28 14:22 David Kaplan
2009-10-28 14:27 ` Jerry Van Baren
0 siblings, 1 reply; 2+ messages in thread
From: David Kaplan @ 2009-10-28 14:22 UTC (permalink / raw)
To: u-boot
What sort of generated file size should i expect for the u-boot.bin file? I
know it's impossible for anyone to tell me exactly, but in what region of
sizes are we talking?
^ permalink raw reply [flat|nested] 2+ messages in thread
* [U-Boot] u-boot.bin
2009-10-28 14:22 [U-Boot] u-boot.bin David Kaplan
@ 2009-10-28 14:27 ` Jerry Van Baren
0 siblings, 0 replies; 2+ messages in thread
From: Jerry Van Baren @ 2009-10-28 14:27 UTC (permalink / raw)
To: u-boot
Hi David,
David Kaplan wrote:
> What sort of generated file size should i expect for the u-boot.bin file? I
> know it's impossible for anyone to tell me exactly, but in what region of
> sizes are we talking?
256K...384K.
If you are looking at a multi-mega/gigabyte .bin file, it is usually
because your memory map has a *large* empty space in it. This is
typically due to interrupt vectors and the executable portions being
widely separated. When creating the .bin file, the Makefile fills empty
spaces with 0xFF (IIRC).
You can use ${CROSS_COMPILE}objdump -h (and other options) to see what
is in your .elf file and where things are located.
gvb
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-10-28 14:27 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-28 14:22 [U-Boot] u-boot.bin David Kaplan
2009-10-28 14:27 ` Jerry Van Baren
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox