Hello,
I had been playing with my programmer (pololu.com/catalog/product/1300) for a few hours with my hardware, the ATmega 1248, and it worked flawlessly out of the box, for multiple flash write cycles. Specifically, I’m using avrdude; my command line options are usually something to the effect of:
avrdude -p m1284p -P /dev/ttyACM0 -c avrispv2 -F -e -U flash:w:foo.hex
And after enjoying myself for a few days playing with my hardware the programmer suddenly seems to have become unreliable with both of the uC’s I have on my PCB.
paste.pocoo.org/show/475134/
paste.pocoo.org/show/475117/
Sometimes the write “works” (the program runs as intended), sometimes not. Sometimes, I even get:
The target is powered by a power supply, not batteries.
I’m not sure what exactly cause this, like I said when I first started playing, it had worked a majority of the time, and it was only suddenly that this issue happened.
My thoughts are that either the programmer has catastrophically failed, or that the 6-pin ISP cable is too long and/or bad (or that avrdude is a self-modifying binary and through some sort of sorcery modified itself to suddenly exhibit that behavior whilst at the same time rooting my machine in order to gain write permission to itself; equally likely ;P). Because the input voltage to my circuitry has been constant the entire time, and I’ve tested two different cpus on two different isp circuits (which are both PCB’s, and not something I hacked together on a breadboard), I would like to also suggest to eliminate those as a possibility as well.
Thank you,
Zack Buhman