From: "HARA@KGC" <hara@kgc.co.jp>
To: <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] RE:LOAD problem or not?
Date: Tue, 21 Jun 2005 01:15:00 -0000 [thread overview]
Message-ID: <000001c575fe$9e28bca0$0af41eac@HARA> (raw)
In-Reply-To: <20050620170716.GD17597@lunn.ch>
Thanks Andrew!
The routine is reviewed again.
--
Yukihisa Hara(hara@kgc.co.jp
-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: Tuesday, June 21, 2005 2:07 AM
To: HARA@KGC
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] LOAD problem or not?
On Mon, Jun 20, 2005 at 12:02:29PM +0900, HARA@KGC wrote:
> Hi.
> It embarrasses it because of an unknown output. When the file was
> transmitted by the LOAD command, the following outputs go out and it
> is not possible to debug it. Could you teach only what even has
> occurred? The environment is as follows.
> My best regards.
>
> ========
> RedBoot> load -v -m xMODEM
> Entry point: 0x8c020000, address range: 0x8c020000-0x8c02d688 xyzModem
> - CRC mode, 1289(SOH)/0(STX)/0(CAN) packets, 2 retries
> RedBoot> go 0x8c020000
> $T0a10:5cb9028c;0f:20ea028c;#1b$T0a10:5cb9028c;0f:20ea028c;#1b$T0a10:5
> cb
> 9028c;0f:20ea028c; <<what is this?? ========
This is your application crashing and throwing an exception. The gdb
stub has taken over allowing you to debug your application. gdb should
understand the $T command and give you an idea where your program has
crashed.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-06-21 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 3:02 [ECOS] LOAD " HARA@KGC
2005-06-20 17:08 ` Andrew Lunn
2005-06-21 1:15 ` HARA@KGC [this message]
[not found] <000b01c573d6$1365a030$05000100@HARA>
2005-06-18 14:15 ` [ECOS] " Jonathan Larmour
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='000001c575fe$9e28bca0$0af41eac@HARA' \
--to=hara@kgc.co.jp \
--cc=ecos-discuss@ecos.sourceware.org \
/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).