AVR-Chat

Hi Dave,
              I have had some problems with debugwire going wrong when using
an earlier version of studio (caused by "myself not familiar with using
debugwire" not entering and exiting debugwire properly) the only solution
that I found was to completely uninstall studio, reboot and reinstall studio
(something to do with studio's use of the registry I think).
Might be worth a try.

Owen.

________________________________________
From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf
Of Dave VanHorn
Sent: Saturday, January 19, 2008 3:53 AM
To: AVR-Chat@yahoogroups.com
Subject: [AVR-Chat] Debugwire, stk-500 and M168


Having some startup issues here with the M168 and new JtagiceMkII on 
an STK-500.

I'm porting my bootloader from M128 to the 168, and I thought I'd 
take the easy way, and use a DIP 168 on the STK500. 

So after a lot of searching again, I finally found a ref to 
installing the 168 in the SCKT3200A2 socket, using the green SPROG2, 
removing the RESET jumper to allow debugwire, and was able to load 
the app.

Unfortunately, the fuses weren't set up right, so I had to get out of 
debugwire and use ISP mode to set the fuses.. Ok that looks good, but 
now the part seems to be "stuck" somewhere, I can't talk to it in 
debugwire, or in ISP mode.

Any pointers? 

There's nothing connected to the port pins, for the moment it's just 
power and reset. I have the device set to internal 8 mhz RC clock.