From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] How to Remove the padding bits from u-boot.bin
Date: Wed, 04 Mar 2009 07:41:44 -0500 [thread overview]
Message-ID: <49AE7708.9040205@ge.com> (raw)
In-Reply-To: <5ae31d3b0903032122t7e689978j2d6ba0a14314efa0@mail.gmail.com>
kuldeep nigam wrote:
> Hi All,
> I am using MIP405T board and trying to reduce the size of u-boot.bin
> by disabling the drivers that i didn't need. But the image size is not
> changing because it is padding all 1's at the end of the image. Can anyone
> tell me how to remove these padding bits.
>
> Image size is 512 K
> Actual image size is 207 K (approx.)
> u-boot version is 1.3.2
>
> Hexdump of u-boot.bin is as follows:
>
> 00337d0 0000 0200 0000 0100 f9ff a8d0 faff 78f8
> 00337e0 faff 90f8 faff acf8 0000 1000 0000 0100
> 00337f0 f9ff 68ce faff b4f8 faff d4f8 faff 04fa
> 0033800 0000 1000 0000 0100 f9ff 68ce faff 08fa
> 0033810 0000 0000 ffff ffff ffff ffff ffff ffff
> 0033820 ffff ffff ffff ffff ffff ffff ffff ffff
> *
> 007fff0 ffff ffff ffff ffff ffff ffff f84b 0421
> 0080000
>
>
>
> with regards,
> kuldeep nigam
Hi kuldeep nigam,
I think you want to change CONFIG_SYS_MONITOR_LEN in your
configs/board/*.h board config file. Based on the numbers above, you
should be able to reduce it to 256K.
* You want it to be a multiple of a flash sector in size.
* Your environment is probably stored in the next flash sector.
* The change doesn't actually change the size of u-boot, it just
changes the amount of padding in the .bin file.
The README file could probably stand some tuning.
<http://git.denx.de/?p=u-boot.git;a=blob;f=README;h=43fb1c0d8959b515c62e612280a0ba538d2921ce;hb=HEAD#l2144>
Best regards,
gvb
prev parent reply other threads:[~2009-03-04 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 5:22 [U-Boot] How to Remove the padding bits from u-boot.bin kuldeep nigam
2009-03-04 12:40 ` Anatolij Gustschin
2009-03-04 12:41 ` Jerry Van Baren [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=49AE7708.9040205@ge.com \
--to=gerald.vanbaren@ge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.