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
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
Host:
Mark Wilson
Director, North American
DSP Field Applications
2
Presenter:
John Stevenson
IDE/Debug Technology Manager
Software Development Systems
3
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
Code Composer Studio™
Probe
In
Compile
Asm Opto
SIM
DSK
Plug-Ins
Edit
Asm
Link
Debug
EVM
Profiling
Graphs
Probe
Out
Studio Includes:
DSP/BIOS  Code Generation Tools
Library  DSP/BIOS™: Real-Time Kernel
Real-Time Analysis (RTA)
 Simulator, Plug-ins, RTDX
5
Third
Party
XDS
DSP
Board
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
Step 1: Setting Up Your System
7
System Characteristics

Operating systems

Supported


Not supported


dosrun.bat
Directory structure


Common locations
Multiple installations

Different instruction set architectures (ISAs)



8
Windows 95, ME & UNIX®
Environment variables


Windows™ 98, 98SE, NT (SP4) & 2000
Side-by-side
Merged
Co-existence with CCSv1.2
Connecting a Target (CCS Setup)

Default target



Memory map

GEL startup files

Overwrite old
settings
Initialization order


For multiple
processors
Different shortcuts for different targets

9
Simulator
cc_setup.exe –i”configname.ccs” -startCCS
Workspaces
 Less

sensitive
Will load as much of the workspace as
possible
 Features

may not translate as expected
May see old windows
 Workspaces

Convert workspace first
 Toolbar
10
contain projects
locations
Step 2: Building Your Application
11
Project Manager

Multiple project support


Build active project
Multiple configuration support

Different build options


(e.g., debug, release, etc.)
Libraries
Project
12
Configuration
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

13
Visual Linker
Project File Conversion

File format





DSP/BIOS™-generated files


*.mak => *.pjt
Copy of old file kept
Now text editable
Configurations
Ignore *cfg.h* & *cfg.s*
Libraries

Run-Time Support Library



TMS320™ DSP Algorithm Standard

14
Now in <installdir>/<target>/cgtools/lib
Same file for both C & C++
Now in <installdir>/<target>/xdais/lib
Build Options
 Build

options
Copied exactly
 Search


Directory name
changes
SSL replaced by
CSL

15
paths
Located in DSP/BIOS
directory
CDB File Conversion
 Open

Double-click on the file in the project manager
 Say

the file
yes to converting the file
A backup file is saved
 Save
the file
 HWI support
 C++
16
Linking
 Linker

Specifying the linker

Text or Visual Linker
 Linker

References to object and library files

Recommend to add to project (can now specify
link order)
 Visual



17
command file (*.cmd)
Linker RCP file
Create a backup of the file
Open the file
Save the file
Chip Support Library

What it is?

Peripheral management functions
Replaces DEVLIB (dev6x.lib) and SSL

Integrated with DSP/BIOS™


Naming conventions (eXpressDSP™)



PER_TypeName()
PER_MACRO_NAME

csl_legacy.h will perform the conversion

18
PER_funcName()
PER_varName()
Chip Support Library

File name changes

Header files now begin with “csl_”


Located in DSP/BIOS include directory

Source archive


csl.src => csl6000.src
Hardware abstraction layer

1.2 files are obsolete


19
csl_dma.h
Can use with csl_legacy.h
New macros are more orthogonal
Chip Support Library

CSL_Init()


No longer needs to be called
Argument changes

Address is now void* instead of unsigned int




Support for big and little endian

Big has an “e” at the end

20
CACHE_flush()
CACHE_clean()
CACHE_invalidate()
csl6201e.lib
Version Control

Version control integration



Add files to source control
Check-in/check-out

Get latest version


21
Supports standard SCC API
Show status of files
Access features of SCC
tool

View revision history

Show differences
Building Outside of CCS IDE

External makefile build



Export of CCS project to standard make format


Allows (Unix®) developers to build with other make
utilities
Timake.exe

22
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
Standalone build utility (i.e., build CCS project without
running CCS)
Symbol Browser

Project-like view

Source code navigation
File list

Function definitions

Support team development
 C++


23
Class browser
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


Exclude from build

24
Use a tool other than the standard compiler
File can be active in specific configurations
Step 3: Editing Your Code
25
Editor
 Tool-tip
variable
watching
 Customize
 Selection


margin
Organization
Resize
 Cursor
26
keywords
mode
CodeMaestro™
 Features





27
Suggest word
Complete word
Auto-parameter info
Auto-member info
Case correct
External Editor
 Use
your
favorite editor



28
CodeWright
Emacs
…
Step 4: Debugging
29
Watch Window
 Local
variables tab
 Multiple watch windows
30
RTDX™
 Simulation

Real-time analysis
 Multiprocessor
 RTDX

RTDX settings
Channel viewer


31
Test communications link
Configuration tool


tools
Diagnostics tool


support
List of available channels
Enable/disable channels
Step 5: Optimizing
32
New Profiler Interface
Toolbar
Code Size
Tabs Organize Elements
33
Data in Columns
Function Profiling



34
Profile all functions
Select one or more functions
Handles all branches for you
Range Profiling

Source files




Disassembly

35
Select and drag
Use dialog box
Right click
Visible selection
Start and End Points

Turn the profiler on and off

Ignore sections of code


36
Already optimized
Startup routines
Events

Tracking different events



Detailed chip-specific simulators


37
100+ events on C6211 simulator
1 event on C5510 simulator
Have the most events
1 event at a time
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
Step 6: Support
39
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

40
Select: Email Technical Support
Update Advisor
 New




method for obtaining
Updates
Patches
Fixes
New utilities
 Requires

online registration
Service code
 Accessing

Periodic check
 Browser
41
requirements
Update Advisor
42
Related Technical References
including...

43
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