linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Chuck Partridge" <Chuck_Partridge@amx.com>
To: <Dmitriy.Zavin@infineon.com>
Cc: "<" <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: SCC2 and SCC3 serial ports on RPX Classic (MPC860)
Date: Wed, 26 Mar 2003 16:21:25 -0600	[thread overview]
Message-ID: <se81d39f.013@amx.com> (raw)


Is this string sent by a program loaded via insmod and busybox?

I had a problem with drivers loaded as modules when using busybox.  The wrong strings would be sent when I did printk.  It drove me nuts for days.  I installed the true version of insmod and all worked fine.

Maybe it helps,

Chuck

>>> <Dmitriy.Zavin@infineon.com> 03/26/03 04:11PM >>>

Wolfgang,

What I mean by "not random" is this:
I write a string to /dev/tts/1, which will cause another string to be printed on the remote console. If I repeat this 50 times, the same messed up string will appear.

Thanks.

I hope that answers the question.

--Dima

>In message
><FD90897E35ABD311AE0E0008C7E6404A07192EDE@ca02exch4.sjc.infineo
>n.com> you wrote:
>>
>> I compiled the 2.4.7 kernel (from TimeSYS) with SCC2 and
>SCC3 enabled for IO. I have a break-out board where I manually
>hook into the TXD/RXD/GND pins (Port A, pins 12/13). Now, I'm
>sending a pattern (FOOOOOO) from the SBC to /dev/tts/1 (SCC2) which is
>> connected to a windows box on COM1. All I get on COM1 is
>garbage. But its not random. I made sure to set all the
>baud/stop bits/parity manually through IOCTL calls to make
>sure its right, but still no go. And SCC3 (/dev/tts/2) is
>completely unresponsive
>
>What exactly do you mean with "garbage, but not completely random"?
>
>Is it the ordinary type of "line noise" as you get when the baud rate
>is wrong, or do you get  valid  characters,  but  only  every  second
>character  gets  output?  If  you  get  every  second character, this
>usually means that your console port is misconfigured.
>
>Best regards,
>
>Wolfgang Denk
>
>--
>Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
>Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
>Always try to do things in chronological order; it's  less  confusing
>that way.
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-03-26 22:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 22:21 Chuck Partridge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 22:38 SCC2 and SCC3 serial ports on RPX Classic (MPC860) Dmitriy.Zavin
2003-03-26 23:57 ` Wolfgang Denk
2003-03-26 19:17 Dmitriy.Zavin
2003-03-26 20:27 ` Dan Malek
2003-03-26 21:54 ` 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=se81d39f.013@amx.com \
    --to=chuck_partridge@amx.com \
    --cc=Dmitriy.Zavin@infineon.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).