1. Getting Started with Code Composer Studio™ IDE v2.0 Presentation begins live from Dallas July 11, 7:00 a.m. and 11:00 a.m. Central Daylight Time (CDT) Code Composer Studio, TMS320, CodeMaestro, C6000, eXpressDSP, DSP/BIOS and RTDX are trademarks of Texas Instruments Incorporated

2. Getting Started with Code Composer Studio ™ IDE v2.0 Code Composer Studio, TMS320, CodeMaestro, C6000, eXpressDSP, DSP/BIOS and RTDX are trademarks of Texas Instruments Incorporated 1

3. Host: Mark Wilson Director, North American DSP Field Applications 2

4. Presenter: John Stevenson IDE/Debug Technology Manager Software Development Systems 3

5. Objectives  Learn how to migrate development to Code Composer Studio™ v2.0  Tips for using the new features of Code Composer Studio v2.0 4

6. Plug-Ins LinkAsm Compile Asm Opto Edit DSP Board Debug SIM Probe In Probe Out GraphsProfiling DSK EVM Third Party XDS Studio Includes:  Code Generation Tools  DSP/BIOS™: Real-Time Kernel Real-Time Analysis (RTA) DSP/BIOS Library  Simulator, Plug-ins,  RTDX Code Composer Studio™ 5

7. Migration Steps  Step 1: Setting up your system  Step 2: Building your application  Step 3: Editing your code  Step 4: Debugging  Step 5: Optimizing  Step 6: Support 6

8. Step 1: Setting Up Your System 7

9. System Characteristics  Operating systems Supported Windows™ 98, 98SE, NT (SP4) & 2000 Not supported Windows 95, ME & UNIX®  Environment variables dosrun.bat  Directory structure Common locations  Multiple installations Different instruction set architectures (ISAs) Side-by-side Merged Co-existence with CCSv1.2 8

10. Connecting a Target (CCS Setup)  Default target Simulator  Memory map GEL startup files Overwrite old settings  Initialization order For multiple processors  Different shortcuts for different targets cc_setup.exe –i”configname.ccs” -startCCS 9

11. Workspaces  Less sensitive Will load as much of the workspace as possible  Features may not translate as expected May see old windows  Workspaces contain projects Convert workspace first  Toolbar locations 10

12. Step 2: Building Your Application 11

13. Project Manager  Multiple project support Build active project  Multiple configuration support Different build options (e.g., debug, release, etc.)  Libraries ConfigurationProject 12

14. Converting Projects  Project file File format Build options Include search path Run-time libraries Linker cmd file  DSP/BIOS CDB file  Chip Support Library (CSL)  Linking Visual Linker 13

15. Project File Conversion  File format *.mak => *.pjt Copy of old file kept Now text editable Configurations  DSP/BIOS™-generated files Ignore *cfg.h* & *cfg.s*  Libraries Run-Time Support Library Now in / /cgtools/lib Same file for both C & C++ TMS320™ DSP Algorithm Standard Now in / /xdais/lib 14

16. Build Options  Build options Copied exactly  Search paths Directory name changes SSL replaced by CSL Located in DSP/BIOS directory 15

17. CDB File Conversion  Open the file Double-click on the file in the project manager  Say yes to converting the file A backup file is saved  Save the file  HWI support  C++ 16

18. Linking  Linker Specifying the linker Text or Visual Linker  Linker command file (*.cmd) References to object and library files Recommend to add to project (can now specify link order)  Visual Linker RCP file Create a backup of the file Open the file Save the file 17

19. Chip Support Library  What it is? Peripheral management functions Replaces DEVLIB (dev6x.lib) and SSL Integrated with DSP/BIOS™  Naming conventions (eXpressDSP™) PER_funcName() PER_varName() PER_TypeName() PER_MACRO_NAME csl_legacy.h will perform the conversion 18

20. Chip Support Library  File name changes Header files now begin with “csl_” csl_dma.h Located in DSP/BIOS include directory Source archive csl.src => csl6000.src  Hardware abstraction layer 1.2 files are obsolete Can use with csl_legacy.h New macros are more orthogonal 19

21. Chip Support Library  CSL_Init() No longer needs to be called  Argument changes Address is now void* instead of unsigned int CACHE_flush() CACHE_clean() CACHE_invalidate()  Support for big and little endian Big has an “e” at the end csl6201e.lib 20

22. Version Control  Version control integration Supports standard SCC API Show status of files Add files to source control Check-in/check-out Get latest version  Access features of SCC tool View revision history Show differences 21

23. Building Outside of CCS IDE  External makefile build User can build custom makefiles within CCS CCS can launch build, load the result, and scan the makefile to populate the project tree with a list of files  Export of CCS project to standard make format Allows (Unix®) developers to build with other make utilities  Timake.exe Standalone build utility (i.e., build CCS project without running CCS) 22

24. Symbol Browser  Project-like view Source code navigation File list Function definitions  Support team development  C++ Class browser 23

25. Running Other Applications  Running applications before/after building Initial & final build steps for a project Pre- & post-build steps for source files  Custom build steps Alternative build Use a tool other than the standard compiler Exclude from build File can be active in specific configurations 24

26. Step 3: Editing Your Code 25

27. Editor  Tool-tip variable watching  Customize keywords  Selection margin Organization Resize  Cursor mode 26

28. CodeMaestro™  Features Suggest word Complete word Auto-parameter info Auto-member info Case correct 27

29. External Editor  Use your favorite editor CodeWright Emacs … 28

30. Step 4: Debugging 29

31. Watch Window  Local variables tab  Multiple watch windows 30

32. RTDX™  Simulation Real-time analysis  Multiprocessor support  RTDX tools Diagnostics tool Test communications link Configuration tool RTDX settings Channel viewer List of available channels Enable/disable channels 31

33. Step 5: Optimizing 32

34. New Profiler Interface Data in ColumnsCode Size Tabs Organize Elements Toolbar 33

35. Function Profiling  Profile all functions  Select one or more functions  Handles all branches for you 34

36. Range Profiling  Source files Select and drag Use dialog box Right click  Disassembly Visible selection 35

37. Start and End Points  Turn the profiler on and off Ignore sections of code Already optimized Startup routines 36

38. Events  Tracking different events 100+ events on C6211 simulator 1 event on C5510 simulator  Detailed chip-specific simulators Have the most events  1 event at a time 37

39. Profile-Based Compiler  Integrated in CCS environment No icon on desktop Uses CCS Profiler Generates a project configuration  Runs on hardware or simulator  C6000™ DSP only 38

40. Step 6: Support 39

41. Contacting Support  Update Advisor support questionnaire Access from within CCS Gathers CCS configuration info  DSP Developers’ Village: www.dspvillage.ti.com Search for info in DSP KnowledgeBase Email tech support from DSP KnowledgeBase Select: Email Technical SupportEmail Technical Support 40

42. Update Advisor  New method for obtaining Updates Patches Fixes New utilities  Requires online registration Service code  Accessing Periodic check  Browser requirements 41

43. Update Advisor 42

44. Related Technical References including...  Application reports: “Migrating CCS 1.20/CCS 1.0 Projects to CCS v2” Links to additional application reports  CCSv2 Getting Started Guide  Code Composer Studio multimedia tutorial files Accessible from help Also available online 43