Hello,
Whenever I try to upload a sketch to my new rainbowduino I get the error "stk500_recv(): programmer is not responding". I have tried all of the "voodoo" out there regarding pressing the reset button at the perfect moment but nothing has worked. Does anyone have any suggestions on what I can try. I'm starting to think that the chip is bad.
thnaks,
Ben
Hello,
I just got a rainbowduino but am having issues uploading a sketch to it. I have looked all over the forum and the internet but noting suggested to other people has worked for me. I have tried pressing the reset button at tons of different times during/before the upload process as suggested by some people with no result. The error I am getting when uploading is "stk500_recv(): programmer is not responding". Does anyone have any suggestions? I'm starting to think that my chip is bad.
Chip: Rainbowduino ATmega328
Computer OS: windows 10
avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch
System wide configuration file is "C:\Users\Mark\Desktop\arduino-nightly\hardware\tools\avr/etc/avrdude.conf"
Using Port : COM3
Using Programmer : arduino
Overriding Baud Rate : 57600
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x53
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x53
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x53
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x53
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x53
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x53
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x53
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x53
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x53
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x53
avrdude done. Thank you.
Problem uploading to board. See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions.
Is the board recognized in Windows?
Have you installed the FT232 drivers for that board ?
Windows 10 also usually means there is a chance you are using USB 3.0
Sometimes that can be a problems with Arduinos so make sure you are using a USB 2.0 port.
If you don't have a USB 2.0 port insert a USB 2.0 "POWERED" hub between the USB 3.0 port and the Arduino.
When I plug in the chip it does show up in the com port list and I didn't install any drivers other than the ones I already had installed.
I tried plugging it into a USB 2 port but I still get the same error message.
Any other ideas?
The board does show up in device manager when I plug it in.
There is a topic at the top of the forum called "loopback test"
You might want to try that.
Hello,
I am trying the loop back test to see if my board is talking to my computer but I am having issues understanding how to do step 3.
"3. Force the processor to remain in reset by connecting a jumper from RESET to GND"
I have a rainbowduino and I can not fine a RESET connector on it anywhere. Can you please help me with this? The link below shows what board I have.
Thanks!
@bensmith0388, I see you have been cross-posting. Please stop.
bensmith0388:
I have a rainbowduino...
...which uses an FTDI adapter. Forcing the processor into reset is irrelevant. If you suspect the FTDI adapter is not working correctly, disconnect it from the Rainbowduino then connect a jumper between TX and RX. The reset of the loop-back steps are essentially the same.
I am new here and didn't know where to post my question.
By FTDI adapter do you mean the USB connector on the board?
bensmith0388:
I am new here and didn't know where to post my question.
Willful ignorance is not an excuse. This is at the top of EVERY SECTION...
http://forum.arduino.cc/index.php?topic=148850.0
By FTDI adapter do you mean the USB connector on the board?
Any of these look familiar...
https://www.google.com/search?q=FTDI+adapter
Looks like the board has an onboard ftdi chip.
So it does. I apologize.
Let's build some board, slap an Atmel chip on it and call it crapDuino.
No support needed, 'cause they'll end up with their questions at the Arduino forum..
If this is your board, the reset pin is at the red arrow (there's a text ´RST´ right there).
One of the available GND pins (male in this case) is at the blue arrow.
You can also keep pressing the reset button during your test, does the same thing.
By the way, looks like both sterretje as well as Coding Badly are right.
You can daisy-chain these boards.
And the means to do so, offers a nice way to also use an external adapter board to be able to upload to this board, so it seems (all pins seem to be available, looking at the above picture)
Thanks for the visual MAS3 I was able to run the loop test but had no results. The lights on the board light up but nothing is echoed back when I enter stuff into serial monitor. So if nothing is echoed back what does that mean?
The USB cable is defective.
The USB-to-serial converter is damaged.
There is a loose connection at one or both ends of the USB cable.
The USB-to-serial converter is not powered.
The logical next step is to try a different USB cable (one known to work).
I have tried multiple USB cables and ports all of which are known to work.
When you say the USB-to-serial converter is not powered does that mean that I need to have a power supply plugged into the board when I am uploading to it?
I have no idea. I assume the board would be powered, including the converter, when it is connected to a USB port.
Yeah that is what I would think too. I did try powering the board in addition to the usb and had the same results so I do not think that is needed.