2.1 Code composer studio tutorial  (Page 2/2)

After you select your file, click Open .

Executing, halting, or stopping your program

To execute your program, select Debug --> Run or press the F5 key:

Your program will then begin to run. You will see the following at the bottom left-hand corner of the Code Composer Studio environment:

To stop running your code, select Debug --> Halt:

You should then see the following at the bottom left-hand corner of the work environment:

To resume running your code, press the F5 button.

Debugging your code

Since there are few of us that can get our code working right the first time, you will probably have to debug your code. To figure out what could be wrong, there are several methods you can use to break the problem down.

Setting breakpoints

To execute your code a little at a time or to stop it after a certain point, you can place breakpoints. You can do this by placing the cursor on the line you want to set the breakpoint on, highlighting it by clicking once, and double-click. You should see a solid red circle on the left:

You can set as many as you like. Rebuild and reload the program. Execute it. The DSP will stop at the first breakpoint. To get to the next breakpoint, press the F5 button to run the DSP again.

To remove the breakpoint(s), place the cursor on the line, highlight it by clicking once, and double-click. The solid red circle should disappear:

Watching variables

To see what values your variables, constants, and/or registers are getting, you can view them in a watch window. Select View --> Watch Window . You should see the following appear in the Code Composer Studio environment:

Click on the ‘Watch 1’ tab:

To add a variable, double-click on the row under the ‘ Name ’ column:

Type in the name of the variable and press the Enter key:

You can change the base of the value by clicking on the ‘ Radix ’ column and selecting how you want to view the value.

Profiling sessions

You can benchmark your code by profiling a session. To do this, you can set one breakpoint at the line where you want the counter to start counting and another breakpoint at where to stop.

Select Profiler --> Start New Session… You will see the following dialog:

Type in a name for your profile session and click OK .

A window will appear at the bottom:

To profile a function, you need to add it to the profile session you just created. Double-click on the file you want to do this in, and place the cursor on any line inside the function and right click. Choose Profile Function --> in (session-name) Session .

Execute the code. When the CPU stops, click on the ‘ Functions ’ tab to see the result of the profiling.

Counting clock cycles

If you just want to count the cycles and do not need all the stats from profiling, you can just view the clock. Select Profiler --> View Clock :

The following window should appear at the bottom:

After setting up your breakpoints, reset the PC to start at the beginning of your code by selecting Debug --> Reset . Run your code. Clear the clock by double-clicking on it, and then run it again. The number of clock cycles will appear in the clock window.

Troubleshooting

If you are having any trouble, sometimes it is best to reset the CPU. You can do this by selecting Debug --> Restart CPU . You will have to reload the program.

Another option is to simply quit Code Composer Studio by selecting File --> Quit and restart the application.