Phytec nanoModul-164, Быстрый старт

Страница: 83 / 96

Debugging

PHYTEC Meßtechnik GmbH 2003 L-379e_4
79
•
Click in line 42 of the C source code (the line-counter is
displayed at the bottom of the µVision2 window) and choose
Run to Cursor line from the Debug Toolbar.
•
Now choose Step into few times and look how the variable
values are changing in the Watch Window.
4.7 Resetting Simulator and the nanoMODUL-164
•
Debugger in Simulator mode: When you are using the simulator
(i.e. no connection to target hardware), pressing the Reset CPU
icon
does not cause a running simulation to stop at the current
point of execution. Reset CPU starts the application from the
beginning address (0) again. Press the Halt button
to halt a
program under normal conditions.
•
Debugger in Monitor mode: The Monitor runs in the target
hardware. A Debugger reset sets the IPC to zero and performs other
initialization routines if no user application was started. It is not as
complete as a hardware-reset (pressing S1 on the Development
Board). The best method of stopping a running application is to
press the Halt button rather than the Reset CPU in Monitor mode.
Halt tries to stop a running application when the ’Serial interrupt
or NMI’ option is enabled. If this option is not enabled, a dialog
box is displayed in which you can select the next step. This has the
advantage of detecting any ‘infinite loop‘ in which your program
might be stuck. With reset, you start again at address 0.
•
The PHYTEC Development Board does not have a hardware NMI
button. A NMI is the most reliable way to stop a running program.
This is even more important when you are using the Bootstrap
version of the Monitor because it is difficult to re-synchronize the
Debugger and the kernel. For example, it is not possible for the
Debugger to re-synchronize automatically by pressing the
hardware-reset button (S1) if the monitor has been downloaded
with the Bootstrap Loader. It must be restarted manually by
restarting the Debugger.