From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Rx FIFO: more than 64 bytes receive error
Date: Sat, 29 Dec 2012 14:58:37 +0100 [thread overview]
Message-ID: <20121229145837.45e33b60@lilith> (raw)
In-Reply-To: <CAB-o9pjeLvV+N+Lb=_0ryc+YLjAiAXtDdjcfq0pFE6wCw2J+vg@mail.gmail.com>
Hi lokesh,
On Sat, 29 Dec 2012 17:01:35 +0530, lokesh nijalinge
<lokesh1kumar2nijalinge@gmail.com> wrote:
> Hi,
>
> I am using the arm processor for my project and need to receive around 1K
> bytes of data over UART. I am able to receive only 64 bytes at U-boot,
> which is the UART RX FIFO size. After receiving the 64 bytes i am not
> getting any data. I read the Technical Reference Manual, which says the if
> more than FIFO size data is received then data will be lost instead
> of overwriting.
>
> Please let me know whether i need to configure any UART registers to
> achieve more than 64 bytes.
> *Details of the project:*
> Processor : DM3730 from Texas instruments -OMAP3 ARM Cortex
> UART device : NS16550
>
> The default code having the UART initialization sequence posted below does
> not seem to take care of the handling of more than 64 bytes of RX data.
Hmm... I can tell any U-Boot receives and correctly processes a lot more
than 64 bytes without any issue; I routinely throw a lot more than this
at the few U-Boot's I have lying around, all of which use NS16550-like
serials. I even sometimes 'loads' a payload of several hundred bytes to
some megs, without any issue.
However, while 'loads' itself can handle very large serial input, the
serial driver in itself will never handle more than the FIFO depth:
the 'loads' command handler has to read from the driver frequently in
order to avoid an overload.
In your case, you did not describe (or did I miss it?) what it is that
*uses* the received bytes, and how and when these received bytes are
read from the driver. Can you elaborate on this?
> *Changes done by us to get the Data from RX fifo. *
Please show such changes as a patch (made with got format-patch or at
least git diff) -- with '[RFC]' in the message subject so that we know
it is not a submission for inclusion into U-boot.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2012-12-29 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 11:31 [U-Boot] Rx FIFO: more than 64 bytes receive error lokesh nijalinge
2012-12-29 13:58 ` Albert ARIBAUD [this message]
2012-12-31 9:29 ` lokesh nijalinge
2013-01-03 13:42 ` Albert ARIBAUD
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=20121229145837.45e33b60@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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