From: Gentleman.nbg@gmx.de
To: Gentleman.nbg@gmx.de
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Fwd: Re: [ECOS] Can't read with cyg_io_read()
Date: Thu, 14 Feb 2008 22:31:00 -0000 [thread overview]
Message-ID: <20080214223117.258120@gmx.net> (raw)
In-Reply-To: <20080214142959.285270@gmx.net>
Can someone acknowledge that the driver "/dev/haldiag" ist only intended for output of traces and is not able to read anything?
I am asking because in documentation there is no explanation of the individual drivers.
-------- Original-Nachricht --------
> Datum: Thu, 14 Feb 2008 15:29:59 +0100
> Von: Gentleman.nbg@gmx.de
> An: ecos-discuss@ecos.sourceware.org
> Betreff: [ECOS] Fwd: Re: [ECOS] Can\'t read with cyg_io_read()
> Hi,
>
> in debugging mode I found out, that I could not use neither /dev/tty0 nor
> /dev/serial0 driver as my handle. The only working driver is /dev/haldiag/.
>
> Where can I change the configuration? with ecos configuration tool?
>
> I am asking because, I am building my eCos image with a makefile and gnu
> make.
>
> Do you really think that /dev/haldiag/ is not able to read from serial
> port? It can write, so I think it should be able to read too.
>
> Thank You
>
>
> -------- Original-Nachricht --------
> Datum: Wed, 13 Feb 2008 17:48:06 +0100
> Von: Andrew Lunn <andrew@lunn.ch>
> An: Gentleman.nbg@gmx.de
> CC: ecos-discuss@ecos.sourceware.org
> Betreff: Re: [ECOS] Can\'t read with cyg_io_read()
>
> On Wed, Feb 13, 2008 at 04:07:13PM +0100, Gentleman.nbg@gmx.de wrote:
> > hi eCos fans,
> >
> > I don't know if it is the apropriate way to ask such things, but I
> haven't found a board for ecos-developers, so I'll make it short:
> >
> > I am testing the serial communication via eCos api. Writing is not the
> issue, there is a example, and it works.
> >
> > But I can't read anything from serial device. I connected it to my PC
> where I am tryting to write (with keyboard) some characters via a terminal
> e.g. MS Hyperterminal. I also tried it by sending a "hello" via the Win32
> Serial API. But my controller application waits forever. I am sure that I have
> sent the characters (as I used a serial port scanner).
> >
> > My eCos example code would look like this:
> >
> > static void simple_prog(CYG_ADDRESS data)
> > {
> > cyg_io_handle_t handle;
> > Cyg_ErrNo err;
> >
> > const char send_string[] = "Hallo";
> > cyg_uint32 len = strlen(send_string)+1;
> >
> > char read_string[6];
> > cyg_uint32 len2 = 6;
> >
> >
> > err = cyg_io_lookup( "/dev/haldiag", &handle );
>
> You will find it work better if you use /dev/tty0. You will need to
> change you configuration a little, add the interrupt serial device
> driver and the TTY driver.
>
> Andrew
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
> --
> Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games!
> http://games.entertainment.web.de/de/entertainment/games/free
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
--
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:[~2008-02-14 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 14:30 Gentleman.nbg
2008-02-14 22:31 ` Gentleman.nbg [this message]
2008-02-14 22:41 ` [ECOS] " Grant Edwards
2008-02-14 23:11 ` Gentleman.nbg
2008-02-14 23:16 ` [ECOS] " Grant Edwards
2008-02-15 15:17 ` Grant Edwards
-- strict thread matches above, loose matches on Subject: below --
2008-02-13 17:08 [ECOS] Fwd: Re: [ECOS] " Gentleman.nbg
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=20080214223117.258120@gmx.net \
--to=gentleman.nbg@gmx.de \
--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).