Phytec phyCORE-ADuC812, Быстрый старт

Страница: 55 / 86

Debugging
© PHYTEC Meßtechnik GmbH 2002 L-462e_2
51
4 Debugging
This Debugging section provides a basic introduction to the debug
functions included in the Keil software evaluation development tool
chain. Using an existing example, the more important features are
described. For a more detailed description of the debugging features,
please refer to the appropriate manuals provided by Keil.
The µVision2 Debugger offers two operating modes that can be
selected in the Project|Options for Target phyCORE-ADuC812
dialog:
•
The Simulator allows PC-based microcontroller simulation of
most features of the 8051 microcontroller family without actually
having target hardware. You can test and debug your embedded
application before the hardware is ready. µVision2 simulates a
wide variety of peripherals, including the serial port, external I/O,
and timers. The peripheral set is selected when you select a CPU
from the device database for your target.
•
Advance GDI drivers, like the Keil Monitor 51 interface, allow
target-based debugging. With the Advanced GDI interface you
may connect directly to the target hardware. Debugging on the
target hardware also enables testing peripheral components of the
application.
The following examples utilize the Keil Monitor 51 interface.
Note:
Use of the monitor program requires protection (reservation) of some
controller resources, such as the serial interface, the serial interrupt
and timer 1. These resources are necessary to allow communication
between the monitor program on the target hardware and the
µVision2 Debugger (refer to the Keil Getting Started Manual for
further information). Do not use these resources when developing an
application program to be debugged using the Keil Monitor 51
interface.
Before using the Keil Monitor 51 interface, a special *.hex file
(the monitor firmware) must be downloaded to the target hardware.