APPENDIX A. CODE COMPOSER STUDIO (CCS) v5: A BRIEF TUTORIAL FOR THE DSK6713

Similar documents
As CCS starts up, a splash screen similar to one shown below will appear.

As CCS starts up, a splash screen similar to one shown below will appear.

Code Composer Studio Operation Manual

Digital Signal Processing and Applications with the TMS320C6713 and TMS320C6416 DSK second edition

Experiment 6 Finite Impulse Response Digital Filter (FIR).

SMT107 User Manual User Manual (QCF42); Version 3.0, 8/11/00; Sundance Multiprocessor Technology Ltd. 1999

F28069 ControlCard Lab1

QUICKSTART CODE COMPOSER STUDIO Stellaris Development and Evaluation Kits for Code Composer Studio

You have a PC with a USB interface, running Microsoft Windows XP (SP2 or greater) or Vista You have the Workshop Installation Software Flash Drive

F28335 ControlCard Lab1

DOMAIN TECHNOLOGIES. Getting Started Guide Version 1.1. BoxView IDE. Integrated Development Environment

TMS. series SIGNUM SYSTEMS CORPORATION. JTAGjet Driver for Code Composer Studio 2.x/3.0. Installation Instructions

TMS320C5502 ezdsp Quick Start Guide

ECE 487 LAB 1 ÇANKAYA UNIVERSITY Overview of DSP Board

PSIM Tutorial. How to Use SimCoder with TI F28335 Target Powersim Inc.

XDS200 ISO Operating Guide

XDS560V2 Installation Guide

Section 2: Getting Started with a FPU Demo Project using EK-LM4F232

BHFlashBurn v2.0. User Guide. BHFlashBurn-UG-02 April 2008

Code Composer Studio Development Tools v3.3. Getting Started Guide

Lab 0 Introduction to the MSP430F5529 Launchpad-based Lab Board and Code Composer Studio

TMS320C5535 ezdsp Quick Start Guide

Quick-Start Guide. BNS Solutions. QSK62P Plus

file://c:\documents and Settings\degrysep\Local Settings\Temp\~hh607E.htm

ECE QNX Real-time Lab

TDS510USB-C2K Emulator Installation Guide

TUTORIAL Auto Code Generation for F2833X Target

PSIM Tutorial. How to Use SCI for Real-Time Monitoring in F2833x Target. February Powersim Inc.

How to: Flash the DC/DC LED Lighting Kit s F28035 controlcard so that it works with the GUI

CST8152 Compilers Creating a C Language Console Project with Microsoft Visual Studio.Net 2003

CST8152 Compilers Creating a C Language Console Project with Microsoft Visual Studio.Net 2005

Texas Instruments Code Composer and ez-dsp Setup Notes

TUTORIAL Auto Code Generation for F2803X Target

System Ace Tutorial 03/11/2008

Hello World on the ATLYS Board. Building the Hardware

TI mmwave Training. xwr16xx mmwave Demo

Configuring Code Composer Studio for OMAP Debugging

CST8152 Compilers Creating a C Language Console Project with Microsoft Visual Studio.Net 2010

Lab 1. OMAP5912 Starter Kit (OSK5912)

TriCore Free Entry Tool Chain. AURIX family and AUDO Future, AUDO MAX

Disassemble the machine code present in any memory region. Single step through each assembly language instruction in the Nios II application.

Using Code Composer Studio IDE with MSP432

MEM MEM Control Applications of DSP. Lab 2. Project Creating & GPIO DSP28355 & CCSv5

user guide January 2006 CSR Cambridge Science Park Milton Road Cambridge CB4 0WH United Kingdom Registered in England

QNX Software Development Platform 6.6. Quickstart Guide

Debugging in AVR32 Studio

Olimex Field Update Kit

Building an Embedded Processor System on Xilinx NEXYS3 FPGA and Profiling an Application: A Tutorial

R8C/Tiny. StarterKit Plus SKP8CMINI-15, SKP8CMINI-17. Clock Stop Detect

Debugging Nios II Systems with the SignalTap II Logic Analyzer

Code Composer Studio IDE Getting Started Guide. User's Guide

