But I don't get how the debugger is supposed to work.

I get the following in my output window.

It seems to stop at the break point that I set in my loop function.

But hitting F10 (step over) just causes it to run so that it stops again at my break point. There does not seem to be any way to step through each line of code.

Program Started 'POVClockMultiplexed'
20:47:15.343 POVClockMultiplexed.ino, line 137	loop()
POVClockMultiplexed is paused at POVClockMultiplexed.ino, line 137, loop()
POVClockMultiplexed Running
20:47:28.156 POVClockMultiplexed.ino, line 137	loop()
POVClockMultiplexed is paused at POVClockMultiplexed.ino, line 137, loop()
POVClockMultiplexed Running
20:47:30.531 POVClockMultiplexed.ino, line 137	loop()
POVClockMultiplexed is paused at POVClockMultiplexed.ino, line 137, loop()
POVClockMultiplexed Running
20:47:32.406 POVClockMultiplexed.ino, line 137	loop()
POVClockMultiplexed is paused at POVClockMultiplexed.ino, line 137, loop()
POVClockMultiplexed Running
20:47:35.578 POVClockMultiplexed.ino, line 137	loop()
POVClockMultiplexed is paused at POVClockMultiplexed.ino, line 137, loop()
POVClockMultiplexed Running
20:47:38.890 POVClockMultiplexed.ino, line 137	loop()
POVClockMultiplexed is paused at POVClockMultiplexed.ino, line 137, loop()
POVClockMultiplexed Running
20:47:40.875 POVClockMultiplexed.ino, line 137	loop()
POVClockMultiplexed is paused at POVClockMultiplexed.ino, line 137, loop()
POVClockMultiplexed Running
20:47:52.062 POVClockMultiplexed.ino, line 137	loop()
POVClockMultiplexed is paused at POVClockMultiplexed.ino, line 137, loop()
POVClockMultiplexed Running
20:47:53.718 POVClockMultiplexed.ino, line 137	loop()
POVClockMultiplexed is paused at POVClockMultiplexed.ino, line 137, loop() 

The fact that single stepping is not supported is documented here:
http://www.visualmicro.com/page/User-Guide.aspx?doc=Debugging-Differences.html

This document is linked from the main debugging documentation page:
http://www.visualmicro.com/page/User-Guide.aspx?doc=Debugging.html

Single stepping would require hardware support in the CPU, which the 8 Bit Atmel CPUs do not provide.

We have prepared a step-by-step debugging tutorial that we will publish in the next few days, and which is intended to help people with their first steps with Arduino/Visual Micro debugging.

Regards,
Heinz Kessler - Visual Micro

Hi,

The only limit on the number of breakpoints is the amount of memory available on the Arduino. Normally this would be quite a few.

One command to go to the next breakpoint is pressing F5 or the "Green Arrow >" toolbar icon

NOTE: If your own code reads the serial then you will have problems with break/continue and instead should use a different serial port or digital pin(s) for the debugger

Hi,

Could you please show a screen shot of the entire ide when stopped at a breakpoint.

I don't think sending a c applies to you. This is for when the Ide does not know the Arduino was already stopped at a breakpoint when the debugger started. It relates to the "send" box on the serial monitor. Type the c character using your keyboard then press the "send" button. Under normal operation this is the same as pressing F5.