Arduino Duemilanove Stk500_recv and the reset button doesn't work


I'm trying to connect the Arduino Duemilanove or Diecimila( with the ATmega328P )with ROS.
Yet I don't understand a bit in ROS so just tried it out.
5 minutes ago everything worked fine. I have not changed anything in the settings from the Arduino IDE, so set ports and set board and the cable typically work.

I've written a quite big sketch, where the Arduino IDE already told me, that stability problems may occur due to the low memory available.
But I could also load this sketch on my Arduino.

Now when I'm trying to load another sketch on my Arduino Duemilanove I am gettin every time the avrude: stk500_recv(): programmer is not responding avrude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00 error code.

Since then I'm not able to load ANY program even the blink program on the Duemilanove.
I remember to solve this problem by just pressing the reset button and then try it again, but now when I'm pressing the reset button the RX and TX or any other LED don't blink.
What happened to my board and can I repair it?

Maybe it is important:
I ran Roscore and Rosserial_arduino ....
When I tried to upload my new sketch, I forgot to stop those running terminals.

And here was the sketch from my last working upload to the Arduino::

#include <ros.h>
#include <std_msgs/Empty.h>
#include <Arduino.h>

  #include <MotorWheel.h>
  #include <Omni3WD.h>
  #include <Omni4WD.h>
  #include <PID_Beta6.h>
  #include <PinChangeInt.h>
  #include <PinChangeIntConfig.h>

  irqISR(irq4,isr4);  // Interrupt function on the basis of the pulse, work for wheel1
  MotorWheel wheel4(3,2,4,5,&irq4); // MotorWheel object called wheel1 
                                  // Motor PWM, DIR, Enocder A, B
  MotorWheel wheel3(11,12,14,15,&irq3); 
  MotorWheel wheel2(9,8,16,17,&irq2); 

  MotorWheel wheel1(10,7,18,19,&irq1);

  Omni4WD Omni(&wheel1, &wheel2, &wheel3, &wheel4);

  int velocity = 200;

ros::NodeHandle nh;

void vorcb(const std_msgs::Empty& vormsg){

  ros::Subscriber<std_msgs::Empty> sub1("vorwaerts", &vorcb);
void rueckcb(const std_msgs::Empty& rueckmsg){

  ros::Subscriber<std_msgs::Empty> sub2("ruckwaerts", &rueckcb);
void rechtscb(const std_msgs::Empty& rechtsmsg){

  ros::Subscriber<std_msgs::Empty> sub3("rechts", &rechtscb);
void linkscb(const std_msgs::Empty& linksmsg){

  ros::Subscriber<std_msgs::Empty> sub4("links", &linkscb);
void cwcb(const std_msgs::Empty& cwmsg){

  ros::Subscriber<std_msgs::Empty> sub5("clockwise", &cwcb);
void ccwcb(const std_msgs::Empty& ccwmsg){

  ros::Subscriber<std_msgs::Empty> sub6("countercw", &ccwcb);

void setup() {
//TCCR0B=TCCR0B&0xf8|0x01;   wann muss ich das anmachen?



void loop() {


Thanks for your help and sorry for all the english grammar mistakes.

I suggest that you change the title; I nearly skipped your post because it states 'Due'. A Due is not the same as a Duemilanove (or Diecimila).

Can you please read How to get the best out of this forum and next apply in your post what you learned about code tags.

  1. What does your operating system think about the board?
  2. Have you tried the loopback test?
1 Like

What do you mean with your first question?
I tried it on Ubuntu and Mac OS
Both didn't work.

The loopback test works !

In the Linux (and probably Mac world), the two important commands are lsusb and dmesg; see what they show when you connect the board. But if the loopback test works, they will probably not reveal anything shocking that would indicate a problem.

So that would point to the main processor (328P); it might have been damaged without you knowing and is slowly dying. You can buy 328P processors with the Optiboot boot loader pre-programmed (DIP version only) and see if that solves the issue; you will have to program the board as an Uno in that case.

I solved the problem. Just needed to rewrite the bootloader on it:)

1 Like

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.