Hardware Reference
In-Depth Information
Figure 3.33
■
CodeWarrior display error messages when there are errors in the program
This phase is entered by selecting
Debug
from the
Project
menu
or pressing the F5 function
key of the keyboard. The initial response of CodeWarrior varies with the connection methods.
I
NITIAL
R
ESPONSE
UNDER
S
ERIAL
M
ONITOR
Suppose the user has a Dragon12-Plus demo board (or other demo board) programmed with
the serial monitor; by pressing the function key F5, the debugger screen will look like that in
Figure 3.34. The user needs to select the COM port before she or he can proceed. After selecting
the correct COM port and clicking on OK, the debugger screen will change to that shown in Fig-
ure 3.35. This screen indicates that the debugger hasn't been able to successfully reset the MCU
yet. Press the reset button indicated in Figure 3.35, and the screen should change to that shown in
Figure 3.37.
I
NITIAL
R
ESPONSE
UNDER
THE
P&E M
ULTILINK
Suppose the user uses a P&E Multilink or a CyclonePro debugger to work with the
Dragon12-Plus demo board; the initial debugger screen after pressing the F5 function will look
like that in Figure 3.36. This screen asks the user whether it is OK to erase the flash memory
and download the program onto the memory. Click on OK and the screen will change to that
shown in Figure 3.37.
D
EBUGGER
S
CREEN
L
AYOUT
The CodeWarrior screen contains seven windows.
•
Source window.
This window holds the source code of the project.
•
Data window.
This window displays all the program variables (
sum
,
average
,
icnt
) declared by assembler directives. The values of each program variable will be
updated after each breakpoint is reached.
•
Command window.
The user can enter commands in this window to ask the
debugger to execute.
•
Assembly window.
This window contains the program as shown in the Source
window but it also displays the line number of each instruction.
Search WWH ::
Custom Search