From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: flash AMD
Date: Thu, 26 Jun 2003 12:51:49 -0400 [thread overview]
Message-ID: <5.1.0.14.2.20030626124723.02159eb0@falcon.si.com> (raw)
In-Reply-To: <00053337.C22236@netcourrier.com>
At 05:10 PM 6/26/2003 -0400, greggiraud@netcourrier.com wrote:
>Hi, I try to use my flash on my custom card. It's like a MPC8260ADS.
>The flash is the AMD AM29DL323GB. I read some source from ppcboot with
>am29dl323b. And for the moment I just want to ask the flash the
>manufacturor id.
>I try the source that I have found, but it doesnt function. When I make the
>autodelect sequence, and then read the first word, normally I would read the
>manufacturor ID, but I read the word that is the flash.
>
>So is someone has used this flash? Have you got source or ideas about that?
>
>Nota: I initialisaze the flash when ppcboot is relocated in the ram.
>grego
>greggiraud@netcourrier.com
The flash control sequences are merely memory reads and write. I usually
use a debugger to do the flash write sequences by hand (per the
manufacturer's data sheet) to put the flash in "read ID" mode and then read
it out, again via the debugger. This gives me the best way to try all the
potential combinations (bus width, chip width, etc.) and figure out what
the proper memory operations are to make it work. Even when I think I know
what the configuration is, I usually do the hand operations to verify that
it really works (and have been surprised more than once :-).
Note that you can very easily test your understanding of the erase and
write algorithms this way too.
gvb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-06-26 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00053337.C22236@netcourrier.com>
2003-06-26 16:51 ` Jerry Van Baren [this message]
2003-06-26 15:10 flash AMD greggiraud
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=5.1.0.14.2.20030626124723.02159eb0@falcon.si.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).