From: "Gerhard TAEUBL" <Gerhard.TAEUBL@frequentis.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: MPC860(T) uart SCCs
Date: Tue, 18 Sep 2001 13:02:06 +0200 [thread overview]
Message-ID: <sba745ea.073@mail.frequentis.com> (raw)
Hallo!
Iwork with an custom board MPC860T kernel 2.4.5. I will use all 4 SCC as uart RS485/RS232. The problem is, that SCC1 and SCC2 works fine and SCC3 and SCC4 not:
I mapped SCC1 to BRG1 (ttyS0) SCC2 to BRG2 (ttyS1)....
SCC3 and SCC4 doesn't generate any interrupt. If I write in a loop something to Port ttyS2 for example the driver fills the buffer set the Ready bit in the bd, and nothing else happens, no output. When the wrap happens the Ready bit is still set, and the program hangs up. It looks like the SCC won't send any data.
sicr is set to 0x1b120900 so I think there is no fault.
anyone any ideas?
Thanks for help
Gerhard
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-09-18 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 11:02 Gerhard TAEUBL [this message]
2001-09-20 7:23 ` MPC860(T) uart SCCs Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2001-09-20 9:35 Gerhard TAEUBL
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=sba745ea.073@mail.frequentis.com \
--to=gerhard.taeubl@frequentis.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).