Actions
Forum Thread Details
  • State Verified Answer
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 404 subscribers
  • Views 741 views
  • Users 0 members are here
Related

Arduino Programming debugging help

GreenYamo

Hello, I am new to the world of Arduino, but loving finding out all about it and experimenting.

 

I would like some advice on debugging programs on the IDE, from what I can see there is no sort of step through function to trace program execution, and no way to track the contents of registers and setting of pins (eg, as on the PICAXE ide).

 

Is there something I am missing?

 

Thank you.

 

Steve

Parents
  • 0

    Hi Steve,

     

    That's a good question and I think debugging is a downside to the Arduino environment.  I still save development time using it versus "raw" C or assembly, but debugging sometimes devolves into a rat's nest of print statements.

     

    Another e14 member actually asked this question last week:

     

    http://www.element14.com/community/message/49046#49046/l/re-debugging-atmega328

     

    There is a promising link in that thread which outlines an approach to step-by-step debugging.  I'm hoping to make time soon to try it out.

     

    Cheers,

    Drew

  • 0 in reply to fustini

    Hi Steve,

     

    I debug code on microcontrollers with print statments. Whenever I have a doubt about some variable, I will print it. Of course that often triggers me wanting to know the next (or previous) variable, so I'll have to recompile and download. But that's often very quick, so I don't mind too much.

     

    loop ()

    {

    static int t;

    if (t >= 1000)

      t = 0;

      printf ("pins on portA are: %x\n", PINA);

    } else t++;

    delay_ms (1);

    }

     

    (I don't remember what the delay function should be called under the arduino environment. I think printf just works like this. )
    Oh, and place an "serial.init (9600)'" in the initialization code.

     

    Then you can use the serial monitor to check for debug outptu.

Reply
  • 0 in reply to fustini

    Hi Steve,

     

    I debug code on microcontrollers with print statments. Whenever I have a doubt about some variable, I will print it. Of course that often triggers me wanting to know the next (or previous) variable, so I'll have to recompile and download. But that's often very quick, so I don't mind too much.

     

    loop ()

    {

    static int t;

    if (t >= 1000)

      t = 0;

      printf ("pins on portA are: %x\n", PINA);

    } else t++;

    delay_ms (1);

    }

     

    (I don't remember what the delay function should be called under the arduino environment. I think printf just works like this. )
    Oh, and place an "serial.init (9600)'" in the initialization code.

     

    Then you can use the serial monitor to check for debug outptu.

Children
No Data