Evaluation Platform Board Manual 65
B.8 Exploring the Code|Lab Debug Windows
This section discusses some basics of the debug environment. Some of these windows an d concepts
have been dealt with during previous exercises in this man ual. However, many new window s are also
discussed and basic interaction exercises are given. Begin this section by launching the Code|Lab
Debugger environment and connection via the JTAG port.

B.8.1 Toolbar Icons

Placing the mouse arrow on any icon displays the text functio n of that icon. When the icon l aunches a
special window (i.e., Watch, Memory, Call Trace, etc.), the icon brings that window up on the first
click and removes the window when pressed again.

B.8.2 Workspace Window

Click on the Workspace icon. Click on the Files and Brow se tabs and examine the contents. Note that
there are more files than the original source files. When you doub le-click on the source files, blink.c
and led.c, the source window appears for that file. When you double-click o n an included file, the
debugger is not be able to find the file.

B.8.3 Source Code

The source code windows are opened by double-clicking on the source files in th e Workspace
window under the files tab. Viewing o f mixed Assembly and C code or C code only, is controlled by
the tabs at the bottom of these windows.

B.8.4 4 Debug and Console Windows

The Debug window displays d ebugger activity messages whi le the Debug tab is displayed. S cript
commands can be entered manually at the top o f the window. Serial output is displayed while the
Console tab is active. Command s for the running application can be entered at the top of th is window.

B.8.5 Memory Window

Click on the Memory window icon. Change the address at the t op of the window to 0xffffe100 and
click on the green arrow to the righ t (or press Enter). This changes the viewable star ting address of the
Memory window. The ATU header begins at 0xffffe100 and contains a known numb er (8086). Also
look at the base and limit re gisters for the memory and Flash devices, at 0xffffe508 and ffffe688
respectively, since they were initialized by RedBoot. Use the Intel® 80332 I/O Processor Developer’s
Manual, to see what the values mean.
Note: The tabs at the bottom allow the selection of two memory regions to observe.