At Wed, 7 Mar 2012 15:15:30 -0800, wayne roberts wrote:
> I have set a breakpoint at main(), and confirmed the msp430 is running from
> reset vector after "monitor reset" then "continue". (it halts at main again)
>
> Yet, I am also using gdb on another platform, where i can single step after
>
At Wed, 07 Mar 2012 22:04:50 +0100, Chris Liechti wrote:
> i was just thinking about that. maybe the server could send a packet
> with register update on "monitor reset".
>
> unfortunately, it looks like "Stop Reply Packets" ("T") are not expected
> when monitor commands are issued, at least there
At Tue, 6 Mar 2012 18:51:26 -0800, wayne roberts wrote:
> (gdb) bt
> #0 0x in ?? ()
> #1 0xc0c0 in blah,blah..etc..
> (gdb) monitor reset
> (gdb) n
> Cannot find bounds of current function
> (gdb)
>
> So, when i issue monitor reset, should the program counter and stack
> pointer be r
First off, when running msp430-gdb:
(gdb) target remote :2000
Remote debugging using :2000
_reset_vector__ () at ../../../gcc-4.6.1/gcc/config/
msp430/crt0.S:105
105 ../../../gcc-4.6.1/gcc/config/msp430/crt0.S: No such file or
directory.
in ../../../gcc-4.6.1/gcc/config/msp430/crt0.S
E