From: Angelo Dureghello <angelo@sysam.it>
To: Greg Ungerer <gregungerer@westnet.com.au>,
Linux/m68k <linux-m68k@vger.kernel.org>
Cc: Finn Thain <fthain@telegraphics.com.au>
Subject: Re: coldfire uart question
Date: Tue, 17 Oct 2017 23:07:25 +0200 [thread overview]
Message-ID: <9fba01f2-9bf4-ecc2-b32e-2e75e203e189@sysam.it> (raw)
In-Reply-To: <077ccbca-027c-67fe-602e-7105d5c46edf@westnet.com.au>
Hi Greg and all,
On 16/10/2017 01:57, Greg Ungerer wrote:
> Hi Angelo,
>
> On 16/10/17 03:28, Angelo Dureghello wrote:
>> i was trying a file transfer with xmodem-1k
>> and uClinux "rx" on the mcf54415 stnmark2 board side.
>>
>> This using a recent mainline kernel:
>> / # cat /proc/version
>> uClinux version 4.14.0-rc4stmark2-001-00118-g811fdbb62a9d
>> / #
>>
>> So, as per xmodem-1k, i send 3 bytes header,
>> a 1024 bytes block, and 2 bytes crc16. But "rx" timeouts
>> waiting the block.
>>
>> Adding some traces to "rx", it timeouts since some bytes
>> (5 to 10) randomly positioned in the block are not received.
>> Of course they have been sent (scope checked).
>
> Check if you are getting overruns on the port:
>
> cat /proc/tty/driver/mcf
thanks, yes, you are right
/ # cat /proc/tty/driver/mcf
serinfo:1.0 driver revision:
0: uart:ColdFire UART mmio:0xFC060000 irq:90 tx:4047 rx:1057 oe:8 RTS|DTR|CD
1: uart:ColdFire UART mmio:0xFC064000 irq:91 tx:0 rx:0 CD
2: uart:ColdFire UART mmio:0xFC068000 irq:92 tx:0 rx:0 CD
3: uart:ColdFire UART mmio:0xFC06C000 irq:93 tx:0 rx:0 CD
/ #
I am at 115200,n,8,1 now.
I checked the u-boot driver and there is no interrupt handler,
only a coldfire_serial_getc checking USR_RXRDY.
Could the RxFIFO_Full interrupt flag be of any help ?
>
> Regards
> Greg
>
>
Regards,
Angelo
>
>> The same 1024 bytes transfer in u-boot (y-modem)
>> always succeed.
>>
>> Since mcf54415 has a 4 slots RX fifo UART, i was wondering
>> if the mcf.c uart driver is not fast enough to read the data,
>> or, where the "linux" limitation could be.
>>
>> Regards,
>> Angelo Dureghello
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
prev parent reply other threads:[~2017-10-17 21:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 17:28 coldfire uart question Angelo Dureghello
2017-10-15 23:08 ` Finn Thain
2017-10-17 21:18 ` Angelo Dureghello
2017-10-18 0:06 ` Finn Thain
2017-10-18 6:37 ` Geert Uytterhoeven
2017-10-18 7:05 ` Angelo Dureghello
2017-10-18 8:15 ` Finn Thain
2017-10-18 7:12 ` Greg Ungerer
2017-10-18 7:19 ` Angelo Dureghello
2017-10-18 7:35 ` Philippe De Muyter
2017-10-15 23:57 ` Greg Ungerer
2017-10-17 21:07 ` Angelo Dureghello [this message]
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=9fba01f2-9bf4-ecc2-b32e-2e75e203e189@sysam.it \
--to=angelo@sysam.it \
--cc=fthain@telegraphics.com.au \
--cc=gregungerer@westnet.com.au \
--cc=linux-m68k@vger.kernel.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