From: Andreas Stenius <andreas.stenius@astekk.se>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Serial communication issues
Date: Wed, 06 Feb 2013 09:47:00 -0000 [thread overview]
Message-ID: <CABCxKrfOr8-AAKEq3qwU-rJrsxBZ9r5anr=Krs1baUvvdtH=Dg@mail.gmail.com> (raw)
Hi,
I've been struggling with this for a few days now, and are initially
looking for anyone that recognizes any of this, or maybe have some
insights to what may be going on.
I'm working on a project based on a custom hardware fitted with a
AT91R40008, at 40Mhz.
The application is debugged using GDB connected with a JTAG dongle to
the board, and this works fine.
However, when the application is running from flash using a ROM
configuration, I have issues on /dev/ser1.
I have a console running on /dev/termios0 (connected to /dev/ser0),
and this runs fine in both RAM and ROM.
The issues on ser1 is that after I send a request (two bytes) the
reply is not always received correctly (or at all, not sure which
yet).
However, whenever I enable some diagnostic printouts around the calls
to cyg_io_write/cyg_io/read, it works ok, so as soon as I affect the
timing of the send/read calls, it works.
The reply is always consistent and correct on the wire (confirmed with
oscilloscope).
I have setup ser1 to operate in a non-blocking mode (and no termios on
this channel).
I'll dig in deeper trying to solve this, just wanted to throw this out
here in case someone recognizes any of this.. ;)
Oh, and running a eCos version from cvs, 2012-05-27.
//Andreas
--
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 reply other threads:[~2013-02-06 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 9:47 Andreas Stenius [this message]
2013-02-06 15:06 ` [ECOS] " Andreas Stenius
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='CABCxKrfOr8-AAKEq3qwU-rJrsxBZ9r5anr=Krs1baUvvdtH=Dg@mail.gmail.com' \
--to=andreas.stenius@astekk.se \
--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).