Let's Make Robots!

problen uploading wild-thumper

Hi everyone!!!

I've been tried to upload my wild thumper but when it's imposible. I tried with arduino relax patch 0022 and arduino 0018 but they give me this menssage: 

Binary sketch size: 3984 bytes (of a 14336 byte maximum)


avrdude: stk500_getsync(): not in sync: resp=0x81

avrdude: failed to write flash memory, rc=-1

avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x80


The board is well selected in the arduino program, the port com too.


What can I do??



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

I have the problems with "usb unknown device", when I realize: WE CAN'T use the DC recharge socket as voltage source. We need to use VBAT/GND


with a 7.2v battery I can't do it work, only with a 12v.

Strange, maybe a defective board.


I have the same problem... I have a Wild Thumper Controller that is powered by a 7,2V 2200 mA LiPo battery. LED2 and LED5 are on, LED3 and LED4 start blinking fast when I plug in the USB cable, then blink both every second after. From the Arduino IDE I can not choose the WTC USB port!

I have updated my Arduino IDE to the latest version (1.0.1) and I am using a Mac with OSX Lion.

How do I re-install the bootloader? Can you post a detailed image of how to connect the ISP socket to the Arduino used as programmer?



The Wild Thumper sample code was written in version 0018 of the Arduino IDE, it needs to be modified to work with later versions. From what you say here, I doubt you need to re-burn the bootloader.It is more likely to be the USB driver.

Unfortunately I do not use a Mac so I cannot help you much.

Hello ducati!

I had a similar problem but in my case, I could select the WTC USB port all along. Anyway, it seem you'll have to re-install the bootloader. I did it with an Arduino 2560 board, but if you had another WTC board you could use it. In http://letsmakerobots.com/node/32096 OddBot (who is a genius) give us a good explanation how do it.

In case of you didn't have another board you can use an AVR-ISP, USBtiniISP, a parallel programmer (http://arduino.cc/en/Hacking/Bootloader to get more information) or an Arduino board as I told you before.

I suggest to you that you choose the last posibility if you have another boards (I did it in this way). In this moment, I'm out but, I promise you to post an image with the conexion needed between WTC and Arduino 2560 board tomorrow (if you need it).

best regards!!!


Hi, thanks for your interest and quick reply!

OddBot was right, I have tried uploading some code using a Windows machine and the WTC works without issues. I wonder why my mac can not recognize the WTC as usb device. All other Arduino Uno boards I use work great!



I was having troubles to burn code to the Arduino from the Wild Thumper Controller board. 

1) Arduino Diecimila or Duemilanova w/ATmega 168 selected.
2) Proper port selected. 
3) LD3 & LD4 blink.
4)avrdude: stk500_getsync(): can’t communicate with device: resp=0x41

So I decided to program the bootloader using an Arduino Uno as the ISP programmer.

1) Loaded Examples/ArduinoISP 
2) Targeted Board/Arduino Uno
3) Selected Port
4) Uploaded
5) Connected the Arduino Uno to the Wild Thumper Controller following:
http://arduino.cc/en/Tutorial/ArduinoISP and using the ICSP pins from the WTC 
6) Arduino IDE didn't recognize the Atmega168pa so I edited boards.txt as suggested in http://www.arduino.cc/cgi-bin/yabb2/YaB ... 76164280/0.
7) Selected Atmega168p
8) avrdude: stk500_paged_write(): (a) protocol error, expect=0x14, resp=0x11
avrdude: stk500_cmd(): programmer is out of sync 
9) Then I realized that was not going to work.
10) Updated avrdude to 5.11.1 (this version supports m168p)
11) Followed http://www.sparkfun.com/tutorials/247
12) Instead of m328p used m168p as follows:
avrdude -P /dev/ttyACM0 -b 19200 -c avrisp -p m168p -v -e -U efuse:w:0x05:m -U hfuse:w:0xD6:m -U lfuse:w:0xFF:m
13) Then selected the proper .hex file:
sudo avrdude -P /dev/ttyACM0 -b 19200 -c avrisp -p m168p -v -e -U flash:w:ATmegaBOOT_168_diecimila.hex -U -F lock:w:0x0F:m
14) Finally got this message:

Reading | ################################################## | 100% 0.12s

avrdude: Device signature = 0x1e940b
avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as D6
avrdude: safemode: efuse reads as 5
avrdude: erasing chip
avrdude: reading input file "ATmegaBOOT_168_diecimila.hex"
avrdude: input file ATmegaBOOT_168_diecimila.hex auto detected as Intel Hex
avrdude: writing flash (16294 bytes):

Writing | ############################################ | 87% 0.00s
avrdude: stk500_paged_write(): (a) protocol error, expect=0x14, resp=0x11
avrdude: stk500_cmd(): programmer is out of sync

I am out of bullets so I hope someone can help me. I guess I am doing something wrong with the Fuse Settings, but I don't know how to properly configure this Bits for the Wild Thumper Controller Board.

Did you have the power connected correctly? I get many cases where people do not realise that the controller cannot be powered by the USB and that they must power the controller with a suitable battery when programming.

The other problem is that people tend to connect the battery (usually 7.2V or higher) to the 5V output instead of the battery input. This puts battery voltage directly onto the MCU and fries it!




I checked the usb driver like psychofreaky told me, but it was correctly installed, even so, I reinstalled it but this didn't solve the problem neither.

I've check the LED 5 when I power it up and I've seen that it don't flash. When I connect the batery the LED 2 turn on and still on, the LED 4 turn on and quickly turn off and still off, but the LED 5 turn on and quickly turn off, a couple second later turn on and still on.

So I think I should re-installing the bootloader. In this moment I don't have a Parallel Programmer so I'll take a few days until post the result.


thank at all!!!

If your board has the ATmega168 20-AU chip then you can use an Arduino as your programmer. Unfortunately that chip is obsolete now and has been replaced with the Atmega168PA. This is the same chip manufactured using a smaller die. Unfortunately the engineers changed the device signature and this causes an error.