Composer Help. Import and Export

Spartan-6 LX9 MicroBoard Embedded Tutorial. Tutorial 1 Creating an AXI-based Embedded System

Migration from HEW to e 2 studio Development Tools > IDEs

TI mmwave Training. mmwave Demo

mce100+ getting started guide Install mce100+ The disc will run and display the below screen: Choose Install mce to continue

To install the Texas Instruments CCS Compiler, follow these steps: 1. Go to the TI Wiki page (

Section Objective: Acquaint with specifications of Launchpad Acquaint with location of switches, LEDs, power-on switch, powering the board.

Bridge Cable User s Guide

Getting Started with Energia for MSP432 LaunchPad

April 4, 2001: Debugging Your C24x DSP Design Using Code Composer Studio Real-Time Monitor

EKK-LM3S811 QUICKSTART

TMS320C6000 Code Composer Studio Getting Started Guide

1) Installing Bluetooth software for Windows (A) Place installation CD into PC and setup should launch automatically.

UNic Eclipse Mini Tutorial (Updated 06/09/2012) Prepared by Harald Gjermundrod

IAR EWARM Quick Start for. Holtek s HT32 Series Microcontrollers

MEM Microprocessor-Based Control Systems. Lab 4. Modeling and Simple Feedback Control DSP28355, CCSv Introduction. 2.

TUTORIAL Auto Code Generation for F2806X Target

Create and Debug a CCSv5.5 Project for DSK6713- or DUETT-Board1

CodeWarrior Development Studio for StarCore DSP SC3900FP Architectures Quick Start for the Windows Edition

Code Composer Studio Getting Started Guide

AURIX family and AUDO Future, AUDO MAX

Resource 2 Embedded computer and development environment

ECE4703 Real-Time DSP Orientation Lab

Installation and Quick Start of isystem s winidea Open in DAVE. Tutorial Version 1.0, May, 2014

Opening Microsoft Visual Studio. On Microsoft Windows Vista and XP to open the visual studio do the following:

CodeWarrior Development Studio for Power Architecture Processors Version 10.x Quick Start

S32R274RRUEVB AND S32R372RRSEVB SOFTWARE INTEGRATION GUIDE (SWIG)

ECE 5655/4655 Laboratory Problems

Getting Started Guide: TMS-FET470A256 IAR Kickstart Development Kit

3 TUTORIAL. In This Chapter. Figure 1-0. Table 1-0. Listing 1-0.

2 TUTORIAL. Overview. VisualDSP Getting Started Guide 2-1 for SHARC DSPs

Dual Tone Multi-Frequency (DTMF) Generation with TI-DSP TMS320C6713 Processor

ZCRMZNICE01ZEMG Crimzon In-Circuit Emulator

QSPI Flash Memory Bootloading In Standard SPI Mode with KC705 Platform

Quick Start Installation Guide

for StarCore DSP Architectures Quick Start for the Windows Edition

ML410 VxWorks BSP and System Image Creation for the BSB DDR2 Design Using EDK 8.2i SP1. April

Code Composer TM. Quick Start Guide

Lab 4- Introduction to C-based Embedded Design Using Code Composer Studio, and the TI 6713 DSK

Spartan -6 LX9 MicroBoard Web Connectivity On Ramp Tutorial

Apex-ICE Universal Emulator Hardware and Software Installation Guide

System Framework Overview Guide and Instructions on How to Use the Template Projects

NetBeans Tutorial. For Introduction to Java Programming By Y. Daniel Liang. This tutorial applies to NetBeans 6, 7, or a higher version.

WRITING CONSOLE APPLICATIONS IN C

Blackhawk USB560v2 System Trace Emulator. Installation Guide

Figure 1. Simplicity Studio

Implementation Techniques for DSP

Using Virtual EEPROM and Flash API for Renesas MCUs RX600 Series

Setting up the PC ready for BESA 11

Transcription:

