AVR Freaks

A programmer only puts code into an AVR.

 

A debugger first puts code into an AVR then it "latches onto it" as it runs allowing you to stop it at any moment and take a look at what's going on inside.

 

Debugging Arduino interferes with normal Arduino operation (to the point where you have to make a small circuit modification) so, like I say, probably best to just stick to added Serial.println() to get clues about what's going on "inside"

You can create you own equivalent to println(). Just fill a buffer with the characters you want to send out the serial port (probably as a null-terminated string - that is as good a way as any). Then call a function that outputs the character, increments a buffer "index", waits for the USART to become empty and repeats (until a null character is detected in the buffer). Its not such a big deal! Works fine in asm. Its a little more complex if you want non-blocking operation but that will get you started.

 

Jim

Do you actually have any bugs?  How is your program misbehaving?  Put some real thought into it.  I might have used an avr debugger once or twice in 15 years.   Use the scope and spit out a few values in serial is usually what it takes.

Now using PICs, I have used debuggers somewhat more....go figure!

If you mean you are simply using an Arduino board because it is a well designed board and you don't intend to use Arduino features (IDE, library, bootloader etc) then get one of Atmel's AVR debug interfaces (cheapest of which is Snap), make the well documented mod to Arduino so that debugWire is free to opeate then wire up the Snap (etc) to it and you can use "proper debugging" in AS7.