> I have been using DW with the Dragon for about 18 months now, > it has been working very well. I have only worked with 5V supplies > though and ALWAYS a 4K7 pull up resistor in the reset line, with > clock ranging from internal 1MHz to crystal 14MHz. In my case, I'm talking to an STK-500 board, with no other "stuff" on the chip, just the bare minimum. Chip is running on internal RC clock. > I must admit that it is not the most solid of debugging environments > but it does work. At times I need to unplug the Dragon and restart > Studio but rarely. Hmm.. > > As far as the wrong values in the registers, is the list file correct > or is something happening at assembly time? No, the lst is right, it's just NOPing some instructions. I've not yet caught it loading anything other than what I said, or doing the wrong instruction, it just looks like the instruction was a nop instead of what I asked for. > With the breakpoint issue, I always do a "build and run" every time I > make the smallest chance. New code gets uploaded to the chip and any > old set breakpoints get cleared, at times some cannot be set in the > original location but they get highlighted and you get asked to remove > them which I do. Remember that breakpoints do in fact change memory > locations, (they are placed in memory with DW not hardware like JTAG) > so it is useful to reload the code and overwrite them. Right, same here. I've had long standing issues in all the debug platforms with what I originally called "ghostpoints". Lotsa debugging happens, many breakpoints get set/cleared etc. Clear all breakpoints, uninstall studio, use a different chip, reinstall studio, start debugging again, and suddenly when you should have been running right through, you're sitting breakpointed at a location where there's no breakpoint, but it IS one that you'd used before. > Hang in there, I have done about a dozen or more project with DW > and I love it. I would prefer if all chips had DW instead of JTAG > as one does not waste any pins. It WILL get better :-) That's just about the only direction it CAN go in from my experience.
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.