From: Jerry Van Baren <gerald.vanbaren@comcast.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot size and boot issue
Date: Tue, 02 Jan 2007 19:43:30 -0500 [thread overview]
Message-ID: <459AFC32.4090705@comcast.net> (raw)
In-Reply-To: <e0590900701021501m434b806cua937bdac4191b765@mail.gmail.com>
mitsy wrote:
> Hello list,
>
> I have mips board (au1550) and I'm having issues booting the board on
> its own when the u-boot size gets larger than 256k. It will boot fine
> when it's connected to BDI.
>
> What am I doing wrong? I've been trying to figure out where I need to
> make a change to support u-boot with larger size since as long as the
> size if smaller than 256k, it works just fine.
>
> Any suggestion will be greatly appreciated.
>
> Thank you so much for your help.
Hi Mitsy,
Disclaimer: I am not a MIPS expert so I may be all wet...
My first guess is that you've allocated 256Kbytes worth of flash (2
blocks at 128K each? 4 blocks at 64K each?) and so, when your image is
more than 256K, you spill out of the allocated blocks and have a damaged
image. It may be as simple as erasing and programming more than 256K.
After erasing your u-boot image, what is at the 256K mark? Hopefully
all 0xFFs (erased).
Another possibility is if you put your environment variables in a fixed
location at the 256K mark, when your image exceeds 256K, the first time
you do an env save command you will damage your image. This shouldn't
happen, but...
Best regards,
gvb
prev parent reply other threads:[~2007-01-03 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 23:01 [U-Boot-Users] u-boot size and boot issue mitsy
2007-01-03 0:43 ` 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=459AFC32.4090705@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