[ECOS] Re: LOAD problem or not?

[ECOS] Re: LOAD problem or not?

[Jonathan Larmour]

Please remember to send to the ecos-discuss list, not ecos-discuss-owner.

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:5cb
> 9028c;0f:20ea028c;  <<what is this??
> ========

It's GDB packets. Your target has probably crashed, at address 0x8c02b95c 
(it's there in little endian as the first register entry in that $T packet).

You can either disassemble your executable to work out where that is in 
your program sources, or you can disconnect your serial terminal, connect 
via GDB, do "target remote /dev/ttyS0" (or whatever) and see where it is then.

Note that it's probably easier just to use GDB to load your executable in 
the first place, rather than using the RedBoot CLI. This is all covered in 
the eCos user manual.

Jifl

> gcc>
> sh-elf-gcc (GCC) 3.3-gnuwing-20030801
> Copyright (C) 2003 Free Software Foundation, Inc.
> 
> Redboot>
> RedBoot(tm) bootstrap and debug environment [ROM]
> Non-certified release, version v2_0 - built 10:50:07, Jun 17 2005
> 
> Platform: InterDAQ plus (SH 7751)
> --
> Yukihisa Hara(hara@kgc.co.jp
> 
> 
> 


-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] LOAD problem or not?

[Andrew Lunn]

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:5cb
> 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

[ECOS] RE:LOAD problem or not?

[HARA@KGC]

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