APPENDIX A. CODE COMPOSER STUDIO (CCS) v5: A BRIEF TUTORIAL FOR THE DSK6713 A.1 Introduction Code Composer Studio (CCS) is Texas Instruments integrated development environment (IDE) for developing routines on a wide variety of their DSPs. In CCS, the editing, code generation, and debugging tools are all integrated into one unified environment. You can select the target DSP, adjust the optimization parameters, and set the user preferences as you desire. An application is developed based on the concept of a project, where the information in the project determines what source code is used and how it will be processed. Learning to use Code Composer Studio is a necessary step in bridging the gap between DSP theory and real-time DSP. We recommend that you devote some time to getting to know CCS. You can practice on your own or you can use this appendix to help get you started. A.2 Starting Code Composer Studio This tutorial assumes that CCS is properly installed on a Windows XP, Windows Vista, or Windows 7-based computer. As of this printing, the latest version of CCS (version 5.1) supports all of these operating systems, and is available for the TMS320C6713 DSP Development Kit (DSK) As long as you are running the CCS version 5.1, this tutorial will sequence you through the basic steps involved in creating, compiling, loading, and running (executing) a project. If CCS is not installed, please install it now. The following discussion assumes you are using a TMS320C6713 DSK. When you are ready... 1. Verify that the development board DIP switches (SW3) are in the OFF position. If you look closely, the switch positions are labeled. 2. Power up the TMS320C6713 DSK by plugging in its power supply to an energized AC outlet, and connecting the power supply cable to the development board. The +5V LED should now be energized on the DSK. 3. Start up and allow the computer that you installed CCS on to fully finish its boot-up process. Plug the USB cable into the development board and then plug the other end of the cable into your PC. Be sure that you allow the computer to finish loading the device drivers before you move to the next step. 4. Launch CCS by double clicking on its icon. After a standard CCS install, this icon will be located on your computer s desktop. You are looking for the icon shown below. As CCS starts up, a splash screen similar to one shown below will appear.

You will then be prompted to select a workspace directory. This directory is where CCS will store your projects. A suggested location would be a directory in documents folder of your user account). If prompted about a software license, select the FREE LICENSE option for the time being. This license supports the XDS100 JTAG emulation used on the OMAP-L138 board. Click Finish.

The CCS integrated development environment (IDE) will then finish loading and a welcome page similar to the one shown below will appear as shown below. A.3 Needed Files 1. Use Windows Explorer to verify that the directory Support exists at C:\EEM478\DSK6713 APPS\Support, where C:\EEM478 may be some other name or disk location that you specified when you installed the provided example projects. If this directory structure does not exist, you either need to create it or install the provided software. There should be several files in the Support directory. If these files are not already in the directory, they can be copied from the Support directory of the provided files. 3. Some form of organization is required for your projects and the dozens of files you will eventually create. CCS uses the concept of a workspace to organize groups of projects. A single workspace can be used to manage any number of projects. 4. If you copied the files from a CD-ROM, the files most likely have a read-only attribute. Removing this attribute may prove helpful later in this process. A.4 Creating a New Project 1. We will now create a project and its associated directory by adding a new project the workspace. 2. To create a new CCS project, click on the File pull down menu, then select New and CCS Project. A dialog box similar to the one shown below will open. By default, the project will be created in the workspace location that was selected when you started CCS. a. In the Project Name: box, type in myfirstproject. b. In the Family box, select C6000. c. In the Variant box, the type of processor target is selected. For the OMAPL138, select Generic C67xx Device. d. Under Project templates and examples, select Empty Project.

3. Click Advanced settings. a. At the Linker command file box, browse to the C:\EEM478\DSK6713 APPS\Support\ directory and select the C6713dsk.cmd file. Leave the other options at their default values.

b. The process you ve just gone through will be the same for every CCS project you create for the TMS320C6713. Click Finish. 4. CCS will now show your project in the Project Explorer window as shown below. Note that the linker command file you selected is displayed in the project tree. You may need to click on the small triangle symbol to expand the project view. A.5 Adding Files to a Project 1. CCS will have created a project directory in the workspace and added files to it. The project information is stored in a number of XML files, such as.ccsproject. We strongly recommend that you not edit or otherwise modify these files. To add files to your project, right-click myfirstproject in the Project Explorer window and select Add files.

