From: Andrew Lunn <andrew@lunn.ch>
To: RandyLin@mxic.com.tw
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Unable to run kernel test program on Samsung SNDS!
Date: Mon, 24 Nov 2003 10:52:00 -0000 [thread overview]
Message-ID: <20031124105232.GA13368@lunn.ch> (raw)
In-Reply-To: <OF5F5C9EEF.581DE50A-ON48256DE8.0032A20A-48256DE8.00341C7F@MXIC.COM.TW>
> RedBoot> go 0x50040
> $O504153533A3C42696E6172792053656D6170686F72652030204F4B3E0A#9E
> =========================================
This is an O format text string which gdb will decode and display. For
some reason your application/redboot thinks it is still talking to
gdb and so is mangling the text.
Have you set CYGSEM_HAL_DIAG_MANGLER in either your application or
Redboot?
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-11-24 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 9:30 RandyLin
2003-11-24 10:52 ` Andrew Lunn [this message]
2003-11-25 2:28 RandyLin
2003-11-25 3:47 ` Gary Thomas
2003-11-26 6:51 RandyLin
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=20031124105232.GA13368@lunn.ch \
--to=andrew@lunn.ch \
--cc=RandyLin@mxic.com.tw \
--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).