public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "T Satish Kumar" <satish@td.idc.lsi.sanyo.co.jp>
To: "Gary Thomas" <gthomas@ecoscentric.com>,
	"Frank Ch. Eigler" <fche@redhat.com>
Cc: <sid@sources.redhat.com>,
	"eCos Discussion" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Re: sid uart1 displays hex output
Date: Tue, 24 Sep 2002 22:34:00 -0000	[thread overview]
Message-ID: <006e01c264db$6b3f2130$19b6b486@sltisatish> (raw)
In-Reply-To: <1032872210.14065.180.camel@hermes.chez-thomas.org>

well, previously i was using ecos 1.3.1..but later when i tried the same
using ecos 2.0..
this time..i m not able to see even the Hex equivalent of the original
string format ..
i disabled both the options and built the ecos library:
eCos HAL->ROM Monitor support->Work with a ROM Monitor to Disabled
(unchecked)

eCos HAL->Platform-independent HAL options->Route diagnostic output to debug
channel to Disabled (unchecked)

but still therez no output string seen in the uart1 of the system monitor
window.

what could be the problem...?

satish



----- Original Message -----
From: "Gary Thomas" <gthomas@ecoscentric.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: "T Satish Kumar" <satish@td.idc.lsi.sanyo.co.jp>;
<sid@sources.redhat.com>; "eCos Discussion"
<ecos-discuss@sources.redhat.com>
Sent: Tuesday, September 24, 2002 5:56 AM
Subject: Re: [ECOS] Re: sid uart1 displays hex output


> On Tue, 2002-09-24 at 06:50, Frank Ch. Eigler wrote:
> > 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.
>
> This program (eCos application?) thinks that this output is being handled
> by GDB.  Turn it off by disabling CYGSEM_HAL_USE_ROM_MONITOR and
rebuilding
> the application.
>
> --
> ------------------------------------------------------------
> Gary Thomas                  |
> eCosCentric, Ltd.            |
> +1 (970) 229-1963            |  eCos & RedBoot experts
> gthomas@ecoscentric.com      |
> http://www.ecoscentric.com/  |
> ------------------------------------------------------------
>
>

      reply	other threads:[~2002-09-25  5:34 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
2002-09-24  5:53   ` [ECOS] " Andrew Lunn
2002-09-24  5:56   ` Gary Thomas
2002-09-24 22:34     ` T Satish Kumar [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='006e01c264db$6b3f2130$19b6b486@sltisatish' \
    --to=satish@td.idc.lsi.sanyo.co.jp \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=fche@redhat.com \
    --cc=gthomas@ecoscentric.com \
    --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).