Ok, things are becoming more interesting. Below is my update to avr@atmel.com, on my debugwire frustrations: Additional info. In the pic that I sent, you can see that the system failed to clear ZH, even though it was straightline code, "clr ZH" This has been absolutely consistent since it started happening, through reboots, powerdown of target and debugger, etc. I also noticed that the debugger was failing to properly load up the stack pointer, which is simply ldi TEMP,low(RAMEND) ; $04FF out SPL,TEMP ;Init stackpointer ldi TEMP,high(RAMEND); out SPH,TEMP ; At the end of this, SP was $04XX where XX was whatever happened to be in ZL when we came in. Today I noticed the common thread. BOTH of these points had breakpoints set. Even though I wasn't USING the breakpoints, (I was single-stepping), that was causing the problem. I may not have read ALL the documentation, but as far as I'm aware, setting a breakpoint is not supposed to also cause the debugger to ignore the instruction at the breakpoint. Please advise.
Message
Re: [AVR-Chat] Re: Debugwire, stk-500 and M168
2008-01-24 by David VanHorn
Attachments
- No local attachments were found for this message.