From: Eran Duchan <pavius@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Non-console UART issues with 8xx
Date: Fri, 15 Apr 2011 02:52:22 +0300 [thread overview]
Message-ID: <BANLkTik=ivFpWQEhqrVnYfr2LS4HSnTDuA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Hey list
I have a custom MPC875 board running 2.6.37. SMC1 is the console, SCC4 is a
general purpose UART (DTS is set up accordingly). No hardware or software
flow control for either.
The issue is simple: the non-console UART transmits garbled characters at
the end of the transmission. For example, set up SMC1 to console (works
perfect) and SCC4 as non-console, run stty -F /dev/ttyCPM1 19200 raw and
then echo -n 1234567890 > /dev/ttyCPM1 - transmission may be something like
"1234567ø". Set the SCC4 as console (same baud rates) and the problem is
reversed (SCC4 works perfect, SMC1 transmit garbled).
Rx direction seems fine, after some rudementary testing.
I dived into the code and see that the console UART has a completely
different initialization sequence than the non-console UART. Short of diving
into this ancient CPM architecture - does anyone have an idea?
Thanks
Eran
[-- Attachment #2: Type: text/html, Size: 1159 bytes --]
next reply other threads:[~2011-04-14 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 23:52 Eran Duchan [this message]
2011-04-15 20:41 ` Non-console UART issues with 8xx Scott Wood
2011-04-16 6:40 ` Eran Duchan
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='BANLkTik=ivFpWQEhqrVnYfr2LS4HSnTDuA@mail.gmail.com' \
--to=pavius@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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).