It still be nice to see what your doing.
You can't have anything hooked to pin 0 and 1 or the reset
A picture of your board

 

I think you should stay the course. I was worried that if I posted that thread you would jump to the more familiar hardware angle

When you plug the UNO in, using the USB port on the Win 10 machine, is the green power light illuminated as in the picture below?



(sorry if you already answered this)

 

We have several posts and many suggestions. One of which I have not seen confirmed.

Are you running the Arduino IDE as Administrator?​

I have had similar problems with the IDE on Win 10. There are separate steps that must be taken each time to run the IDE, unless specific steps are taken the first time you install.

I start by installing a shortcut on the desktop. Then, before running it, I open up the desktop properties and under Security, I check the box to run as Administrator.

Then, I copy this customized shortcut to wherever I may run the IDE. Desktop, taskbar and from the apps menu. I also ensure to delete any original shortcuts.

When NOT running as Administrator, the drivers do not execute successfully and prevent the IDE from communicating with the board.

 

Could you post 2 good pictures one of the front and one of the back of your uno

I showed one of the front in my first post to this forum on 18th May, #72 here:
https://forum.allaboutcircuits.com/...o-controller-programming-skills.159472/page-4

 

When you plug the UNO in, using the USB port on the Win 10 machine, is the green power light illuminated as in the picture below?

Yes, as mentioned, the board runs the old sketch. The only aspects of that post that were abnormal were the three I showed.

 

We have several posts and many suggestions. One of which I have not seen confirmed.

Are you running the Arduino IDE as Administrator?​

Yes. Tried both modes.

 

Yes, as mentioned, the board runs the old sketch. The only aspects of that post that were abnormal were the three I showed.

OK, when you say it "runs" the old sketch, you mean that it is still running the last sketch that was flashed, as soon as you power up...not that it loaded and ran that sketch today.

Tomorrow's a new day...but I am still not convinced that it is bricked...not yet anyways

 

It still be nice to see what your doing.

I'm trying to upload any sketch!

You can't have anything hooked to pin 0 and 1 or the reset

As mentioned, nothing is connected to any pin.

A picture of your board

See my two replies earlier.

 

OK, when you say it "runs" the old sketch, you mean that it is still running the last sketch that was flashed, as soon as you power up...not that it loaded and ran that sketch today.

Tomorrow's a new day...but I am still not convinced that it is bricked...not yet anyways

From post #29:
"The chip is plainly working, at least to some extent, as it's still flashing the last sketch uploaded two days ago."

 

From post #29:
"The chip is plainly working, at least to some extent, as it's still flashing the last sketch uploaded two days ago."

Yes, I read that...and to me, when you say "flashing" it means that you are uploading and flashing the program. It only gets "flashed" once and then it stays there and is executed every time you power up... until you flash another program over it. It's easy to misunderstand and be misunderstood on forums.

 

Yes, I read that...and to me, when you say "flashing" it means that you are uploading and flashing the program. It only gets "flashed" once and then it stays there and is executed every time you power up... until you flash another program over it. It's easy to misunderstand and be misunderstood on forums.

Fair point. I was actually using 'flashing' to mean 'blinking'. Flashing on/off the built-in LED driven from pin 13. The upload was a minor variation of Blink.ino (enough to distinguish it from the built-in sketch).

I assume your 'flashing' is another term for 'uploading', similar to flashing new firmware?

 

@be80be: Here are the photos you asked for.

 

You can try this test (as described here). I just did this to test it out. I first loaded and ran Blink - selecting, of course, the correct port in the IDE. Then I unplugged the USB cable. I did not close the IDE.

I put a jumper from 0 to 1 - that's TX to RX and a second jumper from GND to RESET. Then I plugged the board back in. I heard the familiar "thunk" from the port recognition on my WIN 7.

Then I plugged the USB cable back into the UNO. The LED bit that was blinking stopped blinking - as it should.
Opening up the Serial Port window in the IDE, I type some text, click return and it appears in the output window.



As soon as I remove the reset jumper (and the TX to RX), the UNO resets and then starts the blink program again.

This means that I have the correct port selected and Windows agrees with that.

What do you get?

 

Raymond,

Thanks, but my new UNO arrived promptly this morning and I've just tested it successfully with a couple of sketches. So it was indeed a hardware issue. I must have damaged it somehow.

I'm off to the shed now but I'll be very surprised if it doesn't also work fine on my XP PC. I'll report back later.

 

Raymond,

Thanks, but my new UNO arrived promptly this morning and I've just tested it successfully with a couple of sketches. So it was indeed a hardware issue. I must have damaged it somehow.

I'm off to the shed now but I'll be very surprised if it doesn't also work fine on my XP PC. I'll report back later.

I'm glad the new one came in and it works.

It would be good to know what you did to brick it, IF you did anything. It is possible that it went bad through no fault of yours. Will you send it back?

Anyways, enjoy the shed.

 

Thanks Raymond. The new UNO worked fine on the XP PC. (Once I'd remembered that for some obscure reason it needs to run in Win 2000 Compatibility mode.)

Yep, wish I knew for sure what caused it, but I suppose it had to be the solenoid work, as per post #20:
"I can't remember exactly but at one stage I did drive a solenoid (with protective diode in parallel) via a power MOSFET. That was working OK. Then a bit later after editing that code the described symptoms arose."

 

Just been down the same frustrating route.....
Fixed the problem by setting the processor to ATMega328 (Old Bootloader) - I was unsuccessfully using the 'standard ATMega'

Very old thread but I hope this might help someone.
BR
Simon

 

Thanks for the feedback Simon.

Although my issue turned out to be down to my somehow zapping the USB interface, the thread is packed with valuable trouble-shooting tips. Thanks again to all who contrubuted, particularly to @Raymond Genovese and @be80be.

Terry, UK
(Still an Arduino novice, but learning gradually.)