From: "Young-Han, Kim" <yhkim@da-san.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: MPC 8xx as SPI slave...
Date: Wed, 26 Mar 2003 11:50:51 +0900 [thread overview]
Message-ID: <000b01c2f342$8347d830$337ceccb@dasan.com> (raw)
Hi!
If you have any experience for SPI slave on MPC 8xx,
please advice to me.
I will use the MPC 8xx as SPI slave, the SPI master is not MPC 8xx.
Currently, using the SPI interrupt for RX/TX on MPC 8xx.
The SPI write operation on SPI master is run very well.
But, SPI read operation on SPI master is not so good.
When SPI read operation on SPI master, the CPM of MPC 8xx
report the SPI TX interrupt as TX done.
But, the MPC 8xx SPI not transmit that data on SPI bus,
just transmit old TX data.
In second SPI read operation on SPI master, the MPC 8xx SPI
transmit previous data of TX BD.
It means that the MPC 8xx SPI not transmit the data on time.
I was checked with oscilloscope.
If you know the reason of this problem, please answer to me.
from
Young-Han, Kim
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-03-26 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 2:50 Young-Han, Kim [this message]
2003-03-26 7:03 ` MPC 8xx as SPI slave Wolfgang Denk
2003-03-26 9:44 ` Young-Han, Kim
2003-03-26 11:02 ` Wolfgang Denk
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='000b01c2f342$8347d830$337ceccb@dasan.com' \
--to=yhkim@da-san.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).