Texas Instruments MSP-FET430 manual Development Flow

Page 19

Chapter 2

Development Flow

This chapter discusses how to use Kickstart to develop your application software, and how to use C-SPY to debug it.

Topic

 

Page

2.1

Overview

2-2

2.2

Using Kickstart

2-2

2.2.1

Project Settings

2-3

2.2.2

Creating a Project from Scratch

2-5

2.2.3

Using an Existing IAR V1.x/V2.x Project

2-6

2.2.4

Stack Management within the .xcl Files

2-6

2.2.5

How to Generate Texas Instrument .TXT (and other format)

2-7

 

Files

 

2.2.6

Overview of Example Programs

2-7

2.3

Using C-SPY

2-9

2.3.1

Breakpoint Types

2-9

2.3.2

Using Breakpoints

2-9

2.3.3

Using Single Step

2-10

2.3.4

Using Watch Windows

2-11

2-1

Image 19
Contents 2004 Users GuideImportant Notice Page July Read This First How to Use This ManualAbout This Manual Related Documentation From Texas Instruments Information About Cautions and WarningsFCC Warning If You Need AssistancePage Contents Frequently Asked Questions Tables FiguresPage Topic Get Started NowKit Contents, MSP-FET430X110 Software Installation Kit Contents, MSP-FET430UIFHardware Installation, MSP-FET430X110 Flashing the LED Hardware Installation, USB-IF, MSP-FET430UIFGet Started Now Important MSP430 Documents on the CD-ROM and WEB Development Flow Overview Using KickstartOUTPUT-OUTPUT FILE-EXECUTABLE Project SettingsFactory Settings Creating a Project from Scratch Stack Management within the .xcl Files Using an Existing IAR V1.x/V2.x ProjectOverview of Example Programs How to Generate Texas Instrument .TXT and other format FilesDevelopment Flow Using Breakpoints Using C-SPYBreakpoint Types Using Single Step Using Watch Windows Page Design Considerations for In-Circuit Programming External Power Bootstrap LoaderDesign Considerations for In-Circuit Programming PRGS430 Device SignalsDesign Considerations for In-Circuit Programming Signal connections for MSP-FET430X110 Design Considerations for In-Circuit Programming Jtag Signal Connections Frequently Asked Questions Hardware Program Development Assembler, C-Compiler, Linker Should Done or Not Return Omit OPTIONS-FET DEBUGGER-CONNECTIONS Debugging C-SPYFrequently Asked Questions Figure A-1. Modification to FET Interface module Frequently Asked Questions Frequently Asked Questions Frequently Asked Questions Frequently Asked Questions Frequently Asked Questions Hardware Figure B-1. MSP-FET430X110, SchematicFigure B-1. MSP-FET430X110, Schematic Figure B-2. MSP-FET430X110, PCB Pictorials Figure B-3. MSP-FET430IF FET Interface module, Schematic Figure B-4. MSP-FET430IF FET Interface module, PCB Pictorial Figure B-5. MSP-TS430DW28 Target Socket module, Schematic LED connected to P1.0 Hardware Jumper J7 Jumper J6Open to measure current Hardware Jumper J6 Open to disconnect LED History of changes to MSP-TS430PM64 Target Socket module Figure B-11. MSP-TSPN80 Target Socket module, Schematic Figure B-12. MSP-TSPN80 Target Socket module, PCB Pictorials Figure B-13. MSP-TSPZ100 Target Socket module, Schematic Jumper J6 Figure B-15. MSP-FET430UIF USB Interface schematics Hardware Hardware Hardware Hardware Page FET Specific Menus Emulator EMULATOR-POWER on Reset EMULATOR-FORCE Single Stepping EMULATOR-GIE on/offPin MSP430F44x and MSP430F43x Device Emulation Table D-1. F4xx/80-pin Signal Mapping P1.5/TACLK/ACLK P1.4/TBCLK/SMCLK P1.3/TBOUTH/SVSOUT Page TI to IAR 2.x/3.x Assembler Migration Character strings Segment ControlTranslating Asm430 Assembler Directives to A430 Directives IntroductionDescription Asm430 Directive TI A430 Directive IAR Section Control DirectivesListing Control Directives Constant Initialization DirectivesFile Reference Directives Conditional-Assembly DirectivesReptc Symbol Control DirectivesMiscellaneous Directives Macro DirectivesPreprocessor Directives Asm430 directive A430 directive Additional A430 Directives IARLstpag + #if, #else, #elif Page MSP-FET430UIF Installation Guide Figure F-1. WinXP Hardware Recognition Hardware InstallationFigure F-3. WinXP Driver Location Selection Folder Figure F-4. WinXP Driver Installation Figure F-5. Device Manager