public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: "Ecos-List (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] PC Serial driver
Date: Wed, 13 Sep 2000 18:26:00 -0000	[thread overview]
Message-ID: <8AE4B526B977D411841F00A0CC334020052C53@cuz-exchange.sdesigns.net> (raw)

Hi,

I've ecos running on a PC, debugging with gdb through com1 and I would like
to read some data sent on com2. 

So first I configured eCos to enable the hardware serial driver fort port 1
(ie com2)
I am surprised that in this configuration I had to precise the baudrate, but
not for example stop bits or parity. It seems that I had to configure those
at runtime, but I also have to configure the baud rate so I don't understand
very well what I'm reaaly doing.

Anyway, the serial port seems initialized, as I get the following ouput:
Init device '/dev/ser1'
I386_PC SERIAL init - dev: 2F8.35
Set output buffer - buf: 1B4B60 len: 128
Set input buffer - buf: 1B4BE0 len: 128

Then a cyg_io_lookup seems to return a correct handle.
But then a cyg_io_read block (I'm just reading one char)

It seems I didn't get any interrupts neither. (I put a breakpoint in the
serial DSR)

My serial device works well (I have tested it using my PC as a terminal and
get plenty of input)

Is the Serial Driverfor PC in good shape? Does anyone succedded in reading
something from a serial port? Do I use the good driver?

Thanks

-- 
Fabrice Gautier
fabrice_gautier@sdesigns.com 



                 reply	other threads:[~2000-09-13 18:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8AE4B526B977D411841F00A0CC334020052C53@cuz-exchange.sdesigns.net \
    --to=fabrice_gautier@sdesigns.com \
    --cc=ecos-discuss@sourceware.cygnus.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).