Michael Schippling a écrit : > Just a wild guess, but I'd put a bit of money on the idea that > interrupts need to be enabled for the debugger to work, and > "atomic" disables ints. > MS > Well, I never really noticed problems with interrupts enabled/disabled, it's a jtag (i.e. HW supported) debugger after all, it should not be impacted by interrupts. On the other hand, what happens quite often is that the program continues without reaching any breakpoint or something similar ... You can try to use the command "disassemble" to see assembly and "stepi" to step instruction by instruction. Notice the "i" stepi has a different behavior than "step". Using "display /i $pc" will display the next instruction at each step making it possible to keep track of what's happening (including jumps to interrupts handlers) ...
hope this helps Aurélien _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
