I had some problems with breakpoints not doing what they should, and code seemingly resetting after breakpoint continuation. I don't know how breakpoints work here, but in ancient times it was by replacing instructions. So I tried to just program the code into the chip to see if this might be the cause. And after programming verify failed. It seems I can erase the chip, but programming will successfully program just a K or two.
I have more than one of my PCBs prepared, and using another works fine (so far).
Is there anything I could have done wrong that makes the possible number of flash cycles really low? I did turn breakpoints on/off and make program changes. But hey, how many can I do in less than a week?
I'm not stuck. But if I'm doing something wrong killing my processors, I would like to change my ways. I'm not a typical killer person.
From .HEX to be programmed:
.. and continuing with lots more hex data..
What it reads back:
.. and then FF from there on.
What I use:
ATXMEGA128A3U-AU. Target voltage 3.35V.
JTAGICE MkII Sn:070000003497. Used for debug & program.
Atmel AVR Studio 5 (Version: 5.0.1038.1038)
Â© 2011 Atmel Corp.
All rights reserved.
OS Version: Microsoft Windows NT 6.1.7600.0
AVR Studio Assembler Language Service (1.0)
AVR Studio Assembler Project (1.0)
AVR Studio Device Service (1.0)
AVR Studio GCC Language Service (1.0)
AVR Studio GCC Project (1.0)
AVR Studio Help About (1.0)
AVR Studio Object File Debug Project (1.0)
AVR Studio Software Framework (1.0)
AVR Studio Target Manager (1.0)
AVR Studio Target View (1.0)
AVR Studio Tool Service (1.0)
Status Service (1.0.0)
Visual Assist X (1.0)