User`s manual

Dynamic C User’s Manual digi.com 255
14.2.5 Run Menu
Click the menu title or press <Alt+R> to select the RUN menu.
Run
<F9>
Starts program execution from the current breakpoint. Registers are
restored, including interrupt status, before execution begins. If in
Edit mode, the program is compiled and downloaded.
Stop
<Ctrl+Q>
The “Stop” command stops the program at the current point of exe-
cution. Usually, the debugger cannot stop within nodebug code. On
the other hand, the target can be stopped at an RST 028h instruction
if an RST 028h assembly code is inserted as inline assembly code
in nodebug code. However, the debugger will never be able to
find and place the execution cursor in nodebug code.
Run w/ No Polling
<Alt+F9>
This command is identical to the “Run” command, with one excep-
tion. The PC polls the target every three seconds by default to
determine if the target has crashed. When debugging via Rabbit-
Link, polling is used to make the RabbitLink keep its connection to
the PC open. Polling does have some overhead, but it is very mini-
mal. If debugging ISRs, it may be helpful to disable polling.
Step Into
<F7>
Executes one C statement (or one assembly language instruction if the assembly window is displayed)
with descent into functions. If nodebug is in effect and the Assembly window is closed, execution
continues until code compiled without the nodebug keyword is encountered.
Step Over
<F8>
Executes one C statement (or one assembly language instruction if the assembly window is displayed)
without descending into functions.
Source Step Into
<Alt+F7>
Executes one C statement with descent into functions when the assembly window is open. If
nodebug is in effect, execution continues until code compiled without the nodebug keyword is
encountered.
Source Step Over
<Alt+F8>
Executes one C statement without descending into functions when the assembly window is open.
Toggle Breakpoint
<F2>
Toggles a soft breakpoint at the current cursor location. Soft breakpoints do not affect the interrupt
state at the time the breakpoint is encountered, whereas hard breakpoints and hardware breakpoints do.
Starting with Dynamic C 9, breakpoints can be toggled in edit mode as well as in debug mode. Break-
point information is not only retained when going back and forth from edit mode to debug mode, it is
stored when a file is closed and restored when the file is reopened.