Texas Instruments TMS320C6 Series, Руководство пользователя

Страница: 48 / 304

Execute Some Code / Become Familiar With the Four Debugging Modes
2-12
Execute some code
Let’s run some code —not the whole program, just a portion of it.
Important!
You will be looking at the contents of the PC register in this lesson.
If you cannot see the contents of the PC register in your CPU window, either
resize your CPU window or scroll down until you can see the PC value.
Execute a portion of the sample program:
go main
The label in the COMMAND window changes
to COMMAND [RUNNING...] to indicate
that your program is executing.
You’ve just executed your program up to the point where main() is declared.
Notice how the display has changed:
-
The current PC is highlighted in both the DISASSEMBLY and FILE
windows.
-
The object codes of the first several statements in the DISASSEMBLY win-
dow have changed color because these statements are associated with
the current C statement (which is highlighted in the FILE window).
-
The CALLS window, which tracks functions as they’re called, now lists
main().
-
The color for the value of the PC in the CPU window has changed because
the PC’s value changed during program execution.
Become familiar with the four debugging modes
The debugger has four basic debugging modes:
-
Mixed mode shows both disassembly and C at the same time.
-
Auto mode shows disassembly or C, depending on what part of your
program happens to be running.
-
Assembly mode shows only the disassembly, no C, even if you’re
executing C code.
-
Minimal mode shows only the COMMAND window (no C or
disassembly).
When you opened the FILE window in a previous step, the debugger switched
to mixed mode; you should be in mixed mode now. (You can tell that you’re in
mixed mode if both the FILE and DISASSEMBLY windows are displayed.)