public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: T Satish Kumar <satish@td.idc.lsi.sanyo.co.jp>
Cc: sid@sources.redhat.com, ecos-discuss@sources.redhat.com
Subject: Re: sid uart1 displays hex output
Date: Tue, 24 Sep 2002 05:50:00 -0000	[thread overview]
Message-ID: <20020924085036.A11578@redhat.com> (raw)
In-Reply-To: <001501c26432$e1639f20$19b6b486@sltisatish>; from satish@td.idc.lsi.sanyo.co.jp on Tue, Sep 24, 2002 at 06:28:40PM -0700

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

Hi -

On Tue, Sep 24, 2002 at 06:28:40PM -0700, T Satish Kumar wrote:
> Hi,
> When i run the program using the sid. i get the output in the form of
> hex code on the System monitor's uart1 output window pane !
>    How can i get to see the output in its original format i.e for eg: 
> if the output to be displayed is "Hello" in the printf() function..
> the uart1 window pane displays 48656C6C6F
> [...]

It turns out that this question rightfully belongs to eCos, not to SID.
The eCos libraries sometimes believe that they have a console connection
to GDB instead of a raw tty, and therefore encode output in gdb's remote
protocol $O packets.  You need to tell eCos not to do this encoding for
console output.  I don't recall how to do this - it may be an ecosconfig
option.

- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-09-24 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24  2:28 T Satish Kumar
2002-09-24  5:50 ` Frank Ch. Eigler [this message]
2002-09-24  5:53   ` [ECOS] " Andrew Lunn
2002-09-24  5:56   ` Gary Thomas
2002-09-24 22:34     ` T Satish Kumar

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=20020924085036.A11578@redhat.com \
    --to=fche@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=satish@td.idc.lsi.sanyo.co.jp \
    --cc=sid@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).