Re: [ECOS] GDB Initialisation problem

[Laurent GONZALEZ <laurent.gonzalez@silicomp.fr>]

On Tue, 1 Jun 2004 14:34:58 +0200
e.coullien@faiveley.com wrote:

> 
> 
> Hi,
> 
> We build a card which looks like the Rattler card with a PPC8270.
> But when we used GDB, we have to launch a NEXTI and a JUMP *0x60000
> command to begin debug with GDB at our start adress 0x60000.
> If we do directly the CONTINUE command, it began at 0x15de4 instead of
> 0x60000. Why GDB doesn't go automaticaly to this adress ?
> Is there a file in eCos to change for this?
> 
> 
> (gdb) target remote 192.168.1.3:9000
> Remote debugging using 192.168.1.3:9000
> 0x0000e8b4 in ?? ()
> (gdb) load hello.elf
> Loading section .text, size 0x8de4 lma 0x60000
> Loading section .rodata, size 0x948 lma 0x68de8
> Loading section .data, size 0x574 lma 0x69730
> Start address 0x60000, load size 40096                       (Here it
> knows that
>  the program begins at 0x60000 !!!)
> Transfer rate: 320768 bits in <1 sec, 507 bytes/write.
> (gdb) nexti
> [New Thread 1]
> 0x00015de4 in ?? ()      (Why is it at this adress ?)
> (gdb) jump *0x60000
> 
> Thanks,
> 

Hello,

try a simple "continue" instead of "nexti" or whatever.

regards,

-- 
GONZALEZ Laurent
Silicomp Ingénierie
Tel: 33 476 41 66 98

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