Specifications

Testing with Code Composer Studio
3-6
interrupts and hardware interrupts to occur. Chapter 5 through
Chapter 7 explain these types of events.
10) Choose File
→
Save or press Ctrl+S to save your changes to hello.c.
11) Choose Project
→
Options. Choose the Preprocessor category. Remove
FILEIO from the Define Symbols box in the Compiler tab. Then click OK.
12) Choose Project
→
Rebuild All or click the (Rebuild All) toolbar button.
3.3 Testing with Code Composer Studio
Now you can test the program. Since the program writes only one line to a
LOG, there is not much to analyze. Chapter 5 through Chapter 7 show more
ways to analyze program behavior.
1) Choose File
→
Load Program. Select the program you just rebuilt,
myhello.out, and click Open.
2) Choose Debug
→
Go Main. A window shows the hello.c file with the first
line of the main function highlighted. The highlighting indicates that
program execution is paused at this location.
3) Choose Tools
→
DSP/BIOS
→
Message Log. A Message Log area appears
at the bottom of the Code Composer Studio window.
4) Right-click on the Message Log area and choose Property Page from the
pop-up window.
5) Select trace as the name of the log to monitor and click OK. The default
refresh rate is once per second. (To change refresh rates, choose
Tools
→
DSP/BIOS
→
RTA Control Panel. Right-click on the RTA Control
Panel area and choose Property Page. Choose a new refresh rate and
click OK.)
6) Choose Debug
→
Run or press F5.
The hello world message appears in the Message Log area.
7) Choose Debug
→
Halt or press Shift F5 to stop the program. After the main
function returns, your program is in the DSP/BIOS idle loop, waiting for
an event to occur. See section 3.5, page 3-10 to learn more about the idle
loop.
8) Close the Message Log by right-clicking and selecting Close. This is
necessary because you will use the Profiler in the next section.