From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] minimum bdi config to read flash on 85xx
Date: Thu, 06 Sep 2007 15:06:29 -0700 [thread overview]
Message-ID: <46E079E5.5000102@ovro.caltech.edu> (raw)
In-Reply-To: <50d8dde80709061403t576d0720lf1461bd6ee9e6730@mail.gmail.com>
Hi Luiz,
> This is Luiz and I'm working with Robert in this project.
Glad to hear he's got someone to grow grey hairs
with ... if it hasn't fallen out yet.
> Actually, I'm a hardware guy.
So am I ... this week :)
> I read your messages and it seems you're right. However,
> before introducing these changes on the board, we decided
> to verify all flash circuitry and we noticed the following:
>
> CE# is OK!
> WE# is OK!
> OE# is OK!
>
> We verified it using a scope and triggering CE# pin. After that, we
> tried to write to flash through BDI2000 using "mm" command. Again with a
> scope we checked each address line and apparently everything is fine
> with the address.
I think that after the processor boots LAD[0:31] activate
for each address access, its only during boot that LAD[27:31]
do not toggle, and you have to use LA[27:31]. So its
that confirmation of the address toggles in this case just
confirms that the LAD[27:31] bits toggle.
On the bright-side, it sounds like you have the bit
ordering correct ([27:30])... just not the right bits
(LAD vs LA).
> We also checked the data being written, and it's ok
> too. After that, in order to validate the written, we read the same
> address we had just written. But we got a different value. Therefore we
> are not writing correctly to flash.
Have you tried using simple CFI flash commands;
read the manufacturer ID, read the device ID,
read the sector protection? Don't bother with
BDI Flash commands just yet, just use memory
read/write commands.
> Ok, after all, we fixed our board following your tips.
> We connected LA[27:30] to A[3:0] and A[4:25] to LBA[26:5].
> But we got the same bad result. I mean we read a wrong data.
>
> After, we changed flash access time, decreasing it. And the
> problem persisted. We changed flash chip and nothing happened.
>
> Actually I'm afraid because I can't see what else we can verify
> on hardware.
>
> My opinion is we have mistakes on configuration file. I'm not sure if we
> are configuring all registers correctly.
>
> Do you think it would be helpful if I send you our flash schematic and
> our configuration file?
Sure, no guarantees, you can send me a copy, or send
a link to the group. I'm not too knowledgeable on BDI
config files yet, as I don't have my custom hardware.
However, I have looked at a few hardware designs, so
perhaps I'll spot something on the schematic. The
peripherals seem to be pretty similar between the
PowerQUICCs, so I'll dig up a working configuration
file, and look at the difference in register settings.
What is your Flash? Eg. if its say a Spansion device,
do you have WP# tied high, BYTE# tied low/high, etc?
Are there any address pins left floating?
Do you have a logic analyzer available? If you did,
you'd be able to look at the flash controls and write-data
and convince yourself that your Flash programming
sequence was correct.
The best advice at the moment, is to access your Flash
configuration using manual read/write sequences.
Cheers,
Dave
next prev parent reply other threads:[~2007-09-06 22:06 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 18:11 [U-Boot-Users] minimum bdi config to read flash on 85xx robert lazarski
2007-09-04 18:26 ` David Hawkins
2007-09-04 19:45 ` Ben Warren
2007-09-04 20:50 ` robert lazarski
2007-09-04 21:12 ` Ben Warren
2007-09-04 21:15 ` David Hawkins
2007-09-05 15:05 ` robert lazarski
2007-09-05 16:35 ` David Hawkins
2007-09-05 19:53 ` robert lazarski
2007-09-05 21:19 ` David Hawkins
2007-09-06 21:03 ` Luiz Neto
2007-09-06 21:20 ` Ben Warren
2007-09-06 22:12 ` David Hawkins
2007-09-06 22:06 ` David Hawkins [this message]
2007-09-07 1:41 ` Luiz Neto
2007-09-07 2:00 ` David Hawkins
[not found] ` <50d8dde80709072035j3c066e81wab5216e78d47f89c@mail.gmail.com>
2007-09-08 3:46 ` David Hawkins
2007-09-12 17:23 ` robert lazarski
2007-09-12 18:00 ` David Hawkins
2007-09-12 18:13 ` Jerry Van Baren
2007-09-12 18:23 ` David Hawkins
2007-09-12 18:29 ` David Hawkins
2007-09-12 18:39 ` Jerry Van Baren
2007-09-12 18:44 ` David Hawkins
2007-09-12 19:19 ` robert lazarski
2007-09-12 19:41 ` David Hawkins
2007-09-12 20:06 ` Jerry Van Baren
2007-09-12 20:16 ` David Hawkins
2007-09-12 20:40 ` Jerry Van Baren
2007-09-12 21:39 ` David Hawkins
2007-09-14 18:21 ` robert lazarski
2007-09-14 18:34 ` Jerry Van Baren
2007-09-14 18:43 ` Ben Warren
2007-09-14 19:12 ` David Hawkins
2007-09-14 20:05 ` robert lazarski
2007-09-14 20:14 ` Ben Warren
2013-05-27 13:01 ` [U-Boot] " Monica
2013-05-27 13:37 ` Fabio Estevam
2013-05-28 5:35 ` Monica
2007-09-14 20:16 ` [U-Boot-Users] " Jerry Van Baren
2007-09-14 20:34 ` Leon Woestenberg
2007-09-14 21:04 ` Scott Mann
2007-09-14 20:31 ` David Hawkins
2007-09-06 22:43 ` Clemens Koller
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=46E079E5.5000102@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--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