Texas Instruments MSP-FET430 manual Using Single Step

Page 28

Development Flow

The RUN TO CURSOR operation temporarily requires a breakpoint. Consequently, only N-1 breakpoints can be active when RUN TO CURSOR is used if virtual breakpoints are disabled. Refer to FAQ, Debugging #31).

If, while processing a breakpoint, an interrupt becomes active, C-SPY will stop at the first instruction of the interrupt service routine. Refer to FAQ, Debugging #24).

2.3.3Using Single Step

When debugging an assembler file, STEP OVER, STEP OUT, and NEXT STATEMENT operate like STEP INTO; the current instruction is executed at full speed.

When debugging an assembler file, a step operation of a CALL instruction stops at the first instruction of the CALL’ed function.

When debugging an assembler file, a (true) STEP OVER a CALL instruction that executes the CALL’ed function at full device speed can be synthesized by placing a breakpoint after the CALL and GO’ing (to the breakpoint in “Realtime mode”).

When debugging a C file, a single step (STEP) operation executes the next C statement. Thus, it is possible to step over a function reference. If possible, a hardware breakpoint will be placed after the function reference and a GO will be implicitly executed. This will cause the function to be executed at full speed. If no hardware breakpoints are available, the function will be executed in Non- Realtime mode. STEP INTO is supported. STEP OUT is supported.

Within Disassembly mode (VIEW->DISASSEMBLY), a step operation of a non- CALL instruction executes the instruction at full device speed.

Within Disassembly mode (VIEW->DISASSEMBLY), a step operation of a CALL instruction will place – if possible - a hardware breakpoint after the CALL instruction, and then execute GO. The CALL’ed function will execute at full device speed. If no hardware breakpoint is available prior to the GO, the CALL’ed function will be executed in Non-Realtime mode. In either case, execution will stop at the instruction following the CALL.

It is only possible to single step when source statements are present. Breakpoints must be used when running code for which there is no source code (i.e., place the breakpoint after the CALL to the function for which there is no source, and then GO to the breakpoint in “Realtime mode”).

If, during a single step operation, an interrupt becomes active, the current instruction is completed and C-SPY will stop at the first instruction of the interrupt service routine. Refer to FAQ, Debugging #24).

2-10

Image 28
Contents Users Guide 2004Important Notice Page July Read This First How to Use This ManualAbout This Manual 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 Software Installation Kit Contents, MSP-FET430UIFHardware Installation, MSP-FET430X110 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 Using Breakpoints Using C-SPYBreakpoint Types 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 ReptcMiscellaneous Directives Macro DirectivesPreprocessor 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