Re: bdi2000 and gdb (newbie question)

[Fabian Cenedese <Cenedese@indel.ch>]

>I've got a bdi2000 and Cogent csb337 running the micromonitor boot loader.
>I've been able to compile and download the umon to the csb337 successfully
>using the bdi2000 and jtag interface.  
>
>prompt> gdb CSB337_tst.elf 
>
>(gdb) target remote 192.168.100.44:2001
>Remote debugging using 192.168.100.44:2001
>0x00000000 in ?? ()

snip

>Program received signal SIGTRAP, Trace/breakpoint trap.
>0x63655220 in ?? ()
>(gdb) step
>Cannot find bounds of current function

I don't know this target. But you should look at what data gets returned
over the remote interface (was that "set debug remote 1"?). I also had
similar effects when I returned wrong data for the registers in my self
written stub. Another thing to look at is the endianess. I work with PPC
which can be both little and big endian. Maybe you need to set it
("set endian big/lttle/auto").

BTW, 0x63655220 is "ceR " in ASCII or " Rec" if you change order.
Maybe this looks familiar? I think some string is interpreted as value
for the register (Ok, I know that the remote protocol is MADE of
strings :).

bye  Fabi