Texas Instruments MSP-FET430 manual Program Development Assembler, C-Compiler, Linker

Page 41

Frequently Asked Questions

low power mode is restored (using GO). This behavior appears to happen on all devices except the MSP430F12x.

12)The following ZIF sockets are used in the FET tools and Target Socket modules:

20-pin device (DW package): Wells-CTI 652 D020

28-pin device (DW package): Wells-CTI 652 D028

64-pin device (PM package): Yamaichi IC51-0644-807

80-pin device (PN package): Yamaichi IC201-0804-014

100-pin device (PZ package): Yamaichi IC201-1004-008

Wells-CTI: http://www.wellscti.com/

Yamaichi: http://www.yamaichi.us/

A.2 Program Development (Assembler, C-Compiler, Linker)

1)The files supplied in the 430\tutor folder work only with the simulator. Do not use the files with the FET. Refer to FAQ: Program Development #11)

2)A common MSP430 “mistake” is to fail to disable the Watchdog mechanism; the Watchdog is enabled by default, and it will reset the device if not disabled or properly handled by your application. Refer to FAQ, Program Development #14).

3)When adding source files to a project, do not add files that are #include’ed by source files that have already been added to the project (say, an .h file within a .c or .s43 file). These files will be added to the project file hierarchy automatically.

4)In assembler, enclosing a string in double-quotes (“string”) automatically appends a zero byte to the string (as an “End Of String” marker). Enclosing a string in single-quotes (‘string’) does not.

5)When using the compiler or the assembler, if the last character of a source line is backslash (\), the subsequent carriage return/line feed is ignored (i.e., it is as if the current line and the next line are a single line). When used in this way, the backslash character is a “Line Continuation” character.

6)The linker output format must be “Debug info” or “Debug info with terminal I/O” (.d43) for use with C-SPY. C-SPY will not start otherwise, and a error message will be output. C-SPY cannot input a

.TXT file.

7)Position Independent code can be generated (using PROJECT-

>OPTIONS->GENERAL OPTIONS->TARGET->POSITION- INDEPENDENT CODE).

8)Within the C libraries, GIE (Global Interrupt Enable) is disabled before (and restored after) the hardware multiplier is used. Contact TI if you wish the source code for these libraries so that this behavior can be disabled.

A-3

Image 41
Contents 2004 Users GuideImportant Notice Page July About This Manual How to Use This ManualRead This First 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 Hardware Installation, MSP-FET430X110 Kit Contents, MSP-FET430UIFSoftware Installation 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 Breakpoint Types Using C-SPYUsing Breakpoints 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 Translating Asm430 Assembler Directives to A430 Directives Segment ControlIntroduction Character stringsDescription Asm430 Directive TI A430 Directive IAR Section Control DirectivesListing Control Directives Constant Initialization DirectivesFile Reference Directives Conditional-Assembly DirectivesReptc Symbol Control DirectivesPreprocessor Directives Macro DirectivesMiscellaneous 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