2. While adding files to your project with Add Files dialog, navigate to the directory C:\EEM478\DSK6713 APPS\sine8_LED and select files Sine8_LED.c and gain.gel. Click Open. In the dialog that pops up, ensure that Copy files is selected, and click OK. Second, we will add kit driver support files to the project. Follow the same routines above and add four support files in folder C:\EEM478\DSK6713 APPS\Support\. (Ensure that Copy files is selected) c6713dskinit.c c6713dskinit.h Vectors_poll.asm

A.6 Building the Project 1. Before building the project, some compiler and linker settings have to be modified to ensure that the code has access various peripherals and memory available on the DSK board. a. First, open the properties window of the project by right clicking on its name in the left pane of CCS. b. Go Build C6000 Compiler Include Options and add following directories to the Include Search Path section: - Support Include folder : c:\eem478\dsk6713 APPS\Support - CSL Include folder : c:\ti\c6xcsl\include - BSL Include folder : c:\ti\dsk6713 BSL\c6000\dsk6713\include

II. Go Build C6000 Compiler Advanced Options Predefined Symbols, in the Predefine-NAME section, add text: CHIP_6713 III. Go Build C6000 Compiler Advanced Options Run-Time Model Options, and set Data access model parameter as far.

IV. Go Build C6000 Linker Basic Options, and set C System Stack size as 0x200. V. Go Build C6000 Linker File Search Options, and add following.lib files to Include library file or command file as input section: - CSL library file: C:\ti\C6xCSL\lib_3x\csl6713.lib - BSL library file: C:\ti\DSK6713 BSL\c6000\dsk6713\lib\dsk6713bsl.lib VI. Go Build C600 section: ing folders to Library search path - CSL lib folder: C:\ti\C6xCSL\lib_3x - BSL lib folder: C:\ti\DSK6713 BSL\c6000\dsk6713\lib

Note: After those settings above, you should be able to build your project without any errors. If a problem occurs, you most probably have done some of the steps above incorrectly. Check your setting steps and try again. 2. To build the project, select Project from the main menu and click Build Project. CCS will now compile and link the project files to produce an executable file. If all is well, the console window will show Build Finished. Note that CCS has many menu buttons that have the same function as the menu commands. Getting to know where the frequently used ones are can be very useful and speed up development. A.7 Loading the Program onto the Target Hardware 1. Now that the project is built, you need to load the project onto the target hardware, and then run it. The hardware interface is controlled by a target configuration file which we will add to the project. As before, right-click the project to Add Files and navigate to the C:\ti\DSK6713 BSL\cc\gel directory. Select the DSK6713TargetConfiguration.ccxml and dsk6713.gel files, and click Open. In the dialog that pops up, ensure that Copy files is selected, and click OK.

2. In the Project Explorer window, double-click the DSK6713TargetConfiguration.ccxml file to open it. Select the Advanced tab, and then click the TMS320C671X entry. Under CPU Properties (in the right column), note that the initialization script field has already been set to dsk6713.gel. This is a script file that controls the initialization of the target hardware. Close the DSK6713TargetConfiguration.ccxml file. 3. In the Project Explorer window, click on your project. Then, from the CCS menu, select Run and click Debug. The target hardware is initialized; the configuration script in dsk6713.gel is run (as shown in the Console window), the program is loaded into the DSP s memory, and the DSP halted at the beginning of the main function. A.8 Running the Program on the Target Hardware 1. Now that the project is loaded onto the target hardware, select Run from the main menu and click Resume. Assuming you have connected a line-level audio source and speakers/headphones to the board, you should hear audio being fed through the hardware. You can suspend and resume the program as desired. Note that the key items from the target menu are available as buttons in the debug window. 2. To terminate the debug session, select Run from the main menu and click Terminate. 3. You may modify and rebuild your code even while the hardware is running. You must rebuild and reload a program after any changes are made in the code if you wish to see the results of these changes! A.9 Getting to Know CCS 1. As we mentioned at the start of this appendix, we highly recommend that you invest some time to become familiar with the CCS interface and its operation. It is the cornerstone of real-time DSP using the TMS320C6713 DSK.