public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "Natarajan, Mekala (CTS)" <NMekala@chn.cognizant.com>
Cc: "'ecos-discuss@sources.redhat.com'" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] aeb
Date: Wed, 24 Jan 2001 11:12:00 -0000	[thread overview]
Message-ID: <3A6F2906.9A2D66F1@redhat.com> (raw)
In-Reply-To: <8F1D166D08ACD41196EE00B0D020944B68B5C7@CTSINENTSXUB>

"Natarajan, Mekala (CTS)" wrote:
> 
> Hi,
>         i am using aeb-1 rev-b as my target platform. It has got only one
> serial port.
> i referred the previous mailing list. it says with one serial port it is not
> possible to get a character since the serial port is used by gdb. I have a
> doubt regarding this. If we give printf it is printing the characters in the
> console. Printing is again through serial port i guess. how is this
> happening.

You mean the output is happening through GDB. The point is that this output
is encoded in a GDB packet, received by GDB and displayed by GDB.

> Can someone help on this.
> 
> i am not able to a character from input.
> i tried using getchar(), hal_diag_read_char();it doesn't work..

GDB doesn't support getting characters from the keyboard and sending them
over serial to the target.

If you require serial input, you will have to disconnect from GDB and use
the serial port directly. You will also need to enable the eCos serial
device driver on the AEB.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine

      reply	other threads:[~2001-01-24 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24  8:20 Natarajan, Mekala (CTS)
2001-01-24 11:12 ` Jonathan Larmour [this message]

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=3A6F2906.9A2D66F1@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=NMekala@chn.cognizant.com \
    --cc=ecos-discuss@sources.redhat.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).