From: David Roethig <droethig@cipher.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] problem with generic serial driver?
Date: Thu, 19 May 2005 08:43:00 -0000 [thread overview]
Message-ID: <428BCC08.8060804@cipher.com> (raw)
I am using (as of recently) the generic serial driver
package (16x5x compatible serial device drivers).
The application was sending data to the port using the
file i/o interface:
/* output string to serial port */
err = cyg_io_write( serHandle, writeBuffer, length );
Nothing came out the serial port! That is, until, the app
output a 'diag_printf()'. That was a head-scratcher until
looking at the pc_serial_start_xmit() routine, I noticed
that the trasmitter wasn't being 'kicked' with a character
to the transmit register.
// Enable the transmitter on the device
static void
pc_serial_start_xmit(serial_channel *chan)
{
pc_serial_info *ser_chan = (pc_serial_info *)chan->dev_priv;
cyg_addrword_t base = ser_chan->base;
cyg_uint8 _ier;
HAL_READ_UINT8(base+REG_ier, _ier);
_ier |= IER_XMT; // Enable xmit interrupt
HAL_WRITE_UINT8(base+REG_ier, _ier);
/* kick transmitter */ // **!! added !!**
(chan->callbacks->xmt_char)(chan); // **!! added !!**
}
My questions:
1) is the generic serial package still being used?
2) is this a bug or are things configured incorrectly?
Thanks
Dave
--
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:[~2005-05-18 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 8:43 David Roethig [this message]
2005-05-19 12:16 ` Nick Garnett
2005-05-19 20:01 ` David Roethig
2005-05-19 23:15 ` 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=428BCC08.8060804@cipher.com \
--to=droethig@cipher.com \
--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).