From: Brett Delmage <Brett.Delmage@twobikes.ottawa.on.ca>
To: ECOS mailing list <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Do any of the ARM LPCxxxx serial functions work?
Date: Fri, 21 Apr 2006 20:29:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0604211608570.12142@pannier.canbike.ca> (raw)
I wonder if anyone actually has interrupt-driven serial output working on
any of the ARM Philips LPCxxxx based targets?
I am not getting serial output to start.
The problem I see is in
ser_16x5x.c pc_serial_start_xmit()
The Philips docs state that the UART will not generate a Transmit Holding
Register Empty interrupt unless it has had at least two charcters put into
the FIFO. Then it will set the interrupt flag on the transition to empty.
However Ecos just enables the THRE interrupt, which is insufficient to
cause an initial interrupt.
Brett
--
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:[~2006-04-21 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 20:29 Brett Delmage [this message]
2006-04-24 10:16 ` [ECOS] " Daniel Néri
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=Pine.LNX.4.61.0604211608570.12142@pannier.canbike.ca \
--to=brett.delmage@twobikes.ottawa.on.ca \
--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).