On Tue, Jun 22, 2004 at 07:41:38PM +0200, Chris Liechti wrote: > > > > Is there a way to stop interrupts at all during stepping? Currently I > > always > > yes, newer derivates with EEM can switch off peripheral clocks on > breakpoints, that way, no timer, serial or WDT interrupts occour > however as Steve said, gdbproxy does not support that yet.
"newer derivates with EEM" ?? What is EEM? > > go through my timer interrupt routine after each step - and I have to > > disable > > the timer (or interrupts) before by hand - but then my firmware does not > > longer work as expected. In short - a complete stop of the whole CPU > > and peripherals during debugging and single stepping would be useful (if > > possible, at least a dint). > > debugging real time systems isn't easy and switching off interrupts > doesnt help if you have external events (switches, other signals on the > ports/ADC), the event will ocour anyway and teh CPU will just miss it. > after all you can put a breakpoint on the world ;-) This is true, however debugging is often working like this: setting a breakpoint at the beginning of your code you want to debug. Every thing is working normal until the breakpoint. Once the breakpoint is hit - CPU and all peripherals are stopped - now I do single steeping through the code - CPU and peripherals are enabled for only one cycle (or a number of cycles). Currently the peripherals are not stopped and generate a interrupt after every single step - I understand that this is not implemented. Would be fine if ... sometimes in the futture ... :-) M.
