1. “Code Composer Studio (CCS)”

2. Code Composer Studio
The Code Composer Studio (CCS) application provides an integrated environment with the following capabilities:
Integrated development environment with an editor, debugger, project manager, profiler, etc.
‘C/C++’ compiler, assembly optimiser and linker (code generation tools).
Simulator.
Real-time operating system (DSP/BIOS™).
Real-Time Data Exchange (RTDX™) between the Host and Target.
Real-time analysis and data visualisation.

3. LAB: What is a Project? Project (.PJT) file contains
Project files (by reference):
Source
Libraries
Linker, etc …
Project settings:
Build configurations (compiler, asm options)
DSP/BIOS
Linking, etc …

4. LAB: (1) Create a new projects

5. LAB: Add files to the project
(2) Add files to the project (source, command, library)

6. LAB: Compiler Build Options
Nearly one-hundred compiler options available to tune your code's performance, size, etc.
Following table lists most commonly used options:
Options Description
-mv6700 Generate ‘C67x code (‘C62x is default)
-mv6400 Generate 'C64x code
-fr <dir> Directory for object/ouput files
-q Quiet mode (display less info while compiling)
-g Enables src-level symbolic debugging
-s Interlist C statements into assembly listing
-o3 Invoke optimizer (-o0, -o1, -o2/-o, -o3)
-gp Enable function-level profiling
-k Keep asm files, but don't interlist
debug
optimize
(release)

7. LAB: Two Default Build Configurations
-g -q -fr"c:\modem\Debug" -d"_DEBUG" -mv6700
For new projects, CCS automatically creates two build configurations:
Debug (unoptimized)
Release (optimized)
-q -o3 -fr"c:\modem\Release" -mv6700
Notice that these default configurations do not contain -s or -k. Personally, I'd have added them to the configurations … but the tool developers didn't. Of course, you can modify them if you like. In fact, you probably will come up with your own favorite configurations.

8. LAB: Two Default Build Configurations
-g -q -fr"c:\modem\Debug" -d"_DEBUG" -mv6700
For new projects, CCS automatically creates two build configurations:
Debug (unoptimized)
Release (optimized)
Use the drop-down to quickly select build config.
-q -o3 -fr"c:\modem\Release" -mv6700

9. LAB: Build Options GUI -g -q -fr"c:\modem\Debug" -d"_DEBUG" -mv6700
These are the default build options for a new project
GUI has 8 pages of options for code generation tools
Basic page defaults are -g -mv6700

10. LAB: Linker Options Options Description
-o<filename> Output file name
-m<filename> Map file name
-c Auto-initialize global/static C variables
-x Exhaustively read libs (resolve back ref's)
-q -c -o".\Debug\lab3.out" -x
.\Debug\lab3.out
Run-time Autoinitialization
Like Compiler Options, Build Configurations also contain Linker Options
Default linker options are shown for the Debug configuration of a project name lab3.pjt
".\Debug\" indicates one subfolder level below project (.pjt) location
Linking discussed in detail during four-day workshop

11. LAB: Configuration Tool
Simplifies system design
Automatically includes the appropriate runtime support libraries
Automatically handles interrupt vectors and system reset
MEM handles system memory configuration (builds CMD file)
Many other capabilities will be discussed later …

12. LAB: Config Tool
OK, here are the numbers you’d like everyone to get and compare against each other.
Sorry, we’re not providing them for you. Every time the tools get rev’d they change (for the better!).
The main point:
Optimizer kicks butt over no optimization!

13. LAB: Build (3) Build the output program (lab1.out):
(a) Build the project by:
(i) Clicking the Rebuild All toolbar icon.
(ii) Selecting Rebuild All in the project menu.
(b) Verify that the build output window is complete with “0 errors, 0 warnings”:

14. LAB: Load Program (4) Load the output file lab3.out into DSP memory:
(a) Load the lab3.out by selecting File:Load Program as shown below:

15. LAB: Watch variables (5) Debug and run code:
(a) Go to the beginning of the program, that is main() by selecting Debug:Go Main.
(b) Watch variables:
(i) Select the variable (to be watched) from the lab1.c file, right click and select “Add To Watch Window”. If the variable is ret for instance, the following window will be shown
(ii) To add another variable to the watch select it and then drag and drop it on to the window.

16. LAB: Watch variables (5) Debug and run code:
(c) CCS will automatically add the local variables:

17. LAB: Run / Step (5) Debug and run code:
(d) You can run or step through the code by using the various icons on the toolbar or use the Debug menu:
(e) Stop the processor from running and watch the variable ret:
ret = 7

18. “Code Composer Studio (CCS)” - END -