From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: "Grant Edwards" <grante@visi.com>, <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Re: Uart missing chars when in Release
Date: Sun, 27 Jan 2008 06:46:00 -0000 [thread overview]
Message-ID: <OBEELMDOHGDFDEMJCJCJAENOMIAA.laurie.gellatly@netic.com> (raw)
In-Reply-To: <fnh3uj$vtt$1@ger.gmane.org>
Hi Grant,
>> I have an LPC2112 UART0 running at 117K (2112 does not have
>> the fractional divider, 2112/01 does).
>>
>> I'm sending it 100 characters (1 to 100) at that baud and
>> printing out the characters after they have all arrived.
>Arrived where? Sending from where?
Coming from a LPC2103 not running eCos.
>Is eCos running on both the sending and receiving device? Are
>the "missing" caracters actually on the wire or not? (That
>would tell you whether it's the sender's fault or the
>receiver's fault).
The missing chars are on the wire - I've snooped them.
>> I get consistently 100 chars arriving when the app is run in
>> RAM under debug in eclipse. When running the Release code from
>> flash, about 30% of the time I get less than 100. By less I
>> mean up to 14 characters less. The missing characters are
>> typically together in 1 or 2 bursts.
>>
>> I can't spot what is making the difference.
>I'm not familiar with your platform, but on many platforms
>running from flash can be much, much slower than running from
>RAM -- in some cases up to maybe 8-10X slower, but 4X slower is
>more typical. Flash often has much slower access times that
>RAM and is often narrower than RAM. 2X bus cycles with 4X
>access time can add up pretty fast.
The same platform also runs an Ethernet interface without problems.
10Mbit is quite a bit faster than 115K baud so I feel I can
probably discount that.
>Are you seeing rx overrun errors? If the rx end is running too
>slowly for the data rate, you would see rx overrun errors.
From what I've read, the OE gets cleared on each read of RBR.
How can I check on this? Is there a counter of OE and other errors
kept in eCos that I can access?
Thanks ...Laurie:{)
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-01-27 6:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 4:16 [ECOS] Re: Half Duplex RS485 wangcui
2008-01-26 20:41 ` Laurie Gellatly
2008-01-28 10:34 ` wangcui
2008-01-27 4:52 ` [ECOS] Uart missing chars when in Release Laurie Gellatly
2008-01-27 5:14 ` [ECOS] " Grant Edwards
2008-01-27 6:46 ` Laurie Gellatly [this message]
2008-01-27 9:54 ` Grant Edwards
2008-01-27 11:20 ` Laurie Gellatly
2008-01-27 15:55 ` Grant Edwards
2008-01-28 0:11 ` Laurie Gellatly
2008-01-28 2:37 ` Grant Edwards
2008-01-28 5:53 ` Laurie Gellatly
2008-01-28 15:58 ` Grant Edwards
2008-01-28 20:40 ` Grant Edwards
2008-01-29 23:35 ` Byron Jacquot
2008-02-06 9:35 ` Laurie Gellatly
2008-02-06 15:25 ` Grant Edwards
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=OBEELMDOHGDFDEMJCJCJAENOMIAA.laurie.gellatly@netic.com \
--to=laurie.gellatly@netic.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).