Can't upload to mega 2560 after tinkering.

The mega was working just fine until I started using a chip detector sketch. I'm pretty sure it was either my bad connections and or handling the unit that did it. The problem is I can't upload to it. When I try to upload, the link LED flashes very briefly/dimly followed by an RX LED flash, and then nothing. After awhile, it times out. I wish I had a better explanation of what happened but I was so focused on trying to solve another issue that I created this one. It does pass the loop back test, and I am also able to successfully query its signature with a chip detector sketch loaded on an Uno. The reset button doesn't appear to have any affect; the 'on' LED used to flash after a reset and now it doesn't. Can I use ICSP to reprogram it with my UNO?

Ouch. By the "ON LED", you mean pin 13 not the main power LED?

Anyhow, you should be able if something else did not cook super well done. Try Nick's Atmega Board Programmer sketch on the UNO and hook it up Mega Style:

Mega Uno Funct
Pin Reset Pin 10 SS or Reset Signal
Pin 51 Pin 11 MOSI
Pin 50 Pin 12 MISO
Pin 52 Pin 13 SCK

Vcc 5v Power
Gnd Gnd Ground

Open the serial monitor and see what can be seen.

No I wasn't able to use Nick Gammon's Board programmer, or at least the sketch didn't give me the option to burn the bootloader.
Here is the output from the programmer sketch:

Atmega chip detector.
Entered programming mode OK.
Signature = 1E 98 01
Processor = ATmega2560
Flash memory size = 262144
LFuse = FF
HFuse = D8
EFuse = FD
Lock byte = FF
Clock calibration = 90
Bootloader in use: Yes
EEPROM preserved through erase: No
Watchdog timer always on: No
Bootloader is 8192 bytes starting at 3E000

Bootloader:

3E000: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3E010: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
...
...
3F680: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F690: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F6A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F6B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F6C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F6D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F6E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F6F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F700: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F710: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F720: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F730: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F740: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F750: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F760: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F770: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F780: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3F790: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
3FFF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

MD5 sum of bootloader = 84 D0 4C 9D 6C C8 EF 35 BF 82 5D 51 A5 27 76 99

First 256 bytes of program memory:

0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
10: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

any other suggestions?

Sorry, I was just interested in exactly what you got (chip id etc.). Now, if you switch sketches (keep the same setup as Nick's ABP) on the Uno to "Arduino as ISP" in the Arduino IDE, select the Arduino as ISP as the Programmer. Switch the Board to the Mega 2560 and then "Burn Bootloader". This will take a little bit of time.

When finished, it will more than likely give you a verification error, just ignore it. I have burned the exact same bootloader hex with AVRDUDE manually and the error is only in the Arduino IDE. Should be ready for uploading.

I just tried it again using Nick's sketch, and it worked! weird...

Cool. You saved me a setup on confirming if the 2560 hex was in Nick's ABP. What I like about the ABP is that chip ID that tells me that I am really connected SPI. There is also a 8MHz signal on D9 for virgin AVRs and finally it is FAST. Takes 1 second for ABP while the Arduino as ISP takes 1.5-2 minutes to burn. My to do list has putting the 8u2/16u2 firmware into the sketch.

Enjoy.

I have tried the setup and it will work fine with a another UNO but there is no response when trying it with an original Mega2560 (in fact two boards do exactly the same). It just says:

Atmega chip programmer.
Written by Nick Gammon.

Any suggestions on how to see if the two Megas are trash or not? One is brand new and it has not accepted programming in 3 different computers even though the com port shows up in the Arduino IDE and in the Windows device manager as working properly.

It just says...

is usually an indication that the SPI connections are wrong or incomplete. double-check. then triple-check. Is there any indication that there is a sketch still running on the uc?

I am using the direct connection as described here:

Arduino Uno      Target Mega2560

D10 (SS)            Reset
D11 (MOSI)          D51
D12 (MISO)          D50
D13 (SCK)           D52

Gnd                 Gnd
+5V                 +5V

And though the numbers on the even side are printed somewhat off the proper spots, 11 from the UNO is connected to 51 on the Mega (second from the bottom on the odd numbered side) and so on as here: Connections | UNO to program bootloader on to MEGA 2560 | Blue_Metal | Flickr .

The sketch is running on the Uno as every time you reset you get another two line message as above.

The sketch...

I was wondering about the mega, any signs of life? is the bootloader working when you power cycle (reset to ground)? If you are sure of your connections, then I don't think it is looking good for the mega(s?). Was there an incident that started this? which IDE have you tried?

On the R3 Mega I can program sketches in one computer (running XP) and they work, yet it does not show up in the programmers window and will not accept sketches on a Windows 7 PC. The R2 Mega is non responsive in every machine though it shows up as a COM port in the Arduino IDE on both machines.

The R3 came out of the original box for these tests and the R2 was working in a 3D printer before it went silent. The steppers in the printer were were being tested at the time the processor stopped.

I have tried with both Arduino 1.0 and the latest 1.03.