Texas Instruments MSP-FET430 manual Overview, Using Kickstart

Page 20

Development Flow

2.1 Overview

Applications are developed in assembler and/or C using the Workbench, and they are debugged using C-SPY. C-SPY is seamlessly integrated into the Workbench. However, it is more convenient to make the distinction between the code development environment (Workbench) and the debugger (C-SPY). C- SPY can be configured to operate with the FET (i.e., an actual MSP430 device), or with a software simulation of the device. Kickstart is used to refer to the Workbench and C-SPY collectively. The Kickstart software tools are a product of IAR.

Documentation for the MSP430 family and Kickstart is extensive. The CD-ROM supplied with this tool contains a large amount of documentation describing the MSP430. The MSP430 home page (www.ti.com/sc/msp430) is another source of MSP430 information. The components of Kickstart (workbench/debugger, assembler, compiler, linker) are fully documented in <Installation Root>\Embedded Workbench x.x\common\doc and <Installation Root>\Embedded Workbench\430\doc. .htm files located throughout the Kickstart directory tree contain the most up to date information and supplement the .pdf files. In addition, Kickstart documentation is available on-line via HELP.

Read Me Firsts from IAR and TI, and this document, can be accessed using:

START->PROGRAMS->IAR SYSTEMS->IAR EMBEDDED WORKBENCH

KICKSTART FOR MSP430 V3

Tool

User’s Guide

Most Up To Date

 

 

Information

Workbench/C-SPY

EW430_UsersGuide.pdf

readme.htm, ew430.htm,

 

 

cs430.htm, cs430f.htm,

Assembler

EW430_AssemblerReference.pdf

a430.htm, a430_msg.htm

Compiler

EW430_CompilerReference.pdf

icc430.htm, icc430_msg.htm

C library

 

CLibrary.htm

Linker and Librarian

xlink.pdf

xlink.htm, xman.htm, xar.htm

2.2 Using Kickstart

The Kickstart development environment is function-limited. The following restrictions are in place:

The C compiler will not generate an assembly code list file.

The linker will link a maximum of 4K bytes of code originating from C source (but an unlimited amount of code originating from assembler source).

2-2

Image 20
Contents Users Guide 2004Important Notice Page July About This Manual How to Use This ManualRead This First Information About Cautions and Warnings Related Documentation From Texas InstrumentsIf You Need Assistance FCC WarningPage Contents Frequently Asked Questions Figures TablesPage Get Started Now TopicKit Contents, MSP-FET430X110 Hardware Installation, MSP-FET430X110 Kit Contents, MSP-FET430UIFSoftware Installation Hardware Installation, USB-IF, MSP-FET430UIF Flashing the LEDGet Started Now Important MSP430 Documents on the CD-ROM and WEB Development Flow Using Kickstart OverviewProject Settings OUTPUT-OUTPUT FILE-EXECUTABLEFactory Settings Creating a Project from Scratch Using an Existing IAR V1.x/V2.x Project Stack Management within the .xcl FilesHow to Generate Texas Instrument .TXT and other format Files Overview of Example ProgramsDevelopment Flow Breakpoint Types Using C-SPYUsing Breakpoints Using Single Step Using Watch Windows Page Design Considerations for In-Circuit Programming Bootstrap Loader External PowerDesign Considerations for In-Circuit Programming Device Signals PRGS430Design 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 Debugging C-SPY OPTIONS-FET DEBUGGER-CONNECTIONSFrequently 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 Figure B-1. MSP-FET430X110, Schematic HardwareFigure 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-GIE on/off EMULATOR-FORCE Single SteppingPin 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 Segment Control Translating Asm430 Assembler Directives to A430 DirectivesIntroduction Character stringsSection Control Directives Description Asm430 Directive TI A430 Directive IARConstant Initialization Directives Listing Control DirectivesConditional-Assembly Directives File Reference DirectivesSymbol Control Directives ReptcPreprocessor Directives Macro DirectivesMiscellaneous Directives Additional A430 Directives IAR Asm430 directive A430 directiveLstpag + #if, #else, #elif Page MSP-FET430UIF Installation Guide Hardware Installation Figure F-1. WinXP Hardware RecognitionFigure F-3. WinXP Driver Location Selection Folder Figure F-4. WinXP Driver Installation Figure F-5. Device Manager