Have I smoked my Uzebox via AVRISP MKII?

Too all,

OK, I’m a noob when it comes to programming chips, but I pride myself on following directions and understanding the tasks at hand prior to any major deployment operation. Well, I thought I had done my due diligence in preparing my Uzebox for its first program flash, but I guess I was wrong. I hope I have not smoked my ATmega644! Any help would be appreciated.

So here is the situation I’m in…

  1. I can no longer get into programming mode with AVR Studio via AVRISP mkII.

  2. My Uzebox no longer lights up when power is applied via USB adaptor.

  3. My AVRISP mkII - both lights are green confirming connections from USB and Target.

Below is my setup prior to flashing.

Device: atmega644 on a Uzebox AVCore Development Module attached to Uzebox GameCard Baseboard. - Fully working prior to flashing.

Programmer:ATMEL AVRISP mkII -

Software: AVR Studio 4.13.528

GUI Version 4, 13, 0, 528

Operating System - Windows XP

Major 5

Minor 1

PlatformID 2

Build 2600 - Service Pack 3

Plugins:

AvrPluginAvrAsmObject 1, 0, 0, 45

AvrPluginavrgccplugin 1, 0, 0, 7

Stk500Dll 1, 0, 1, 0

My config prior to programming:

Program tab:

Device:ATmega644

Programming Mode: ISP mode

Erase Device befor Programming - checked

Verify Device After Programming - checked

Flash: Input HEX File - DonkeyKong.hex

EEPROM: Input HEX File - blank(no entries)

Fuses tab: (selected only)

Brown-out detection disabled;[BODLEVEL=111]

Boot Flash section size=512 words Boot start address=$FE00;[BOOTSZ=11]

Ext. Crystal Osc.;Frequency 3.0-8.0 MHz;Start-up time: 16K CK + 65 ms;[CKSEL=1110 SUT=11]

Auto Verify - checked

Smart Warnings - checked

Output box below for Fuses:

Setting mode and device parameters…OK!

Entering programming mode… FAILED!

Leaving programming mode… OK!

LockBits tab: (selected only)

Mode 1:No memory lock features enabled

Application Protection Mode 1:No lock on SPM and LPM in Application Section

Boot Loader Protection Mode 1:No lock on SPM and LPM in Boot Loader Section

Auto Verify - checked

Smart Warnings - checked

Output box below for LockBIts:

Setting mode and device parameters…OK!

Entering programming mode… FAILED!

Leaving programming mode… OK!

Advanced tab:

Signature Bytes - 0x00 0x00 0x00

"WARNING: Signature does not match selected device!

Calibrate for frequency: 8.0MHz

Value: 0x00

Write Address: blank - Flash clicked

Communication Settings - not used

Output box below for Advanced:

Setting mode and device parameters…OK!

Entering programming mode… FAILED!

Leaving programming mode… OK!

Board tab:

Voltages - VTarget 4.9

Oxcillator and ISP Clock

ISP Freq: 6.48kHz

Revision: Hw:0x01, FW major 0x01, FW minor: 0x06

Output box below for Advanced:

Getting revisions… HW: 0x01, FW Major: 0x01, FW Minor: 0x06 … OK

Getting VTARGET… 5.0V … OK

Setting ISP frequency SD=0x3e… OK

Auto tab: not used

Taken my pain to another forum where I have received a tremendous amount of help in understanding my problem. No doubt that I set my programmer up incorrect which resulted in me being locked out my device. The prescribed action to correct the problem is to perform a High Voltage Serial Programming (HVSP). Unfortunately, my programmer cannot perform this task. I will probably replace the atmega644 instead, and be on my way and be wiser for it.

Mike