From: harri.siirtola@vtt.fi
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Simple serial interrupt question (Atmel AT91)
Date: Sun, 10 Jun 2001 23:44:00 -0000 [thread overview]
Message-ID: <3.0.32.20010611094314.00984ce0@vttmail.vtt.fi> (raw)
I have my interrupt-driven serial I/O almost working. It uses a DSR routine
and is modified from PID serial implementation. I try to send a short
string to this port (AT91X40 port 1, secondary) with cyg_io_write(). The
problem is:
Running without breaks results to the first two characters to appear at the
port. Setting a breakpoint to my xxx_serial_putc() gives the whole string,
char by char of course.
So, what does the breakpoint execution do (with interrupt acknowledge or
something else) that I should add to my implementation?
BTW, trying to send the string in a loop, xxx_serial_start_xmit() seems to
be called once for each cyg_io_write() call but xxx_serial_stop_xmit() is
called once before the first cyg_io_write() call. What's the role of these
functions?
Thanks,
Harri
next reply other threads:[~2001-06-10 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-10 23:44 harri.siirtola [this message]
2001-06-21 3:35 ` Jonathan Larmour
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=3.0.32.20010611094314.00984ce0@vttmail.vtt.fi \
--to=harri.siirtola@vtt.fi \
--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).