Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Message

Re: [AVR-Chat] Re: Debugwire, stk-500 and M168

2008-01-21 by David VanHorn

On Jan 21, 2008 4:43 PM, John Samperi <samperi@ampertronics.com.au> wrote:
> At 08:16 AM 22/01/2008, you wrote:
> >  After that, the part is inaccessible either way.
>
> Once in DW mode the only thing that will revert the chip to
> normal mode is either exiting DW from within a debug session
> or resetting the fuse via HVPP.

Well, I'm not sure WHAT mode the chip is in now.
I can't talk to it with ISP, or Debugwire.
It was in ISP mode, and I exited the programmer, and started debugging.
At that point, it told me that the debugwire wasn't enabled (correct)
and I told it to use ISP mode to enable debug wire.
That was the last I was able to talk to the chip.

> Are you using the Dragon or JTAG Mk2 for debugging?

MkII

> Just to refresh my memory, do you have a 4K7 or 10K pullup
> on the reset pin? ("THEY" say it is not necessary) and of
> course no cap.

STK-500 with reset jumper removed.

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.