Texas Instruments MSP-FET430 manual Project Settings, Output-Output File-Executable

Page 21

Development Flow

The simulator will input a maximum of 4K bytes of code.

A “Full” (i.e., unrestricted) version of the software tools can be purchased from IAR. A mid-featured tool set – called “Baseline”, with a 12K byte C code size limitation and basic floating-point operations – is also available from IAR. Consult the IAR web site (www.iar.se) for more information.

2.2.1Project Settings

The settings required to configure the Workbench and C-SPY are numerous and detailed. Please read and thoroughly understand the documentation supplied by IAR when dealing with project settings. Please review the project settings of the supplied assembler and C examples; the project settings are accessed using: PROJECT->OPTIONS with the project name selected. Use these project settings as templates when developing your own projects. Note that if the project name is not selected when settings are made, the settings will be applied to the selected file (and not to the project).

The following project settings are recommended/required:

Specify the target device (GENERAL OPTIONS->TARGET->DEVICE)

Enable an assembler project or a C/assembler project (GENERAL OPTIONS-

>TARGET->ASSEMBLER ONLY PROJECT)

Enable the generation of an executable output file (GENERAL OPTIONS-

>OUTPUT->OUTPUT FILE->EXECUTABLE)

In order to most easily debug a C project, disable optimization (C/C++

Compiler->CODE->OPTIMIZATIONS->SIZE->NONE (BEST DEBUG

SUPPORT))

Enable the generation of debug information in the compiler output (C/C++

Compiler ->OUTPUT->GENERATE DEBUG INFO)

Specify the search path for the C preprocessor (C/C++ Compiler-

>PREPROCESSOR->INCLUDE PATHS)

Enable the generation of debug information in the assembler output

(ASSEMBLER->OUTPUT->GENERATE DEBUG-INFO)

Specify the search path for the assembler preprocessor (ASSEMBLER -

>PREPROCESSOR->INCLUDE PATHS)

In order to debug the project using C-SPY, specify a compatible format (LINKER->OUTPUT->FORMAT->DEBUG INFO [WITH TERMINAL IO])

Specify the search path for any used libraries (LINKER->CONFIG->SEARCH

PATHS)

Specify the C-SPY driver. Select PROJECT->OPTIONS->Debugger->Setup- >Driver->FET Debugger to debug on the FET (i.e., MSP430 device). Select SIMULATOR to debug on the simulator. If FET Debugger is selected, use PROJECT->OPTIONS->FET Debugger->Setup->Connection to select the appropriate port: LPTx for the parallel FET Interface or TI USB FET for the USB Interface.

2-3

Image 21
Contents 2004 Users GuideImportant Notice Page July How to Use This Manual Read This FirstAbout 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 Kit Contents, MSP-FET430UIF Software InstallationHardware 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 C-SPY Using BreakpointsBreakpoint 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 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 DirectivesMacro Directives Miscellaneous 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