Can not upload code, L (13) pin does not light up when plugged into my computer

Hello Everyone,

I have two Arduino boards communicating with each other being used for a capstone project (I will call them Arduino 1 and 2). Both of them were working last night. Last night one of my teammates was trying to establish I2C connection to a carbon dioxide sensor on Arduino 1. Code was able to be uploaded onto Arduino 1 and a LCD screen also connected was working at the end of the night.

This morning the LCD screen is on but nothing appears. We also can not upload code onto Arduino 1, with the correct COM port selected; After compiling it 'uploads' indefinitely.

When Arduino 1 is plugged into the computer, the green 'ON' light turns on but the L/13 pin light does not flash. When Arduino 2 is plugged into the computer, the green 'ON' light turns on, the L/13 pin light flashes for a few seconds, and the RX light flashes while there is power. Arduino 1 also is not responding to pushing the reset button, nothing appears to happen even though the green 'ON' light is consistently on when plugged into the computer.

Any help or advice about how to get Arduino 1 working again would be greatly appreciated!

Unplug EVERYTHING, and retry.

We have tried that and it did not fix the problem :frowning:

What type of Arduino do you have?

They are actually sparkfun RedBoards which we believe to be equivalent to an Arduino Uno. The computer is also still able to upload code onto the working Arduino.

So you DON'T have an Arduino then.

Never mind, try to load the bootloader using the working Redboard. GOOGLE will give you full instructions.

Thank you for the suggestion! I've been trying to upload a bootloader as instructed by youtube and am now receiving the following error. I have checked the wiring connections multiple times along.

avrdude: Version 6.3-20190619
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

Using Port : COM7
Using Programmer : stk500v1
Overriding Baud Rate : 19200
AVR Part : ATmega328P
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PC2
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :

Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack


eeprom 65 20 4 0 no 1024 4 0 3600 3600 0xff 0xff
flash 65 6 128 0 yes 32768 128 256 4500 4500 0xff 0xff
lfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
efuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
lock 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00
signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00

Programmer Type : STK500
Description : Atmel STK500 Version 1.x firmware
Hardware Version: 2
Firmware Version: 1.18
Topcard : Unknown
Vtarget : 0.0 V
Varef : 0.0 V
Oscillator : Off
SCK period : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.04s

avrdude: Device signature = 0x000000 (retrying)

Reading | ################################################## | 100% 0.04s

avrdude: Device signature = 0x000000 (retrying)

Reading | ################################################## | 100% 0.05s

avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
Double check connections and try again, or use -F to override
this check.

avrdude done. Thank you.

Error while burning bootloader.

If everything is wired correctly, and the correct chip is selected, this means your Microcontroller is dead!

Aw no that's not great! I'll try fiddling a little more but thank you so much for your help!

You NEED to do more fiddling if you hope to get this project working; consider the facts:
You had two similar setups.

Both were working at the end of the night, and the boards had previously been used without issue, until some additional work was done on them..

But on this night, while both were working in the evening, come morning. both are now dead.

Chances are that when you try to wire up replacements they will suffer the same fate!

So you need to figure out what happened.

How much current was that setup drawing? CO2 sensors are often power hogs; some generate considerable waste heat; could that have been cooking something?... some LCDs can pull a couple hundred mA, too (colored high res ones, though the backlit character ones can pull IIRC close to 100 with the backlight on... How was it powered? Hopefully not from a wallwart through DC barrel jack if the current is high, though all those LDOs are supposed to be over-temp protected, it doesn't seem to work all that well. You seem to have two boards that are very different levels of damaged - one of them, I reckon is nearly working (the one that gives you bootloader flashes and then causes one of the serial lights to flash (did the code that was on it periodically print to serial?)

Did you have any places where a voltage higher than 5v could have been getting onto a pin? Or where a pin set OUTPUT might be shorted to the opposite rail, or a pin trying to drive the other way? or trying to power something that is too large a load for it?

The board that gives bootloader lights is a better bet. If the chip is removable, I'd try a brain transplant with a working chip. you can upload with the chip in a known working board, check if any pins are stuck HIGH or LOW - if so, whatever was connected to that pin(s) that are now blown is suspect.

If you can't upload via USB, can you upload using programmer? Maybe upload bare minimum so all the pins are INPUT, and check if any of them are actually behaving like outputs (that's the normal blown pin failure mode).

A REDBOARD is not an Uno. The serial; chip on the REDBOARD is more durable to electrical abuse than the 16u2 on the Uno (but not reprogrammable, not that most users reprogram the 16u2). My instinct is that an Uno would have failed faster, if any difference. mentioning it as a caution against thinking you should get official boards for better results as the replacement, and winding up with ones that are easier to damage instead.

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.