public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: Uart missing chars when in Release
Date: Sun, 27 Jan 2008 05:14:00 -0000	[thread overview]
Message-ID: <fnh3uj$vtt$1@ger.gmane.org> (raw)
In-Reply-To: <OBEELMDOHGDFDEMJCJCJMENMMIAA.laurie.gellatly@netic.com>

On 2008-01-27, Laurie Gellatly <laurie.gellatly@netic.com> wrote:

> 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?

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).

> 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.

> I've checked the ecc files and made then as close as possible.
> I have noticed, that for some strange reason, telling eCos to
> disable the FIFO seems to help though its does not seem to set
> it up or make use of it.
>
> Any suggestions on what to try next?

Are you seeing rx overrun errors?  If the rx end is running too
slowly for the data rate, you would see rx overrun errors.

-- 
Grant Edwards                   grante             Yow!  What UNIVERSE is
                                  at               this, please??
                               visi.com            


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2008-01-27  5:14 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   ` Grant Edwards [this message]
2008-01-27  6:46     ` [ECOS] " Laurie Gellatly
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='fnh3uj$vtt$1@ger.gmane.org' \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.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).