From: "Augustine Nebu Philips" <nebuphilips@eudoramail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 64-bit Data Flash Access Problem [MPC8245]
Date: Wed, 24 Sep 2003 12:04:41 -0500 [thread overview]
Message-ID: <PBEHCIIEFPBFGFAA@whowhere.com> (raw)
Hi
I have a set of 8 1GB data flash chips (Samsung) on an MPC8245 Ref. Board. These are on a 64-bit bus-mode.
-------DBUS_SIZ[0-1]:DBUS_SIZ[2] = 110b -------
All 8 chips are selected by a single chip select (RCS1). Trying a 32-bit read from the Data Address Location after giving the Command to Access the flash IDs, only 4 flashes on a common byte lane seem to be responding. 32-bit writes appear only on the DH[0-31] and not on DL[0-31].
I am not very clear as to:
(a) How do we perform writes to send out data out on
all 64-bits of the bus..?
(b) How would we ideally access 64-bit data through 32- bit reads..?
(c) Or must we *have* 64- bit read/write
instructions..?
many thanks in advance for any response ..
Regards
Nebu
Need a new email address that people can remember
Check out the new EudoraMail at
http://www.eudoramail.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-09-24 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 17:04 Augustine Nebu Philips [this message]
2003-09-24 18:13 ` 64-bit Data Flash Access Problem [MPC8245] Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2003-09-24 17:31 Steven Blakeslee
2003-09-24 17:34 Augustine Nebu Philips
[not found] <0000C657.C22236@eudoramail.com>
2003-09-24 17:43 ` Jerry Van Baren
2003-09-24 18:03 Steven Blakeslee
2003-09-24 18:07 Milliorn Gary-rxcr80
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=PBEHCIIEFPBFGFAA@whowhere.com \
--to=nebuphilips@eudoramail.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).