Another Duemilanove with error not sync

Hello guys,

I am new to the forum and newbie with Arduinos, but I have basis for electronics and computing.
I am writing as last wish to save an Arduino Duemilanove (e_roboto.tw) bought in dx.com.
Important to say that I have an Arduino Nano which works perfectly.

After some errors in the installation drivers and a boot, managed to load the example blink on my Duemilanove and since then has never more worked, I explain: In the next day and it wasn't blinking and when trying to load and got the error: avrdude: not in sync : resp = 0x00.
After reading many posts, I tried:

• tested the cable;
• did the loop-back test;
• checked model and port;
• tested on different computers (my Nano works forever at all);
• tried different IDE versions (0022 until 1.0.5);
• tried different versions of FDTI drivers (2.0.0, 24, 28, 30);
• press the reset button before/during/after/in a row/ strongly when uploading;
• put a resistor between pin 5 and Reset to load;
• bought and changed the ATmega328P-PU with bootloader already recorded;
• tried to burn the bootloader using a TinyISP (Atmega new and old);

And I still getting the error message: avrdude: not in sync: resp = 0x00
I'm using Windows 7 32-bit.

Is it time to give up or have something to be done yet?

Thank you

• did the loop-back test;

And?

srmark, have you noticed any complications with the Nano now that, I assume, you have the FTDI driver installed along with the Arduino driver?

Nano also uses FTDI driver. There is no indication of 16U2 type driver being installed.

Thank you guys,

Coding Badly,
loop-test OK

Honduras,
Nano works perfectly, I suppose Nano and Duemilanove use the same FTDI driver, right?

CrossRoads,
Can I assume that there is no driver error?

Additional information:
I tried upload the blink sample using an usbTiny and this is the result:

Programmer Type : USBTINY
Description : USBtiny simple USB programmer

avrdude: Using SCK period of 10 usec
CMD: [ac 53 00 00] [00 00 00 00]
CMD: [ac 53 00 00] [00 00 00 00]
avrdude: initialization failed, rc=-1
avrdude: AVR device initialized and ready to accept instructions

Reading | | 0% 0.00sCMD: [30
00 00 00] [00 00 00 00]
CMD: [30 00 01 00] [00 00 00 00]
Reading | ################# | 33% 0.00sCMD: [30
00 02 00] [00 00 00 00]
Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
avrdude: Expected signature for ATMEGA328P is 1E 95 0F

Sure doesn't look like the chip is talking.

Try the chip detector sketch:

• did the loop-back test;

And? What happened?

Thank you Nick. Very interesting...
Just a doubt: in this case, what the objective: check the fuses or other information that would be used to correct the previous error (upload the blink sample)?

avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.

To find out if the chip is working or not. If the chip responds, then there is some comms issue (eg. wrong baud rate, wrong baud selected, wrong fuses, USB interface not working, no bootloader, etc.).

srmark:

• tried to burn the bootloader using a TinyISP (Atmega new and old);

Oh?

srmark:
avrdude: Expected signature for ATMEGA328P is 1E 95 0F

Well, that's what would bounce back if you were trying to bootload with your "Tiny ISP" and there was a "plain" 328 in place. Many Arduino clones use the ATmega328 instead of the 328P to save a few cents. Anyway, it probably shipped without a bootloader on it (read of that a few times in "comments" there at dx.com - caveat emptor.)
The signature for the 328P is 0x1e 0x95 0x0f
The signature for the 328 (no "P" suffix) is signature = 0x1e 0x95 0x14

"Non-P" devices can be programmed by modifying the avrdude.conf file.
In the ATmega328 section, find and change signature = 0x1e 0x95 0x0f (the P signature) to signature = 0x1e 0x95 0x14 (non-P)

avrdude: Device signature = 0x000000

However that is not a valid signature.

Yes, a lot of thrashing about preceded the "last wish" effort here.

Hi guys,

I found a cold solder (or maybe cold weld? ) in the second capacitor, see the image:

Could be this issue the reason of the sync error?

I'm not sure I can fix it... it's seeming damaged

Thank you

No, that will not keep the 328 from responding, unless it drags down the 5v line.
Do you measure 5V at the power header?

Hi Nick,

Sorry, but I got some errors on compilation (Did I something wrong?)

Atmega_Board_Detector\md5.c.o: In function md5_starts': C:\Arduino\libraries\Atmega_Board_Detector/md5.c:40: multiple definition of md5_starts'
md5.c.o:C:\Temp\build8542142942334762976.tmp/md5.c:40: first defined here
Atmega_Board_Detector\md5.c.o: In function md5_process': C:\Arduino\libraries\Atmega_Board_Detector/md5.c:51: multiple definition of md5_process'
md5.c.o:C:\Temp\build8542142942334762976.tmp/md5.c:51: first defined here
Atmega_Board_Detector\md5.c.o: In function md5_update': C:\Arduino\libraries\Atmega_Board_Detector/md5.c:174: multiple definition of md5_update'
md5.c.o:C:\Temp\build8542142942334762976.tmp/md5.c:174: first defined here
Atmega_Board_Detector\md5.c.o: In function md5_finish': C:\Arduino\libraries\Atmega_Board_Detector/md5.c:221: multiple definition of md5_finish'
md5.c.o:C:\Temp\build8542142942334762976.tmp/md5.c:221: first defined here

Thank you

CrossRoads:
No, that will not keep the 328 from responding, unless it drags down the 5v line.
Do you measure 5V at the power header?

I have 5.06V between pin 7 and 8 of the AtMega.

C:\Arduino\libraries\Atmega_Board_Detector/md5.c

What is the sketch doing there in the libraries folder?

It should be in your sketches folder, and not inside the C:\Arduino download folder at all.

I don't know... I used the menu (1.0.5) and after your post I copied manually and it ran.
I'll connect the boards and post the result soon.

Hello Nick,

I performed the sketch and just received that:

¿ï?ܽ¿!.Ì (57,600 baud)

Atmega chip detector. (115,200 baud)

BTW: Led 13 is blinking very very fast

Atmega chip detector.

That means it has not gone into programming mode. (115200 is the right baud rate).

Please post a photo of how you have it wired up.