From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: "eCos Discuss" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Serial communications
Date: Wed, 08 Jul 2009 16:27:00 -0000 [thread overview]
Message-ID: <PGEAIGBPLOMOJDAPCOJHKEKANEAB.pderocco@ix.netcom.com> (raw)
In-Reply-To: <24391031.post@talk.nabble.com>
> From: grahamlab
>
> The board does not reset and has an indepedant power supply
Do you have another identical board lying around? If so, try it. Hardware
occasionally does fail.
Beyond that, I think I would be looking for evidence that the system is
freezing momentarily. A scope can be helpful for this, especially if you
populate your code with things that pulse various unused port pins at
various points. That's generally better than diagnostic output, because it
takes nearly zero time.
Basically, though, this sounds like it needs hands-on debugging, not
speculation by other people. You may need to write your own tests. Heck, in
the end, you may need to write your own serial driver.
--
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-08 16:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26049960.287991246881965794.JavaMail.nabble@isper.nabble.com>
2009-07-06 12:50 ` [ECOS] " Nick Garnett
2009-07-07 7:00 ` [ECOS] " grahamlab
2009-07-07 8:15 ` [ECOS] " John Dallaway
2009-07-07 9:29 ` [ECOS] " grahamlab
2009-07-07 10:23 ` Nick Garnett
2009-07-07 11:04 ` grahamlab
2009-07-07 16:46 ` grahamlab
2009-07-08 9:25 ` Daniel Morris
2009-07-08 10:05 ` grahamlab
2009-07-08 11:01 ` Sergei Gavrikov
2009-07-08 11:41 ` grahamlab
2009-07-08 11:52 ` Sergei Gavrikov
2009-07-08 12:58 ` grahamlab
2009-07-08 16:27 ` Paul D. DeRocco [this message]
2009-07-09 7:47 ` grahamlab
2009-07-09 9:07 ` Nick Garnett
2009-07-10 10:43 ` grahamlab
2009-07-10 12:08 ` Sergei Gavrikov
2009-07-10 12:31 ` Nick Garnett
2009-07-10 12:55 ` grahamlab
2009-07-10 13:17 ` Nick Garnett
2009-07-14 11:06 ` Bessemer
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=PGEAIGBPLOMOJDAPCOJHKEKANEAB.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).