I recieved my first board late last night and had it running for a couple of hours. I tried a couple of the examples out of the makezine arduino book. I think while playing around with some leds i managed to short something on the board because it stopped responding to my laptop. Everytime i plugged the board in, windows would display "usb device not recognised".
This morning i managed to put the board into dfu mode and somewhat flash it using flip. This is the first time i have done this and struggled to comprend the tutorials due to the lack of information on the rev 3 board. Under dfu mode the board is installed as a ATMEGA16u2 device. I selected the same device under flip and uploaded the file "Arduino-usbserial-atmega16u2-Uno-Rev3.hex".
After resetting the board it has been sucessfully re-installed as Arduino UNO R3 (COM3) under ports (com & lpt) which i thought was great news until i tried uploading a example sketch in the arduino ide. While uploading the "blink" sketch i got the error "avrdude: stk500_getsync(): not in sync: resp=0x00". I have check it is the right port, i have tried changing the port number, using a different cable, resetting the board before upload, re-istalling the drivers and restarting my laptop to no avail.
I need to start prototyping some circuit for use in our formula student car asap so any help would be greatly appreciated.
Board: Arduino Uno Rev 3
Operating system: Windows 7 64bit
I've just tried that with a number of different ports but the same error message is displayed. I also tried the loop back test, the board is visable to the laptop and the arduino ide software but i dont get any response in the serial monitor.
If i can't fix the board and have it operational in the next few days I will send it back and get a replacement.
Yeh it connects to the computer fine. It makes the connection sound, the board is fully powered up, it's visible in device manager and selectable in the arduino ide.
I'm wondering if i've made a mistake while flashing it or damaged the hardware on the board.
Well to reset it to DFU i found i had to bridge the gnd and reset headers and then gnd the right hand side of the closest resistor just above the "RESET EN" solder points.
I've noticed that the RX and TX led's are not lighting up when i try and upload a program anymore. I tried the loop back test without the atmega328 in and i had the same disappointing results. Although the chip is showing it's self as a usb device on my computer it doesn't seem to be able to respond to any serial data.
I guess that now that the software isn't a problem it must be a hardware fault. Is there anything else i can do to save the board or should i just send off for a replacement in the morning?
You are going to have to get a 10K resistor onto those RESET EN pads to pull that Reset pin. You can solder (problem if you are going to return it tomorrow) or pressure it onto the pads just for the hex file upload. Upload Arduino-usbserial-atmega16u2-Uno-Rev3.hex. After that, see what it does.
If that does not work, switch ICSP to the Arduino and flash the UNO bootloader on the Atmega328 through the Arduino IDE. I am not sure how you FLIP'd the 16u2 without the RESET enabled.
Well the hex file seemed to upload fine the other day when i reset it using a couple of ground jump leads. Once i uploaded the file the board started to show up as a arduino uno rev 3 (com3) instead of a unrecognised device. I can try it again but i've done this process a couple of times. I'll upload a picture of the board and the points i used, i found it on another forum.
How do i switch ICSP to the arduino chip? I've tried uploading the bootloader again through the ide but get the same error "avrdude: stk500_getsync(): not in sync: resp=0x00"
As I stated in my earlier post, if the loopback does not work then you have isolated the problem to the 16u2 side of the board. Until that works, I would not even worry about the atmega328.
At this point, it seems as if the 16u2 has been damaged and you should could consider getting a new board.
Cheers for all your help on this problem, i've decided that it's not worth it to mess around with the board anymore. I sent it off this morning for a replacement. Hopefully the next one will be more reliabe and i'll be a hell of a lot more carefully with it.#