From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: "eCos Discuss" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Simple serial comms
Date: Fri, 03 Jul 2009 07:43:00 -0000 [thread overview]
Message-ID: <PGEAIGBPLOMOJDAPCOJHGEDPNEAB.pderocco@ix.netcom.com> (raw)
In-Reply-To: <24318811.post@talk.nabble.com>
> From: grahamlab
>
> I have a standard ecos - I have not changed many settings
> where is the driver code located?
packages/devs/serial/cortexm/stm32/v3_0/
> what could be a source of spurious interrupts?
Depends upon what else you're doing besides receiving bytes. Perhaps
something to do with wherever the bytes are going? Any other threads doing
anything else?
What bit rate are you using? What clock rate are you running the CPU at?This
isn't a screamingly fast CPU, but I would think it would handle
115200bps--I've done that speed on a slow Atmel ARM7 chip, and that driver's
ISR and DSR code looks even less efficient.
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.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
next prev parent reply other threads:[~2009-07-03 7:43 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
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 [this message]
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=PGEAIGBPLOMOJDAPCOJHGEDPNEAB.pderocco@ix.netcom.com \
--to=pderocco@ix.netcom.com \
--cc=ecos-discuss@ecos.sourceware.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 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).