public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: grahamlab <graham.labdon@cranems.co.uk>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Simple serial comms
Date: Thu, 02 Jul 2009 15:36:00 -0000	[thread overview]
Message-ID: <m33a9fjdwa.fsf@xl5.calivar.com> (raw)
In-Reply-To: <24307911.post@talk.nabble.com>

grahamlab <graham.labdon@cranems.co.uk> writes:

> 
> >How are you sending the bytes?
> I can also make my program behave like this. The problen arises when I send
> the data in a chunk > 128 bytes - either using minicom or another program.

In that case I suspect that enabling flow control might be
necessary. If you can use harware flow control that would be best,
otherwise use software flow control.


-- 
Nick Garnett                                       eCos Kernel Architect
eCosCentric Limited    http://www.eCosCentric.com       The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.      Tel: +44 1223 245571
Registered in England and Wales:                         Reg No: 4422071


-- 
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:[~2009-07-02 15:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 12:48 grahamlab
2009-07-02 13:25 ` Simon Kallweit
2009-07-02 13:28   ` grahamlab
2009-07-02 14:24 ` Nick Garnett
2009-07-02 14:36   ` grahamlab
2009-07-02 15:36     ` Nick Garnett [this message]
2009-07-03  5:56       ` grahamlab
2009-07-03  6:18         ` Paul D. DeRocco
2009-07-03  6:46           ` grahamlab
2009-07-03  7:19             ` Paul D. DeRocco
2009-07-03  7:23               ` grahamlab
2009-07-03  7:43                 ` Paul D. DeRocco
2009-07-03  9:38         ` Nick Garnett
2009-07-03 12:30           ` grahamlab
2009-07-03 12:45             ` Nick Garnett
2009-07-03 13:36               ` grahamlab
2009-07-03 15:09                 ` Nick Garnett

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=m33a9fjdwa.fsf@xl5.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=graham.labdon@cranems.co.uk \
    /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).