From: Greg Ungerer <gregungerer@westnet.com.au>
To: Angelo Dureghello <angelo@sysam.it>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: coldfire uart question
Date: Mon, 16 Oct 2017 09:57:01 +1000 [thread overview]
Message-ID: <077ccbca-027c-67fe-602e-7105d5c46edf@westnet.com.au> (raw)
In-Reply-To: <1f18ad0d-d147-5c64-ad65-a4bc545d4bff@sysam.it>
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
Regards
Greg
> 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
>
next prev parent reply other threads:[~2017-10-15 23:57 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 [this message]
2017-10-17 21:07 ` Angelo Dureghello
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=077ccbca-027c-67fe-602e-7105d5c46edf@westnet.com.au \
--to=gregungerer@westnet.com.au \
--cc=angelo@sysam.it \
--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 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.