2 - 1 32-Bit-DSP-MicrocontrollerTMS320F2812 Texas Instruments Incorporated European Customer Training Center University of Applied Sciences Zwickau (FH)

Slides:



Advertisements
Similar presentations
Introduction to Eclipse. Start Eclipse Click and then click Eclipse from the menu: Or open a shell and type eclipse after the prompt.
Advertisements

Getting started with MPLAB Launch MPLAB Set Toolbar as in the next slide by clicking the leftmost icon Open a new Source file by choosing [FILE][NEW] Type.
Introduction to HT-IDE3000 Micro-C development System Department.
Tutorial 2 IDE for ARM 7 board (2). Outline Introduce the Debug mode of uVision4 2.
CS 450 MPX P ROJECT Introduction to Turbo C. W HY USE T URBO C? Many ANSI C compilers are available for free, however they lack certain features that.
Code Composer Department of Electrical and Computer Engineering
Professional Toolkit V2.0 C:\Presentations - SmartCafe_Prof_V2.0 - bsc page 1 Professional Toolkit 2.0.
Slide 1CPU Emulator Tutorial This program is part of the software suite that accompanies the book The Digital Core, by Noam Nisan and Shimon Schocken 2003,
COMPUTER PROGRAMMING I Essential Standard 5.02 Understand Breakpoint, Watch Window, and Try And Catch to Find Errors.
A Guide to Oracle9i1 Introduction To Forms Builder Chapter 5.
The IDE (Integrated Development Environment) provides a DEBUGGER for locating and correcting errors in program logic (logic errors not syntax errors) The.
Chapter 2: The Visual Studio.NET Development Environment Visual Basic.NET Programming: From Problem Analysis to Program Design.
UBI >> Contents Chapter 12 Hardware Multiplier MSP430 Teaching Materials Texas Instruments Incorporated University of Beira Interior (PT) Pedro Dinis Gaspar,
1 Introduction to Programming Environment Using MetroWerks CodeWarrior and Palm Emulator.
Bit-DSP-MicrocontrollerTMS320F2812 Module 2 : Program Development Tools.
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)
Introduction Purpose Objectives Content Learning Time
1 ENG236: ENG236: C++ Programming Environment (2) Rocky K. C. Chang THE HONG KONG POLYTECHNIC UNIVERSITY.
Virtual Instrumentation With LabVIEW. Course Goals Understand the components of a Virtual Instrument Introduce LabVIEW and common LabVIEW functions Create.
P.1ECE 331, Prof. A. Mason Professor Andrew Mason Michigan State University Spring 2013 ECE 331: PC Lab 1: Using HC12 ASM Simulators.
CCS APPS CODE COVERAGE. CCS APPS Code Coverage Definition: –The amount of code within a program that is exercised Uses: –Important for discovering code.
Keith Elder Microsoft MVP
IE 411/511: Visual Programming for Industrial Applications
Debugging Projects Using C++.NET Click with the mouse button to control the flow of the presentation.
Tutorial 111 The Visual Studio.NET Environment The major differences between Visual Basic 6.0 and Visual Basic.NET are the latter’s support for true object-oriented.
ADAM2 Single Remocon MCU IDE User’s Manual S/W Integrated Development Environment - Assembler - Simulator - Code Wizard V1.0 Technical Sales Team, ETA.
Introduction Purpose This training course covers debugging an application on an SH target in the Renesas HEW (High-performance Embedded Workshop) development.
Tutorial 11 Five windows included in the Visual Basic Startup Screen Main Form Toolbox Project Explorer (Project) Properties.
Active-HDL Interfaces Debugging C Code Course 10.
UBI >> Contents Chapter 2 Software Development tools Code Composer Essentials v3: Code Debugging Texas Instruments Incorporated University of Beira Interior.
UBI >> Contents Chapter 2 Software Development tools Code Composer Essentials v3: Creating a project Texas Instruments Incorporated University of Beira.
Visual Basic.NET Comprehensive Concepts and Techniques Chapter 8 Debugging, Creating Executable Files, and Distributing a Windows Application.
Chapter 2 – Introduction to the Visual Studio .NET IDE
1 4-Development Environment Development processor  The processor on which we write and debug our programs Usually a PC Target processor  The processor.
© 2008, Renesas Technology America, Inc., All Rights Reserved 1 Introduction Purpose  This training module provides an overview of debugging features.
CS320n –Visual Programming More LabVIEW Foundations.
Renesas Technology America Inc. 1 M16C Seminars Lab 3 Creating Projects Using HEW4 14 March 2005 M16C Seminars Lab 3 Creating Projects Using HEW4 Last.
Using Simulator With Undertow Suite. Source environment variables For example, envsource has all the environment variables set up. You can change the.
1 Getting Started with C++ Part 1 Windows. 2 Objective You will be able to create, compile, and run a very simple C++ program on Windows, using Microsoft.
Debugging tools in Flash CIS 126. Debugging Flash provides several tools for testing ActionScript in your SWF files. –The Debugger, lets you find errors.
Visual Basic Integrated Development Environment (IDE) 56:150 Information System Design.
CSC 1201 LAB RULES Nouf Aljaffan (C) CSC 1201 Course at KSU.
IE 411/511: Visual Programming for Industrial Applications Lecture Notes #2 Introduction to the Visual Basic Express 2010 Integrated Development Environment.
Debugging Lab Antonio Gómez-Iglesias Texas Advanced Computing Center.
Editing and Debugging Mumps with VistA and the Eclipse IDE Joel L. Ivey, Ph.D. Dept. of Veteran Affairs OI&T, Veterans Health IT Infrastructure & Security.
What's New in Visual Studio 2010 Debugging Brian Peek Senior Consultant, ASPSOFT, Inc. Microsoft MVP - C#
Chapter 2: The Visual Studio.NET Development Environment Visual Basic.NET Programming: From Problem Analysis to Program Design.
Programming and Debugging with the Dragon and JTAG Many thanks to Dr. James Hawthorne for evaluating the Dragon system and providing the core content for.
Workshop Setup The software/hardware used in this workshop are:
Chapter 2: The Visual Studio .NET Development Environment
Programming and Debugging with the Dragon and JTAG
VAB™ for INFINITY Tutorial
Tutorial 2 IDE of Keil for the ARM 7 board(2)
CS4101 Introduction to Embedded Systems Lab 1: MSP430 LaunchPad IDE
Appendix A Barb Ericson Georgia Institute of Technology May 2006
Computer Programming I
PRU-ICSS Programming with CCS
CENG2400 Tutorial 1 Keil IDE CENG2400 tutorial 1 v.7a.
Using Visual Studio with C#
Important terms Black-box testing White-box testing Regression testing
Important terms Black-box testing White-box testing Regression testing
DEMO Presentation Prepared by: Bashir SADEGHI Supervised by: Dr
Debugging with Eclipse
ECE 3567 Microcontroller Lab
CSC235 - Visual Studio Tutorial
Debugging Visual Basic Programs
Software Setup & Validation
Debugging Dwight Deugo
Debugging with Eclipse
Presentation transcript:

