This seems a nice idea! Are you associating the breakpoint directly with the interrupt handler? In such way we could write a dummy simple button event handler just to make same space for the breakpoint. So stepping a little after the Breakpoint code would go back to the previous function. Is that a bad idea? I'm not behind the telos and i can't try rigth now.
- Max 2006/5/9, Matt Thompson <[EMAIL PROTECTED]>:
I have the same problem under Linux, but unfortunately I have not found a workaround. I have added a breakpoint to a User Button event, allowing me to enter the debugger with the button, but that doesn't really help, other than to view memory. Cheers, Matt Thompson andrea labo wrote: > Hi all. > > I'd like to solve a problem I have while debugging a TelosB Board. > The mote is connected to PC trough the parallel JTAG interface. On the > host (Windows XP and Cygwin) msp430-gdbproxy is running. > msp430-gdbproxy recognizes the micro (msp430...) so the communication > with TelosB is fully functional. > When i connect gdb to gdbproxy, everything seems to be fine. I could > use all the monitor instances, step instructions, watch memory and > starting program execution (command c). > I need to halt the processor to analyze which instruction is currently > executed. > When i press the CTRL+C keys, and i suppose to halt the micro, all i > get is the following: > > Program received signal SIGINT, interrupt. > 0x00004000 in _reset__vector__ ( ) . > > What should i do? >> From Texas JTAG specifications i read that is possible to halt the > micro, but seems it doesn't work. > > Thanks for the support. > > - Max > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
