next topic »

[on:]

Hello,
    I am getting to the point where Serial.println debugging is not cutting it for understanding what is going on my my programs and want a debugger to allow me to step through them.  I am new to using debuggers/emulators and could use some recommendations.  Should I invent in a Dragon?

    I plan on using this for production stuff (eventually).

Thanks in advance

[Reply #1 on:]

Although it may sound old fashioned - pen and paper is still a good debugging tool. Writing down what you see, what you expect.
Write down how a variable changes when you read through the code helps a lot.

You can also use one or more free pins and a LED to check paths.
Sometimes for fast signals another Arduino can be a tool of choice (read data from serial or i2C and compare it with what you expect.

What kind of application are you trying to debug?
Can you post the code?

[Reply #2 on:]

Although it may sound old fashioned - pen and paper is still a good debugging tool. Writing down what you see, what you expect.
Write down how a variable changes when you read through the code helps a lot.

You can also use one or more free pins and a LED to check paths.
Sometimes for fast signals another Arduino can be a tool of choice (read data from serial or i2C and compare it with what you expect.

What kind of application are you trying to debug?
Can you post the code?

As I don't want to duplicate posts, I put the code in this thread http://arduino.cc/forum/index.php/topic,144778.0.html

Thanks for your reply.

[Reply #3 on:]

I find (at work in real life) that debuggers/emulators are something that should never be used. And trying to use one with interrupts is just not on.

Mark

[Reply #4 on:]

Interrupts are about the only time I'd consider using an in-circuit emulator.