UNO R3/When it does not work/06. Troubleshooting checklist
When it does not work · 06 of 6

Troubleshooting checklist

Nine things that go wrong with an UNO, and the checks for each in the order that finds the cause fastest. Most of them are the cable, the Tools menu, a pin with no pinMode, or something wired where it should not be, and each one points to the page of this book that explains it.

Check in order

From the symptom to the cause
No ON lamp
The symptom
No ON lamp means no 5 V rail. It is the cable, or something shorting the rail, far more often than the board.

Each symptom has a chain of checks, cheapest and commonest first. The first box is the answer more often than the rest together. Work down until one fits, then read the article named under it.

No ON lamp

The green ON lamp sits on the 5 V rail, so no lamp means no 5 V. Try another cable and another USB socket first. Then pull everything off the headers: a wire from 5V or 3V3 to GND trips the 0.5 A resettable fuse behind the USB-C socket, and it resets itself once it has cooled with the board unplugged. Four ways to power it and the 5V and 3V3 pins have the details.

No port

The ON lamp lights and the Tools menu shows no new port. A charge-only cable is the commonest cause; a cable that has ever uploaded is the test. Then the driver: the board's USB chip is a CH340C, and if no port appears, install the latest CH340 driver from WCH, the company that makes it. The CH340 driver and Board and port.

Upload fails

Check Board: Arduino Uno and the port that disappears when you unplug. Then unplug anything on D0 or D1: they are wired straight to the CH340C, and a module there fights it (Serial on D0 and D1). Then close any other program that has the port open. When the upload fails has the error messages.

Serial garbage

The Serial Monitor's baud menu does not match Serial.begin. Set it to the number in the sketch. The Serial Monitor.

A pin that reads wrong

A pin with no pinMode and nothing connected floats and reads at random (the floating input). With INPUT_PULLUP the logic is upside down: LOW is pressed (INPUT_PULLUP). Two or three counts per press is bounce (debouncing).

Analogue that wanders

An analogue pin with nothing on it reads noise (analogRead). If every reading drifts together, the reference is moving: DEFAULT is the 5 V rail, and USB 5 V is not exact (the reference, measure the board's own supply).

A PWM pin that stops

tone() takes Timer2, which stops PWM on 3 and 11. The Servo library takes Timer1, which stops PWM on 9 and 10. Only the six pins marked ~ do PWM at all. tone(), Servo and the timers they take and the six ~ pins.

The board is warm

Unplug first. A warm ATmega328P usually means an OUTPUT pin wired to GND or 5V, or a load that asks a pin for more than the 20 mA to design to (how much a pin can give). A warm regulator on the barrel jack is the AMS1117 turning the difference between the jack voltage and 5 V into heat, and more so at higher voltages and loads (four ways to power it).

It resets by itself

If it happens only when the Serial Monitor opens, that is the auto-reset: the CH340C's DTR line reaches RESET through a capacitor, and uploads depend on it. If it happens under load on USB, the 0.5 A fuse is tripping or the supply is sagging; if the chip carries the standard Uno fuse settings, its brown-out detector resets it when its supply falls to about 2.7 V. If it happens after the sketch has run a while, look for large arrays or long strings that run SRAM out (flash, SRAM and EEPROM).

When it does not work

None of these symptoms matches

Unplug everything from the headers, upload Blink, and check the L lamp. If that works, the board is fine and the fault is in what was connected or in the sketch. Add things back one at a time until it stops.

It worked yesterday and nothing changed

Something did: a different cable, a different USB socket, an IDE or board-package update, or a wire that moved. Retrace those before suspecting the board. A board that uploads Blink is not broken.

Two symptoms at once

Start with the one higher on this page. Power comes before the port, and the port before the upload, so fixing the first often clears the second without touching it.

Where this goes next

Everything about the chip and the Arduino IDE is in one book shared with the Nano. It starts with installing the IDE.

The ATmega328P book: install the Arduino IDE →

Edit this page — content/books/uno/troubleshooting.mdx

Community

Questions about this product

See what other owners have asked, and read their solutions.

Ask a question ↗

UNO R3 USB-C (ATmega328P)

Loading discussions…

Discuss this article

Ask about this page. The answer stays here, on the page it belongs to, for whoever hits the same wall next.

Browse Modules and blocks on the forum →