Home › Evil Mad Scientist Forums › Microcontrollers › avrdude problem with MEGA2560 › Re: avrdude problem with MEGA2560
It is not clear to me exactly what you are trying to do, nor exactly what the problem is.
You have said that you are trying to get a Peggy board working, but that you’re using an Arduino Mega2560 on it. The Peggy boards do not come with an Arduino Mega2560, nor a socket for one, nor any other obvious way to attach one to it. So, it is not whatsoever clear what your actual hardware setup is.
You are having a problem with uploading code to the ‘2560 board. However, you have not said how you are trying to upload the code. The fact that you are mentioning the AVR ISP and AVRISP MKII leads me to guess that you are using an external programmer (perhaps an AVR ISP programmer of some sort?), rather than direct uploads via the more standard USB/bootloader interface, but you have not said. It is not clear what hardware you are using to connect the Mega2560 to your computer.
The fact that you mention “boards.txt” suggests that you are trying to upload from within Arduino, rather than directly from the command line… but you have not said so directly. Assuming that you are trying to upload from within Arduino, then please follow the steps of the Arduino troubleshooting guide. I would also suggest starting over with a fresh copy of the Arduino IDE, one where you have _not_ edited the boards.txt file. If you are not using Arduino (and you are programming from the command line or another program), then you should ignore the boards.txt file.
The fact that you can upload to both an Arduino Nano and Uno suggests that your computer and basic programming methods are sound. If you are using the USB interface to program these from within Arduino (guessing here– again, you haven’t really indicated what your hardware, programming, or software setups are!) then that does suggest that your USB drivers are working properly.
If you find the same sort of behavior (these two boards always work, these two boards never work, etc) across multiple computers, that may indicate that the boards that the boards (or at least, the part of the hardware that allows them to be programmed) may be damaged.