It's been a while since I've done some projects with an AVR, but now I've started one again.
I'm building a 6-channel voltage logger, currently with an ATMEGA168. All works well, but I would need some more codespace to implement SD/MMC support.
I've swapped the AVR with a brand new M328, but my programmer refuses to write the .hex file correctly.
I'm using a MySmartUSB MKII programmer with the latest MyAVR ProgTool (v1.39).
The programmer will find the chip, but when I try to burn the .hex-file, it keeps returning a checksum verification error after programming.
When I read back the code from the chip, I find that some code is written, mostly in the very last part of the memory.
MyAVR.com support replied to my question that my setup should support the M328, "since it is only a memory upgrade compared to the M168".
The M168 still works flawlessly with the MySmartUSB, and an M88 also works in my target board.
In all three cases, power supply is rock solid 5V, checked with my oscilloscope during programming as well.
I've also got the MyMultiProg add-on board, which allows me to program the chips without the need of a target circuit:
But no difference. M88, M168 work flawlessly but M328 fails during verification.
I've borrowed a genuine Atmel AVRISP MKII, which connects to the M168 and M88 without any troubles, but refuses communication with the M328:
Unable to enter programming mode. Please verify device selection, interface settings, target power and connections to the target device.
I am using AVR Studio 6.0 and the AVRISP firmware is 1.11.
I've tried 4 different M328's, all brand new and purchased through Mouser.com (so I assume they're genuine).
Am I overlooking something here?