On 06/24/2010 03:20 PM, Timur Tabi wrote:
Timur Tabi wrote:
I'd say that there are plenty of unknown issues with this driver/hardware.
For some reason, QE UART is just unreliable. I've had several people try to
use the QE for UART, and almost everyone has problems with it.
I finally got in to
Timur Tabi wrote:
> I'd say that there are plenty of unknown issues with this driver/hardware.
> For some reason, QE UART is just unreliable. I've had several people try to
> use the QE for UART, and almost everyone has problems with it.
I finally got in touch with one of the other development
>> Also in the current Linux kernel, there is a dependence on the
>> correctness
>> of the "brg-frequency" property from the dts. Look up above
>> qe_setbrg() at
>> the qe_get_brg_clk() function. Before the return (there are multiple
>> return
>> points) printk the brg_clk being returned. That m
On 06/22/2010 01:01 PM, Chuck Meade wrote:
What BRGs did you choose for tx and rx?
BRG1& BRG2
OK
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 th
>> What BRGs did you choose for tx and rx?
>
> BRG1 & BRG2
OK
>> 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
On 06/22/2010 12:14 PM, Chuck Meade wrote:
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 beca
>> 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 U
On 06/22/2010 09:53 AM, Chuck Meade wrote:
Sure. Go to opensource.freescale.com/firmware and download (for your
MPC8358)
the 8360 soft UART mode microcode patch. You will need to know if
your CPU
is a 2.0 or 2.1 silicon, since there is a different microcode patch
for each.
Then in the kernel c
>> Sure. Go to opensource.freescale.com/firmware and download (for your
>> MPC8358)
>> the 8360 soft UART mode microcode patch. You will need to know if
>> your CPU
>> is a 2.0 or 2.1 silicon, since there is a different microcode patch
>> for each.
>>
>> Then in the kernel config I believe I incl
On 06/22/2010 09:28 AM, Chuck Meade wrote:
Hi Gary,
According to the errata, it looks like the MPC8358 is subject to
erratum QE_UART6. You'll need to use soft UART mode and load the
microcode patch. Once that is done you will also need to use two
different BRG's, one for tx and one for rx, sin
Gary Thomas wrote:
> I'm still trying to get UCC UART to work on my MPC8358 with
> the 2.6.33.3 kernel.
>
> When I try to send data to the port, there is no output, not
> even any interrupts on the device. What I see is that the UART
> driver seems to initialize fine and pushes characters into
> th
>> Hi Gary,
>>
>> According to the errata, it looks like the MPC8358 is subject to
>> erratum QE_UART6. You'll need to use soft UART mode and load the
>> microcode patch. Once that is done you will also need to use two
>> different BRG's, one for tx and one for rx, since the soft UART mode
>> mic
On 06/22/2010 09:10 AM, Chuck Meade wrote:
On 06/22/2010 10:55 AM, Gary Thomas wrote:
I'm still trying to get UCC UART to work on my MPC8358 with
the 2.6.33.3 kernel.
When I try to send data to the port, there is no output, not
even any interrupts on the device. What I see is that the UART
dri
On 06/22/2010 10:55 AM, Gary Thomas wrote:
> I'm still trying to get UCC UART to work on my MPC8358 with
> the 2.6.33.3 kernel.
>
> When I try to send data to the port, there is no output, not
> even any interrupts on the device. What I see is that the UART
> driver seems to initialize fine and p
14 matches
Mail list logo
