All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Meade <chuck@ThePTRGroup.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: UCC UART
Date: Tue, 22 Jun 2010 14:14:56 -0400	[thread overview]
Message-ID: <4C20FDA0.5050208@ThePTRGroup.com> (raw)
In-Reply-To: <4C20F671.9090605@mlbassoc.com>

>> I did not do that, and I have it running here.  I will say though that I
>> hardcoded the driver to run in soft UART mode.  You will need to at least
>> add the appropriate line to your dts to get the driver to operate in
>> Soft UART mode.
>>
>> I hardcoded mine because I had to backport this UCC UART driver to an
>> older
>> Linux kernel, and that kernel was from before dts existed.
>>
>> Add whatever you need to your dts to make it run in soft UART mode and
>> get
>> the firmware loaded.  Use two different BRGs for tx and rx.  Make sure
>> your
>> BRG choice is valid for your UCC3.
>>
>> I believe that the UCC UART support has not had too much use so far, but
>> I do have it working (in that older kernel after backporting).
> 
> I've done all this but sadly the behaviour is the same :-(
> 
> Any ideas what I might be missing?

Check your setup of the UCC3 pins for UART mode.  Make sure you either have
the UCC3 CD, CTS, RTS pins at the correct levels, or deconfigure those pins
(set them up as GPIOs).  Just verify every pin is properly set up for UCC3.
The UCC3 TxD and RxD signals must be set up properly.

What BRGs did you choose for tx and rx?

Get a scope on the UCC3 tx pin and try to output some chars.  See if there is
any digital activity on that pin at all.  If you are looking at a terminal for
output, there are too many things that could be wrong between that tx pin and
your display (e.g. level translation issue, null modem issue, baud incompatibility,
terminal program set for XON/XOFF or HW flow control and UART not set up compatibly).

For now get the probe directly on the CPU's UCC3 Tx pin, output chars and see
if there is any activity.

Chuck Meade
chuck@ThePTRGroup.com

  reply	other threads:[~2010-06-22 18:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 14:55 UCC UART Gary Thomas
2010-06-22 15:06 ` Tabi Timur-B04825
2010-06-22 15:10 ` Chuck Meade
2010-06-22 15:14   ` Gary Thomas
2010-06-22 15:28     ` Chuck Meade
2010-06-22 15:46       ` Gary Thomas
2010-06-22 15:53         ` Chuck Meade
2010-06-22 17:44           ` Gary Thomas
2010-06-22 18:14             ` Chuck Meade [this message]
2010-06-22 18:41               ` Gary Thomas
2010-06-22 19:01                 ` Chuck Meade
2010-06-22 21:19                   ` Gary Thomas
2010-06-22 21:27                     ` Chuck Meade
     [not found] ` <4C20D162.2020302@freescale.com>
2010-06-24 21:20   ` Timur Tabi
2010-06-25  0:49     ` Gary Thomas

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=4C20FDA0.5050208@ThePTRGroup.com \
    --to=chuck@theptrgroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.