From: Nick Garnett <nickg@ecoscentric.com>
To: "damien millescamps" <damien.millescamps@gmail.com>
Cc: "Chris Zimman" <czimman@bloomberg.com>,
"andrew wiggin" <end3er@gmail.com>,
ecos-devel@ecos.sourceware.org
Subject: Re: Serial VS Diagnostic interface
Date: Wed, 14 Jan 2009 14:19:00 -0000 [thread overview]
Message-ID: <m34p02rmw1.fsf@xl5.calivar.com> (raw)
In-Reply-To: <587ce2cd0901140529h562f0daasa0d8dfde252249bf@mail.gmail.com>
"damien millescamps" <damien.millescamps@gmail.com> writes:
> On Wed, Jan 14, 2009 at 2:24 PM, Chris Zimman <czimman@bloomberg.com> wrote:
> >> Actually as it just inline code. I have already checked it is
> >> correctly included. Maybe I should have been more explicit: Is there
> >> anything to ensure the HW serial driver is correctly initialized ?
> >> Where should pc_serial_lookup() be called in a normal behavior ?
> >
> > If you can build the serial tests and they pass, you should be in good shape.
> > Alternatively, if opening "/dev/ser0" succeeds, you're good to go.
> >
>
> opening /dev/ser0 results in an error. Now that I know it should
> normally work, I can start to instrument a little bit to find out why
> it doesn't work for me.
The most common problem with serial devices is not enabling
CYGPKG_IO_SERIAL_DEVICES. Obviously you also have to include the
CYGPKG_IO_SERIAL package too.
Note that AT91 serial devices cannot be shared between diagnostics and
serial drivers. So if you want to continue using diagnostics on a
particular UART, you need to disable it for the drivers.
--
Nick Garnett eCos Kernel Architect
eCosCentric Limited http://www.eCosCentric.com The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No: 4422071
next prev parent reply other threads:[~2009-01-14 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 19:58 andrew wiggin
2009-01-14 0:21 ` Chris Zimman
2009-01-14 13:03 ` andrew wiggin
2009-01-14 13:25 ` Chris Zimman
2009-01-14 13:30 ` damien millescamps
2009-01-14 14:19 ` Nick Garnett [this message]
2009-01-14 14:58 ` damien millescamps
2009-01-14 15:10 ` Nick Garnett
2009-01-16 16:20 ` andrew wiggin
2009-01-16 16:23 ` Chris Zimman
2009-01-16 17:35 ` Jonathan Larmour
2009-01-16 19:02 ` andrew wiggin
2009-01-14 13:45 ` Chris Zimman
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=m34p02rmw1.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=czimman@bloomberg.com \
--cc=damien.millescamps@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=end3er@gmail.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).