Unable to push code to Uno R3 using USBasp

[Flameblazer]

Hi, I'm trying to upload a modified "Blink" example to my Uno using USBasp and ICSP ports.

Code:

void setup() {
  pinMode(13, OUTPUT);
}

void loop() {
  digitalWrite(13, HIGH);
  delay(3000);              
  digitalWrite(13, LOW);    
  delay(1000);              
  digitalWrite(13, HIGH);
  delay(500);
  digitalWrite(13, LOW);   
  delay(500); 
}

Error:

Sketch uses 1,066 bytes (3%) of program storage space. Maximum is 32,256 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 2,039 bytes for local variables. Maximum is 2,048 bytes.
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: error: programm enable: target doesn't answer. 1 
avrdude: initialization failed, rc=-1
         Double check connections and try again, or use -F to override
         this check.

The LEDs on the Uno are very dim or don't glow at all when connected to the programmer.

Additional info on my arduino:
I'm trying to use ICSP to program my Uno because I had mistakenly shorted the voltage regulator pins while testing it using a voltmeter and there was smoking coming out of the FTDI chip. Since then, the Uno board is not being recognized by my laptop. But the Uno still powers up and the standard Blink example which I had uploaded on it before still works.

Also, do I have to power the Uno using USB or an AC adapter while uploading using the USBasp?

[mrburnette]

Flameblazer:
<...>
I'm trying to use ICSP to program my Uno because I had mistakenly shorted the voltage regulator pins while testing it using a voltmeter and there was smoking coming out of the FTDI chip. Since then, the Uno board is not being recognized by my laptop. But the Uno still powers up and the standard Blink example which I had uploaded on it before still works.
<...>

Ouch!
There is a chance that the Atmega328P chip is defective - just a few pins; that is, when the FTDI chip went to chip heaven, the current surge could have damaged the uC; one can easily take out the uC nearly on an I/O pin by I/O pin basis due to the way the chip CMOS circuitry is manufactured.
Point is, the chip could be bad even if it is blinking the last sketch loaded.

That being said, trying to diagnose the specific issue in the forum is futile... all anyone can do is just guess. You have two options depending on how you feel:

• buy a new board
• put in a known-good uC replacing the 328 assuming it is a -PU (dual-inline) chip. Before doing this, you should remove the existing 328P-PU and use a VOM/DVM to analyze the voltage on the pins of the uC. As you already know the FTDI is bad, you may as well "cut" the traces from that chip to the uC carefully with an Xacto knife.

Good luck and welcome to the elite "smokin'" club... it happens to us all.

Ray

[DrAzzy]

One of the components that got fried when you did that failed shorted. This damaged part is dragging down the supply rail, and keeping the chip from working (because the supply voltage is too low).

If the part that failed shorted is something other than the '328, locating and removing that part (or parts) may restore the device to functioning. Unless it's a board with a removable '328p, you can't really verify that the '328 is still working prior to fixing the power supply problem - it may be the '328p that failed shorted, or the '328p may be otherwise damaged.

Usually it's the LM358 or the regulator itself that dies when you do that (and of course the 16u2 on official boards - that burns out if you even think about abusing the power rail)

[Flameblazer]

Thanks a lot everyone and sorry for the late reply . I'll first check if the 328 Chip is working. I currently don't have an Uno on me so that might take some time.

travis_farmer:
only if the programmer doesn't not supply power.

~Travis

I think the programmer is supposed to supply power since it has a 5V pin as the LED on the Uno lights up, but it is very dim.