From: Sergei Gavrikov <w3sg@SoftHome.net>
To: Alexey Shusharin <mrfinch@mail.ru>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: diag_printf via serial port
Date: Thu, 31 May 2007 14:29:00 -0000 [thread overview]
Message-ID: <1180617817.12360.70.camel@sg-ubuntu> (raw)
In-Reply-To: <465EB804.9040200@mail.ru>
Alexey Shusharin wrote:
> Uwe Kindler wrote:
> > Hello Alexey,
> >
> > which serial channel do you use for the serial connection? I also have a
> > LPC-E2294 board (Rev. B) here. Do you use the onboard USB connector or
> > the onboard RS232 D-Sub connector for serial conection?
> >
> > Best regards
> >
> > Uwe
> >
> Hello Uwe,
>
> I use USB connector. Do you test Sergei's port? You can find it on his
> home page (http://sgs.gomel.by/sg/articles/olpce2294/index.html).
>
> However, I clear up some of features.
>
> It's not a problem of /dev/ttydiag. I don't understand why, but then I
> use the serial connection instead of the ethernet my thread doesn't
> start (it doesn't perform other work). cyg_user_start() works properly
> and its output appear on the serial port.
Alexey, as far as I could understand, you try to busy one serial port
(UART0) by a triple work: for the debugging, for the diagnostic and for
the interrupt driven TTY mode, but that isn't possible.
You should use the second port on the board (D-Sub UART1) for TTY mode
(/dev/ser1) and using CYGDAT_LIBC_STDIO_DEFAULT_CONSOLE option to point
what stdio output should appear there, i.e. printf() output (!diag)
shouldn't appear on /dev/ttydiag. By default, stdio output quite flows
via /dev/ttydiag.
-- Sergei
--
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 prev parent reply other threads:[~2007-05-31 13:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 12:01 cetoni GmbH - Uwe Kindler
2007-05-31 12:30 ` Alexey Shusharin
2007-05-31 13:25 ` cetoni GmbH - Uwe Kindler
2007-05-31 14:29 ` Sergei Gavrikov [this message]
2007-06-01 12:27 ` Alexey Shusharin
2007-06-01 13:42 ` Sergei Gavrikov
2007-06-01 16:35 ` Alexey Shusharin
2007-06-01 18:25 ` Sergei Gavrikov
2007-06-04 7:40 ` Alexey Shusharin
2007-06-04 8:35 ` Sergei Gavrikov
2007-06-04 17:44 ` Sergei Gavrikov
2007-06-01 18:31 ` Sergei Gavrikov
2007-06-01 18:48 ` Mike Arthur
2007-06-01 20:15 ` Sergei Gavrikov
2007-06-01 16:00 ` Sergei Gavrikov
2007-06-01 14:04 ` Sergei Gavrikov
2007-06-01 18:47 ` Sergei Gavrikov
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=1180617817.12360.70.camel@sg-ubuntu \
--to=w3sg@softhome.net \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mrfinch@mail.ru \
/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).