Code Composer Studio Getting Started Guide
Code Composer StudioGetting Started GuideLiterature Number: SPRU509May 2001Printed on Recycled Paper
IMPORTANT NOTICETexas Instruments and its subsidiaries (TI) reserve the right to make changes to their productsor to discontinue any product or service without notice, and advise customers to obtain the latestversion of relevant information to verify, before placing orders, that information being relied onis current and complete. All products are sold subject to the terms and conditions of sale suppliedat the time of order acknowledgment, including those pertaining to warranty, patent infringement,and limitation of liability.TI warrants performance of its products to the specifications applicable at the time of sale inaccordance with TI’s standard warranty. Testing and other quality control techniques are utilizedto the extent TI deems necessary to support this warranty. Specific testing of all parameters ofeach device is not necessarily performed, except those mandated by government requirements.Customers are responsible for their applications using TI components.In order to minimize risks associated with the customer’s applications, adequate design andoperating safeguards must be provided by the customer to minimize inherent or proceduralhazards.TI assumes no liability for applications assistance or customer product design. TI does notwarrant or represent that any license, either express or implied, is granted under any patent right,copyright, mask work right, or other intellectual property right of TI covering or relating to anycombination, machine, or process in which such products or services might be or are used. TI’spublication of information regarding any third party’s products or services does not constitute TI’sapproval, license, warranty or endorsement thereof.Reproduction of information in TI data books or data sheets is permissible only if reproductionis without alteration and is accompanied by all associated warranties, conditions, limitations andnotices. Representation or reproduction of this information with alteration voids all warrantiesprovided for an associated TI product or service, is an unfair and deceptive business practice,and TI is not responsible nor liable for any such use.Resale of TI’s products or services with statements different from or beyond the parameters statedby TI for that products or service voids all express and any implied warranties for the associatedTI product or service, is an unfair and deceptive business practice, and TI is not responsible norliable for any such use.Also see: Standard Terms and Conditions of Sale for Semiconductor Products.www.ti.com/sc/docs/stdterms.htmMailing Address:Texas InstrumentsPost Office Box 655303Dallas, Texas 75265Copyright 2001, Texas Instruments Incorporated
PrefaceRead This FirstAbout This ManualTo get started with Code Composer Studio (CCS) IDE, you must go throughthe first two chapters of this book. The remaining chapters contain informationthat can be useful to you, depending on your needs and the tools you are using.To determine whether you can utilize the features in these chapters, pleasereview the online help provided with Code Composer Studio.How to Use This ManualThis document contains the following chapters:ChapterTitleDescription1Getting Started with Code Composer Studio IDEWalks you through the steps ofsetting up the CCS IDE andshows you how to access documentation.2Code Composer Studio ProjectManagement and Editing ToolsInstructions on the basic functionality of the CCS IDE.3Code Composer Studio CodeGeneration ToolsReviews development tools provided with CCS IDE.4Code Composer Studio DebugToolsReviews the available debugtools and the device generationsto which they apply.5Code Composer Studio Optimization ToolsProvides information on profilingcode and the ‘C6000 PBC.6Code Composer Studio RealTime ComponentsOverview of the real-time components featured in CCS IDE.7Code Composer Studio ChipSupport Library OverviewProvides and overview of thefeatures and architecture of CSL.8TMS320 DSP Algorithm StandardReviews the TMS320 DSP Algorithm Standard, and explains theresources available to algorithmwriters.Read This Firstiii
Notational ConventionsNotational ConventionsThis document uses the following conventions. Program listings, program examples, and interactive displays are shownin a special typeface similar to a typewriter’s. Examples use a boldversion of the special typeface for emphasis; interactive displays use abold version of the special typeface to distinguish commands that youenter from items that the system displays (such as prompts, commandoutput, error messages, etc.).Here is a sample program 06.field.field.field.even1, 23, 46, 3Here is an example of a system prompt and a command that you mightenter:C:csr –a /user/ti/simuboard/utilitiesRelated Documentation From Texas InstrumentsFor additional information on your target processor and related support tools,see the online manuals provided with the CCS IDE.To access the online manuals:Help CCS Documentation ManualsRelated DocumentationYou can use the following books to supplement this user’s guide:American National Standard for Information Systems-ProgrammingLanguage C X3.159-1989, American National Standards Institute (ANSIstandard for C)The C Programming Language (second edition), by Brian W. Kernighanand Dennis M. Ritchie, published by Prentice-Hall, Englewood Cliffs, NewJersey, 1988Programming in C, Kochan, Steve G., Hayden Book Companyiv
Related Documentation From Texas InstrumentsTrademarksCode Composer Studio, DSP/BIOS, Probe Point(s), RTDX, TMS320C6000,and TMS320C5000 are trademarks of Texas Instruments Incorporated.Pentium is a registered trademark of Intel Corporation.Windows and Windows NT are registered trademarks of MicrosoftCorporation.All trademarks are the property of their respective owners.To Help Us Improve Our Documentation . . .If you would like to make suggestions or report errors in documentation, pleaseemail us. Be sure to include the following information that is on the title page:the full title of the book, the publication date, and the literature number.Email:support@ti.comRead This Firstv
ContentsContents1Getting Started with Code Composer Studio IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Instructions on setting up the CCS IDE and tools that aid you in using CCS IDE, such as documentation.1.11.21.31.41.51.62Development Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Creating a System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Getting Started with CCS Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Accessing CCS Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Accessing Documentation from the Start Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Update Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8To Check for Tool Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8To Uninstall the Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9To Automatically Check for Tool Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Component Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Opening Component Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Multiple Versions of the CCS IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Code Composer Studio Project Management and Editing Tools . . . . . . . . . . . . . . . . . . . . 2-1Instructions on using the basic functionality of the CCS IDE.2.12.22.32.42.52.62.72.8Creating a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Adding Files to a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Using Source Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Building and Running the Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Selecting a Project Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Change the Active Project Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Add a New Project Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Building Projects From the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Importing an External Makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Limitations and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Reviewing Your Source Code Using the Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13CodeMaestro Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14External Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15vii
Contents3Code Composer Studio Code Generation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Code Composer Studio Code Generation Tools.3.13.23.33.43.53.63.73.84Code Composer Studio Debug Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Reviews the available debug tools and the device generations to which they .14viiiCode Generation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Code Generation Tools and Code Composer Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Build Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Set Project Level Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Set File-Specific Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Compiler Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Interfacing with Code Composer Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Assembly Language Development Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Assembler Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Linker Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Visual Linker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Getting Started with the Visual LInker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10C/C Code Development Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Overview of Applicable Debug Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Introduction to Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Software Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Hardware Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Watch Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Probe Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Simulator Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Emulator Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Advanced Event Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Event Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Event Sequencer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Displaying Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Symbol Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23General Extension Language (GEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Command Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Code Composer Studio Project Management and Editing Tools Instructions on the basic func-tionality of the CCS IDE. 3 Code Composer Studio Code Generation Tools Reviews development tools pro-vided with CCS IDE. 4 Code Composer Studio Debug Tools Reviews the available debug tools and the device generations to which they apply. 5 Code Composer .
2 Code Composer Studio Project Management and Editing Tools Provides instructions on the ba-sic functionality of CCStudio IDE. 3 Code Composer Studio Code Generation Tools Reviews development tools pro-vided with CCStudio IDE. 4 Code Composer Studio Debug Tools Reviews the available debug tools and the device generations to which they apply.
1 MSP-EXP430G2 LaunchPad kit 1 USB cable 1 32.768 kHz crystal 1 Female-Male 6" jumper wire VI. LABORATORY PROCEDURE: A) Code Composer Studio 1. Open Code Composer Studio, located at: Start All Programs Texas Instruments Code Composer Studio 5.4.0 Code Composer Studio 5.4.0. 2. You will be prompted to create a workspace; select a .
About This Manual This manual describes the use of Texas Instruments Code Composer Studio IDE v5.4 (CCS v5.4) with the MSP430 ultralow-powermicrocontrollers. This manual describes only the Windows version of the Code Composer Studio IDE. The setup for Linux is similar and is therefore not described separately. How to Use This Manual Read and follow the instructions in the Get Started .
Sync, Studio 3, Studio 4, Studio 5 (and Studio 5 Lx), Studio 64X, Studio 128X, and Studio 64XTC. . document refers to an Opcode Studio 64XTC, but the next couple of pages are a little detour. Please don’t be confused. Your computer has at least one USB port, which looks like this: . If you have a blue G3, the USB ports are on the back.
3 1 Overview 1.4 What is in the Box Studio 26c and Studio 68c Owner's Manual 1.4 What is in the Box Your Studio-series package contains: Studio 26c or Studio 68c 24-bit, 192 kHz audio interface Quick Start Guide Audio Interface 1M USB-C to C Cable 1M USB-C to A Cable MIDI / S/PDIF breakout cable (Studio 68c only) External power supply (Studio 68c only)
About This Manual This manual describes the use of TI Code Composer Studio IDE v7.x (CCS v7.x) with the MSP430 ultra-low-power microcontrollers. This document applies only for the Windows version of the Code Composer Studio IDE. The Linux version is similar and, therefore, is not described separately. Trademarks
indicates a Studio Project where the files were added directly from the Studio Project to the Studio Session (right-click, add to new/existing Studio Session). The Bluebeam Studio Project and Bluebeam Studio Session must be linked in order to "update" from Session to Project. Using this method will OVERWRITE THE ORIGINAL STUDIO PROJECT FILES.
Alex Rider was woken by the first chime. His eyes flickered open, but for a moment he stayed completely still in his bed, lying on his back with his head resting on the pillow. He heard a bedroom door open and a creak of wood as somebody went downstairs. The bell rang a second time, and he looked at the alarm clock glowing beside him. There was a rattle as someone slid the security chain off .