Bit-DSP-MicrocontrollerTMS320F2812 Texas Instruments Incorporated European Customer Training Center University of Applied Sciences Zwickau (FH) Module 2 : Program Development Tools

2 - 2 Help CPU Window Memory window Graph window Project Manager:  Source & object files  File dependencies  Compiler, Assembler & Linker build options Status window Full C/C++ & Assembly Debugging:  C & ASM Source  Mixed mode  Disassembly (patch)  Set Break Points  Set probe Points Watch window Productive Editor:  Structure Expansion Menus or Icons Code Composer Studio® IDE

2 - 3 Learning by doing - Step by Step Code Composer Studio ® - The Basics 1. The Start-up - Window 2. Create a F28x - project, based on C language 3. Debug your program 4. Watch your variables 5. Perform a Single Step Debug 6. Use Breakpoints 7. What is a Probe Point for ? 8. Other View Commands

Create a F28x - project Project ==> New give your project a name : “Lab1”, select a target and a suitable location of your hard disk: Note : the project file (“Lab1.pjt) is a plain ASCII-text file and stores all set-ups and options of the project. This is very useful for a version management.

2 - 5 Write a C-Source Code :  File  New  Source File unsigned int k; void main (void) { unsigned int i; while(1) { for (i=0;i<100;i++) k=i*i; } 2. Create a F28x - project (cont.)  File  Save as : “lab1.c”

Create a F28x - project (cont.) Add your file to the project : –  Project  Add files to project –Add: “lab1.c” Compile your source code :  Project  Compile File –active window will be compiled –in the event of syntax errors : modify your source code as needed Add the C-runtime-library to your project :  Project  Build Options  Linker  Library Search Path : c:\ti\c2000\cgtools\lib  Project  Build Options  Linker  Include Libraries : rts2800_ml.lib Add the stack- size of 0x400  Project  Build Options  Linker  Stack Size : 0x400

2 - 7 Linking Linker name.cmd.map.obj.out Memory description Memory description How to place s/w into h/w How to place s/w into h/w Memory description Memory description How to place s/w into h/w How to place s/w into h/w

Create a F28x - project (cont.) Load the binary code into the DSP :  File  Load Program  Debug\Lab1.out –Note: a new binary code can be downloaded automatically into the target. This is done by  Option  Customize  Program Load Options  Load Program after Build. This setup will be stored for permanently. Run the program until label “main”  Debug  Go main

Perform a Single Step Debug Perform a single step trough the program :  Debug  Step Into ( or F8 ) Watch the current PC ( yellow arrow) and the numerical values of i and k in Watch Window while you single step through the code ! There are more debug - commands available, see next slide

Adding a Breakpoint Set a Breakpoint : –Place the Cursor in Lab1.c on line : k = i * i; –Click right mouse and select ‘Toggle Breakpoint’ –the line is marked with a red dot ( = active breakpoint ) Note : most Code Composer Studio Commands are also available through buttons or trough Command -Keys ( see manual, or help ) Reset the Program  Debug  Reset CPU  Debug  Restart Perform a real time run  Debug  Run ( or F5) DSP stops when reaching an active breakpoint repeat ‘Run’ and watch your variables remove the breakpoint ( Toggle again) when you’re done.

Red dot : active Breakpoint Yellow arrow : Current PC Toggle Breakpoint Remove all Breakpoints 6. Adding a Breakpoint (cont. )

Set a Probe Point Causes an update of a particular window at a specific point in your program. When a window is created it is updated at every breakpoint. However, you can change this so the window is updated only when the program reaches the connected Probe Point. When the window is updated, execution of the program is continued. To set a Probe - Point : –Click right mouse on the line ‘k = i*i;’ in the program first.c –select : ‘Toggle Probe Point ‘ ( indicated by a blue dot ) –select  Debug  Probe Points... –In the Probe Point Window click on the line ‘first.c line 13 -> no Connection’ –in the ‘Connect to’ - selector select ‘Watch Window’ –exit this dialog with the ‘Replace’ and ‘OK’ - Button Run the program and verify that the watch window is updated continuously.