From: Rogan Dawes <rogan@dawes.za.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] DNS323 (Orion5x) must double ORION5X_SZ_BOOTROM to access full flash
Date: Mon, 23 Aug 2010 18:06:51 +0200 [thread overview]
Message-ID: <4C729C9B.6000509@dawes.za.net> (raw)
Hi Albert,
I've been trying to figure out why I could not erase sectors in my flash
greater than SA70. It turned out that this was on a megabyte boundary,
and in fact, was exactly half way through my flash.
The flash is a 64Mbit part, i.e. 8MB, and I could only access the first
4MB of it, even though the ORION5X_SZ_BOOTROM parameter was set to (8 *
1024 * 1024). By "access" I mean that even md.b commands simply returned
"00", and flash erase commands returned immediately without actually
doing anything.
Doubling the value for ORION5X_SZ_BOOTROM allowed me to access the
additional sectors, but that makes me wonder what the reason for it is.
I know that the flash chip is wired up strangely, but would that also
affect the window mappings? If that is the case, I just need to document
WHY the parameter is doubled, but if not, it would be good to understand
the real reason for the change.
Rogan
next reply other threads:[~2010-08-23 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 16:06 Rogan Dawes [this message]
[not found] ` <4C7356E0.500@free.fr>
2010-08-24 6:07 ` [U-Boot] DNS323 (Orion5x) must double ORION5X_SZ_BOOTROM to access full flash Albert ARIBAUD
2010-08-24 7:47 ` Rogan Dawes
2010-08-24 11:34 ` Albert ARIBAUD
2010-08-24 12:17 ` Rogan Dawes
2010-08-24 12:52 ` Albert ARIBAUD
2010-08-25 4:38 ` Prafulla Wadaskar
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=4C729C9B.6000509@dawes.za.net \
--to=rogan@dawes.za.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