Texas Instruments MSP-FET430 manual Frequently Asked Questions

Page 46

Frequently Asked Questions

2)C-SPY can download data into RAM, INFORMATION, and Flash MAIN memories. A warning message is output if an attempt is made to download data outside of the device memory spaces.

3)C-SPY can debug applications that utilize interrupts and low power modes. Refer to FAQ, Debugging #24).

4)C-SPY cannot access the device registers and memory while the device is running. C-SPY will display “-“ to indicate that a register/memory field is invalid. The user must stop the device in order to access device registers and memory. Any displayed register/memory fields will then be updated.

5)When C-SPY is started, the Flash memory is erased and the opened file is programmed in accordance with the download options as set in PROJECT->OPTIONS->FETDEBUGGER->DOWNLOADCONTROL->DOWNLOAD CONTROL. This initial erase and program operations can be disabled selecting PROJECT->OPTIONS-> FET DEBUGGER->DOWNLOAD CONTROL ->DOWNLOAD CONTROL- >SUPPRESS DOWNLOAD. Programming of the Flash can be initiated manually with EMULATOR->INIT NEW DEVICE.

6)The parallel port designators (LPTx) have the following physical addresses: LPT1: 378h, LPT2: 278h, LPT3: 3BCh. The configuration of the parallel port (ECP, Compatible, Bidirectional, Normal) is not significant; ECP seems to work well. Refer FAQ, Debugging #1) for additional hints on solving communication problems between C-SPY and the device.

7)C-SPY asserts RST/NMI to reset the device when C-SPY is started and when the device is programmed. The device is also reset by the C- SPY RESET button, and when the device is manually reprogrammed (EMULATOR->INIT NEW DEVICE), and when the JTAG is resynchronized (EMULATOR->RESYNCHRONIZE JTAG). When RST/NMI is not asserted (low), C-SPY sets the logic driving RST/NMI to high-impedance, and RST/NMI is pulled high via a resistor on the PCB.

RST/NMI is asserted and negated after power is applied when C-SPY is started. RST/NMI is then asserted and negated a second time after device initialization is complete.

Within C-SPY, EMULATOR->”POWER ON” RESET will cycle the power to the target to effect a reset.

8)C-SPY can debug a device whose program reconfigures the function of the RST/NMI pin to NMI.

9)The level of the XOUT/TCLK pin is undefined when C-SPY resets the device. The logic driving XOUT/TCLK is set to high-impedance at all other times.

10)When making current measurements of the device, ensure that the JTAG control signals are released (EMULATOR->RELEASE JTAG ON GO), otherwise the device will be powered by the signals on

A-8

Image 46
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 Introduction Segment ControlTranslating Asm430 Assembler Directives to A430 Directives 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