Texas Instruments MSP-FET430X110 User Manual
Texas Instruments MSP-FET430X110 User Manual

Texas Instruments MSP-FET430X110 User Manual

Msp-fet430 flash emulation tool (fet) (for use with iar embedded workbench version 3.x)
Table of Contents

Advertisement

MSP-FET430 Flash Emulation Tool (FET)
(For Use With
IAR Embedded Workbench Version 3.x)
User's Guide
Literature Number: SLAU138F
June 2004 – Revised March 2007

Advertisement

Table of Contents
loading

Summary of Contents for Texas Instruments MSP-FET430X110

  • Page 1 MSP-FET430 Flash Emulation Tool (FET) (For Use With IAR Embedded Workbench Version 3.x) User's Guide Literature Number: SLAU138F June 2004 – Revised March 2007...
  • Page 2 SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 3: Table Of Contents

    .............. 2.2.3 Using an Existing IAR V1.x/V2.x Project ..............2.2.4 Stack Management and .xcl Files ......2.2.5 How to Generate Texas Instruments .TXT (and Other Format) Files ................ 2.2.6 Overview of Example Programs ....................... Using C-SPY ..................2.3.1 Breakpoint Types ..................
  • Page 4 C.1.1 Emulator → Device Information ................ C.1.2 Emulator → Release JTAG on Go ..............C.1.3 Emulator → Resynchronize JTAG ..............C.1.4 Emulator → Init New Device ................C.1.5 Emulator → Secure - Blow JTAG Fuse ............... C.1.6 Emulator → Breakpoint Usage .................
  • Page 5 List of Figures ..............Signal Connections for 4-Wire JTAG Communication ............Signal Connections for 2-Wire Spy-Bi-Wire Communication ................... MSP-FET430X110, Schematic ....................MSP-FET430X110, PCB ..............MSP-TS430PW14 Target Socket Module, Schematic ............... MSP-TS430PW14 Target Socket Module, PCB ..............MSP-TS430DW28 Target Socket Module, Schematic ...............
  • Page 6 List of Tables ............Number of Device Breakpoints and Other Emulation Features ....................F4xx/80-pin Signal Mapping List of Tables SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 7: Preface

    Read This First About This Manual This manual documents the Texas Instruments MSP-FET430 Flash Emulation Tool (FET). The FET is the development tool for the MSP430 ultralow-power microcontroller. Both available interfaces, the parallel port interface and the USB interface, are described here.
  • Page 8 SLAU056 If You Need Assistance Support for the MSP430 device and the FET is provided by the Texas Instruments Product Information Center (PIC). Contact information for the PIC can be found on the TI web site at www.ti.com. Additional device-specific information can be found on the MSP430 web site at www.ti.com/msp430.
  • Page 9: Get Started Now

    This chapter enables you to inventory your FET, and then it instructs you how to install the software and hardware, and run the demonstration programs....................Topic Page ..........Kit Contents, MSP-FET430X110 ............. Kit Contents, MSP-FET430PIF Kit Contents, MSP-FET430Pxx0 ('P120, 'P140, 'P410, 'P430, 'P440) ............ Kit Contents, MSP-FET430UIF Kit Contents, MSP-FET430Uxx ('U14, 'U28, 'U38, 'U23x0, 'U48, ..............
  • Page 10: Kit Contents, Msp-Fet430X110

    • One READ ME FIRST document • One MSP430 CD-ROM • One MSP-FET430X110 Flash Emulation Tool. This is the PCB on which is mounted a 20-pin ZIF socket for the MSP430F11xIDW, MSP430F11x1AIDW, or MSP430F11x2IDW device. A 25-conductor cable originates from the FET for connecting to the PC parallel port.
  • Page 11: Kit Contents, Msp-Fet430Uif

    www.ti.com Kit Contents, MSP-FET430UIF • One small box containing two or four MSP430 device samples MSP-FET430P120: MSP430F123IDW and/or MSP430F1232IDW MSP-FET430P140: MSP430F149IPM and/or MSP430F169IPM MSP-FET430P410: MSP430F413IPM MSP-FET430P430: MSP430F437IPN and/or MSP430FG439 MSP-FET430P440: MSP430F449IPZ Consult the device data sheets for device specifications. Device errata can be found in the respective device product folder on the web provided as a PDF document.
  • Page 12: Software Installation

    KickStart is compatible with Windows® 98, Windows 2000, Windows ME, Windows NT 4.0, and Windows XP. However, the USB FET interface works only with Windows 2000 and Windows XP. Hardware Installation, MSP-FET430X110 1. Connect the 25-conductor cable originating from the FET to the parallel port of your PC. The driver for accessing the PC parallel port is installed during IAR Embedded Workbench installation.
  • Page 13: Hardware Installation, Msp-Fet430Uif

    (MSP430xxxx) and desired language (assembler or C). 4. Click Project → Options → FET Debugger → Setup → Connection to select the appropriate port: Texas Instruments LPT-IF for the parallel FET Interface (MSP-FET430PIF) or Texas Instruments USB-IF for the USB Interface (MSP-FET430UIF) or for the eZ430.
  • Page 14: Important Msp430 Documents On The Cd-Rom And Web

    www.ti.com Important MSP430 Documents on the CD-ROM and Web 1.12 Important MSP430 Documents on the CD-ROM and Web The primary sources of MSP430 information are the device-specific data sheet and user's guide. The most up-to-date versions of these documents that are available at the time of production are provided on the CD-ROM included with this tool.
  • Page 15: Development Flow

    Chapter 2 SLAU138F – June 2004 – Revised March 2007 Development Flow This chapter describes how to use KickStart to develop application software and how to use C-SPY to debug it....................Topic Page .................. Overview ................. Using KickStart ................Using C-SPY SLAU138F –...
  • Page 16: Overview

    www.ti.com Overview 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 simulator of the device.
  • Page 17 9. Specify the active parallel port used to interface to the FET if not LPT1 (FET Debugger → Setup → Connection → Texas Instruments LPT-IF) or specify the USB port (FET Debugger → Setup → Connection → Texas Instruments USB-IF).
  • Page 18: Creating A Project From Scratch

    www.ti.com Using KickStart 2.2.2 Creating a Project From Scratch This section presents step-by-step instructions to create an assembler or C project from scratch, and to download and run the application on the MSP430 (see also Section 2.2.1, Project Settings). The MSP430 IAR Embedded Workbench IDE User's Guide presents a more comprehensive overview of the process.
  • Page 19: Using An Existing Iar V1.X/V2.X Project

    -D_STACK_SIZE=xx to allocate xx bytes for the stack. Note that the .xcl file also reserves 50 byes for the heap if required (for example, by malloc()). 2.2.5 How to Generate Texas Instruments .TXT (and Other Format) Files The KickStart linker can be configured to output objects in TI .TXT format for use with the GANG430 and PRGS430 programmers.
  • Page 20: Using C-Spy

    www.ti.com Using C-SPY Using C-SPY Appendix C for a description of FET-specific menus within C-SPY. 2.3.1 Breakpoint Types The C-SPY breakpoint mechanism makes use of a limited number of on-chip debugging resources (specifically, N breakpoint registers, see Table 2-1). When N or fewer breakpoints are set, the application runs at full device speed (or realtime).
  • Page 21: Using Single Step

    www.ti.com Using C-SPY 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 (see FAQ Debugging #33). If, while processing a breakpoint, an interrupt becomes active, C-SPY stops at the first instruction of the interrupt service routine (see FAQ Debugging #26).
  • Page 22 www.ti.com Using C-SPY To change the format of the displayed variable (default, binary, octal, decimal, hex, char), select the type, click the right mouse button, and then select the desired format. The value of the displayed variable can be changed by selecting it, and then entering the new value. In C, variables can be watched by selecting them and then dragging and dropping them into the Watch Window.
  • Page 23: Design Considerations For In-Circuit Programming

    Chapter 3 SLAU138F – June 2004 – Revised March 2007 Design Considerations for In-Circuit Programming This chapter presents signal requirements for in-circuit programming of the MSP430....................Topic Page Signal Connections for In-System Programming and Debugging, ....MSP-FET430PIF, MSP-FET430UIF, GANG430, PRGS430 .................
  • Page 24: Signal Connections For In-System Programming And Debugging, Msp-Fet430Pif, Msp-Fet430Uif, Gang430, Prgs430

    www.ti.com Signal Connections for In-System Programming and Debugging, MSP-FET430PIF, MSP-FET430UIF, GANG430, PRGS430 Signal Connections for In-System Programming and Debugging, MSP-FET430PIF, MSP-FET430UIF, GANG430, PRGS430 With the proper connections, the C-SPY debugger and an FET hardware JTAG interface, such as the MSP-FET430PIF and MSP-FET430UIF, can be used to program and debug code on a target board. In addition, the connections can also support the GANG430 or PRGS430 production programmers, which provide an easy way to program prototype boards, if desired.
  • Page 25: Signal Connections For 4-Wire Jtag Communication

    www.ti.com Signal Connections for In-System Programming and Debugging, MSP-FET430PIF, MSP-FET430UIF, GANG430, PRGS430 J1 (see Note A) V /AV /DV J2 (see Note A) 0.1 µF 10 µF Ω 47 k MSP430Fxxx (see Note B) JTAG RST/NMI VCC TOOL TDO/TDI TDO/TDI VCC TARGET TDI/VPP TDI/VPP...
  • Page 26: External Power

    In this case, external power can be supplied to the tool via connections provided on the MSP-FET430X110 and the target socket modules. See the schematics of the MSP-FET430X110 and the target socket modules in...
  • Page 27: Bootstrap Loader

    www.ti.com Bootstrap Loader When a target socket module is powered from an external supply, the external supply powers the device on the target socket module and any user circuitry connected to the target socket module, and the FET interface module continues to be powered from the PC via the parallel port. If the externally supplied voltage differs from that of the FET interface module, the target socket module must be modified so that the externally supplied voltage is routed to the FET interface module (so that it may adjust its output voltage levels accordingly).
  • Page 28 www.ti.com Design Considerations for In-Circuit Programming SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 29: Frequently Asked Questions

    Appendix A SLAU138F – June 2004 – Revised March 2007 Frequently Asked Questions This appendix presents solutions to frequently asked questions regarding hardware, program development, and debugging tools....................Topic Page ................. Hardware ....Program Development (Assembler, C-Compiler, Linker) ..............Debugging (C-SPY) SLAU138F –...
  • Page 30: Hardware

    Use an external clock source to drive XIN directly. 4. When the MSP-FET430X110 is used as an interface to an MSP430 on the user's circuit (i.e., there is no MSP430 device in the FET socket), the XOUT and XIN signals from the FET should not be connected to the corresponding pins of the in-circuit MSP430.
  • Page 31: Program Development (Assembler, C-Compiler, Linker)

    www.ti.com Program Development (Assembler, C-Compiler, Linker) 12. Information memory may not be blank (erased to 0xFF) when the device is delivered from TI. Customers should erase the information memory before its first usage. Main memory of packaged devices is blank when the device is delivered from TI. 13.
  • Page 32 www.ti.com Program Development (Assembler, C-Compiler, Linker) 11. The example programs given in the KickStart documentation (i.e., Demo, Tutor, etc.) are not correct. The programs work only in the simulator. However, the programs do not function correctly on an actual device, because the Watchdog mechanism is active. The programs need to be modified to disable the Watchdog mechanism.
  • Page 33: Debugging (C-Spy)

    www.ti.com Debugging (C-SPY) 20. Numerous C and C++ runtime libraries are provided with the Workbench: cl430d: C, 64-bit doubles cl430dp: C, 64-bit doubles, position independent cl430f: C, 32-bit doubles cl430fp: C, 32-bit doubles, position independent dl430d: C++, 64-bit doubles dl430dp: C++, 64-bit doubles, position independent dl430f: C++, 32-bit doubles dl430fp: C++, 32-bit doubles, position independent See the IAR MSP430 C/C++ compiler reference guide for more information on which library to use.
  • Page 34 www.ti.com Debugging (C-SPY) 4. 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. 5. C-SPY can debug applications that utilize interrupts and low power modes (see FAQ Debugging #26).
  • Page 35 www.ti.com Debugging (C-SPY) 19. C-SPY utilizes the system clock to control the device during debugging. Therefore, device counters, etc., that are clocked by the Main System Clock (MCLK) will be affected when C-SPY has control of the device. Special precautions are taken to minimize the effect upon the Watchdog Timer. The CPU core registers are preserved.
  • Page 36 www.ti.com Debugging (C-SPY) 31. It is possible to use C-SPY to get control of a running device whose state is unknown. Simply use C-SPY to program a dummy device, and then start the application with Release JTAG on Go selected. Remove the JTAG connector from the dummy device and connect to the unknown device. Select Debug →...
  • Page 37: B Hardware

    Appendix B SLAU138F – June 2004 – Revised March 2007 Hardware This appendix contains information relating to the FET hardware, including schematics and PCB pictorials....................Topic Page ............... Schematics and PCBs ..........MSP-FET430UIF Revision History SLAU138F – June 2004 – Revised March 2007 Hardware Submit Documentation Feedback...
  • Page 38: Schematics And Pcbs

    Schematics and PCBs Schematics and PCBs Figure B-1. MSP-FET430X110, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 39: Msp-Fet430X110, Pcb

    LED connected to P1.0 Jumper J5 Open to disconnect LED Orient Pin 1 of Ensure value is 82 Ω MSP430 device Jumper J1 Open to measure current Figure B-2. MSP-FET430X110, PCB SLAU138F – June 2004 – Revised March 2007 Hardware Submit Documentation Feedback...
  • Page 40: Msp-Ts430Pw14 Target Socket Module, Schematic

    www.ti.com Schematics and PCBs Figure B-3. MSP-TS430PW14 Target Socket Module, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 41: Msp-Ts430Pw14 Target Socket Module, Pcb

    www.ti.com Schematics and PCBs Connector J3 External power connector Jumper J5 to 'ext' LED connected to P1.0 Jumpers J7 to J12 Close 1-2 to debug in Spy-Bi-Wire Mode. Jumper J4 Close 2-3 to debug in Open to disconnect LED 4-wire JTAG mode. Orient Pin 1 of Jumper J6 MSP430 device...
  • Page 42: Msp-Ts430Dw28 Target Socket Module, Schematic

    www.ti.com Schematics and PCBs Note: Connections between the JTAG header and pins XOUT and XIN are not required and should not be made. Figure B-5. MSP-TS430DW28 Target Socket Module, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 43: Msp-Ts430Dw28 Target Socket Module, Pcb

    www.ti.com Schematics and PCBs LED connected to P1.0 Jumper J5 Jumper J4 Open to measure current Open to disconnect LED Connector J3 External power connector Remove R8 and jumper R9 Orient Pin 1 of MSP430 device Figure B-6. MSP-TS430DW28 Target Socket Module, PCB SLAU138F –...
  • Page 44: Msp-Ts430Da38 Target Socket Module, Schematic

    www.ti.com Schematics and PCBs Figure B-7. MSP-TS430DA38 Target Socket Module, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 45: Msp-Ts430Da38 Target Socket Module, Pcb

    www.ti.com Schematics and PCBs Jumpers JP4 to JP9 Close 1-2 to debug in Spy-Bi-Wire Mode, LED connected to P1.0 Close 2-3 to debug in 4-wire JTAG Mode Jumper JP3 Open to disconnect LED Orient pin 1 of MSP430 device Jumper JP2 Open to measure current Connector J3 External power connector...
  • Page 46: Msp-Ts430Qfn23X0 Target Socket Module, Schematic

    www.ti.com Schematics and PCBs Figure B-9. MSP-TS430QFN23x0 Target Socket Module, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 47: Msp-Ts430Qfn23X0 Target Socket Module, Pcb

    www.ti.com Schematics and PCBs Connector J5 External power connector Jumper JP2 Jumper JP1 to 'ext' Open to measure current Jumper JP3 Open to disconnect LED LED connected to P1.0 Figure B-10. MSP-TS430QFN23x0 Target Socket Module, PCB SLAU138F – June 2004 – Revised March 2007 Hardware Submit Documentation Feedback...
  • Page 48: Msp-Ts430Dl48 Target Socket Module, Schematic

    www.ti.com Schematics and PCBs Figure B-11. MSP-TS430DL48 Target Socket Module, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 49: Msp-Ts430Dl48 Target Socket Module, Pcb

    www.ti.com Schematics and PCBs Jumper J5 Open to measure current LED connected Connector J3 to P1.0 External power connector Jumper JP1 to ‘ext’ Jumper J4 Open to disconnect LED Orient pin 1 of MSP430 device Figure B-12. MSP-TS430DL48 Target Socket Module, PCB SLAU138F –...
  • Page 50: Msp-Ts430Pm64 Target Socket Module, Schematic

    www.ti.com Schematics and PCBs Note: Connections between the JTAG header and pins XOUT and XIN are not required and should not be made. Figure B-13. MSP-TS430PM64 Target Socket Module, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 51: Msp-Ts430Pm64 Target Socket Module, Pcb

    www.ti.com Schematics and PCBs Connector J5 LED connected to pin 12 External power connection Remove R8 and jumper R9 Jumper J7 Open to measure current Jumper J6 Open to disconnect LED Orient Pin 1 of MSP430 device Figure B-14. MSP-TS430PM64 Target Socket Module, PCB SLAU138F –...
  • Page 52: Msp-Ts430Pn80 Target Socket Module, Schematic

    www.ti.com Schematics and PCBs Figure B-15. MSP-TS430PN80 Target Socket Module, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 53: Msp-Ts430Pn80 Target Socket Module, Pcb

    www.ti.com Schematics and PCBs LED connected to pin 12 Connector J5 External power connection Remove R8 and jumper R9 Jumper J6 Open to disconnect LED Orient Pin 1 of MSP430 device Figure B-16. MSP-TS430PN80 Target Socket Module, PCB SLAU138F – June 2004 – Revised March 2007 Hardware Submit Documentation Feedback...
  • Page 54: Msp-Ts430Pz100 Target Socket Module, Schematic

    www.ti.com Schematics and PCBs Note: Connections between the JTAG header and pins XOUT and XIN are not required and should not be made. Figure B-17. MSP-TS430PZ100 Target Socket Module, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 55: Msp-Ts430Pz100 Target Socket Module, Pcb

    www.ti.com Schematics and PCBs Jumper J7 Jumper J6 Open to measure current Open to disconnect LED LED connected to pin 12 Connector J5 External power connection Remove R8 and jumper R9 Orient Pin 1 of MSP430 device Figure B-18. MSP-TS430PZ100 Target Socket Module, PCB SLAU138F –...
  • Page 56: Msp-Fet430Pif Fet Interface Module, Schematic

    www.ti.com Schematics and PCBs Figure B-19. MSP-FET430PIF FET Interface Module, Schematic Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 57: Msp-Fet430Pif Fet Interface Module, Pcb

    www.ti.com Schematics and PCBs Figure B-20. MSP-FET430PIF FET Interface Module, PCB SLAU138F – June 2004 – Revised March 2007 Hardware Submit Documentation Feedback...
  • Page 58: Msp-Fet430Uif Usb Interface, Schematic (1 Of 4)

    www.ti.com Schematics and PCBs Figure B-21. MSP-FET430UIF USB Interface, Schematic (1 of 4) Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 59: Msp-Fet430Uif Usb Interface, Schematic (2 Of 4)

    www.ti.com Schematics and PCBs Figure B-22. MSP-FET430UIF USB Interface, Schematic (2 of 4) SLAU138F – June 2004 – Revised March 2007 Hardware Submit Documentation Feedback...
  • Page 60: Msp-Fet430Uif Usb Interface, Schematic (3 Of 4)

    www.ti.com Schematics and PCBs Figure B-23. MSP-FET430UIF USB Interface, Schematic (3 of 4) Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 61: Msp-Fet430Uif Usb Interface, Schematic (4 Of 4)

    www.ti.com Schematics and PCBs Figure B-24. MSP-FET430UIF USB Interface, Schematic (4 of 4) SLAU138F – June 2004 – Revised March 2007 Hardware Submit Documentation Feedback...
  • Page 62: Msp-Fet430Uif Usb Interface, Pcb

    www.ti.com Schematics and PCBs Figure B-25. MSP-FET430UIF USB Interface, PCB Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 63: Msp-Fet430Uif Revision History

    www.ti.com MSP-FET430UIF Revision History MSP-FET430UIF Revision History Revision 1.3 • Initial released hardware version Assembly change on 1.3 (May 2005) • R29, R51, R42, R21, R22, R74: value changed from 330R to 100R Changes 1.3 to 1.4 (Aug 2005) • J5: VBUS and RESET additionally connected •...
  • Page 64 www.ti.com Hardware SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 65: Fet-Specific Menus

    Appendix C SLAU138F – June 2004 – Revised March 2007 FET-Specific Menus ....................Topic Page ..................Menus SLAU138F – June 2004 – Revised March 2007 FET-Specific Menus Submit Documentation Feedback...
  • Page 66: Menus

    www.ti.com Menus Menus C.1.1 Emulator → Device Information Opens a window with information about the target device being used. Also, this window allows adjusting the target voltage in the case an MSP-FET430UIF interface is used to supply power to the target by performing a right-click inside this window.
  • Page 67: Emulator → Advanced → Memory Dump

    www.ti.com Menus C.1.9 Emulator → Advanced → Memory Dump Write the specified device memory contents to a specified file. A conventional dialog is displayed that permits the user to specify a file name, a memory starting address, and a length. The addressed memory is then written in a text format to the named file.
  • Page 68 www.ti.com FET-Specific Menus SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 69: 80-Pin Msp430F44X And Msp430F43X Device Emulation

    Appendix D SLAU138F – June 2004 – Revised March 2007 80-Pin MSP430F44x and MSP430F43x Device Emulation 80-pin MSP430F44x and MSP430F43x devices can be emulated by the 100-pin MSP430F449 device. Table D-1 lists where the pin signals of an 80-pin device appear on the pins of an MSP-TS430PZ100 target socket module.
  • Page 70: F4Xx/80-Pin Signal Mapping

    www.ti.com F4xx/80-Pin Signal Mapping F4xx/80-Pin Signal Mapping Table D-1. F4xx/80-pin Signal Mapping Connection Required MSP430-TS430PZ100 F4xx/80-pin Signal F4xx/80-pin Pin Number Between Indicated Pins of Pin Number MSP430-TS430PZ100 Socket DVcc1 P6.3/A3 P6.4/A4 P6.5/A5 P6.6/A6 P6.7/A7 VREF+ XOUT VeREF+ VREF-/VeREF- P5.1/S0 P5.0/S1 P4.7/S2 14-46 P4.6/S3...
  • Page 71 www.ti.com F4xx/80-Pin Signal Mapping Table D-1. F4xx/80-pin Signal Mapping (continued) Connection Required MSP430-TS430PZ100 F4xx/80-pin Signal F4xx/80-pin Pin Number Between Indicated Pins of Pin Number MSP430-TS430PZ100 Socket P3.0/STE0/S31 43-71 COM0 P5.2/COM1 P5.3/COM2 P5.4/COM3 P5.5/R13 P5.6/R23 P5.7/R33 DVcc2 DVss2 P2.5/URXD0 P2.4/UTXD0 P2.3.TB2 P2.2/TB1 P2.1/TB0 P2.0/TA2...
  • Page 72 www.ti.com 80-Pin MSP430F44x and MSP430F43x Device Emulation SLAU138F – June 2004 – Revised March 2007 Submit Documentation Feedback...
  • Page 73: Msp-Fet430Uif Installation Guide

    Appendix E SLAU138F – June 2004 – Revised March 2007 MSP-FET430UIF Installation Guide This section describes the hardware installation process of the MSP-FET430UIF USB debug interface on a PC running Windows XP. The installation procedure for a Windows 2000 system is very similar and, therefore, not shown here....................
  • Page 74: Hardware Installation

    www.ti.com Hardware Installation Hardware Installation 1. Connect the MSP-FET430UIF USB Debug Interface with a USB cable to a USB port of your PC. 2. Windows now should recognize the new hardware as an "MSP430 USB FET x.xx.xx" (see Figure E-1). Figure E-1.
  • Page 75: Winxp Driver Location Selection Folder

    www.ti.com Hardware Installation 5. Browse to the folder where the driver information files are located (see Figure E-3). On a default installation the files are located in the following directory: C:\Program Files\IAR Systems\Embedded Workbench 4.0\430\drivers\TIUSBFET\WinXP Figure E-3. WinXP Driver Location Selection Folder 6.
  • Page 76: Winxp Driver Installation

    www.ti.com Hardware Installation 7. Note that WinXP shows a warning that the driver is not certified by Microsoft®. Ignore this warning and click "Continue Anyway" (see Figure E-4). Figure E-4. WinXP Driver Installation 8. The Wizard installs the driver files. 9.
  • Page 77: Device Manager

    www.ti.com Hardware Installation 12. The MSP-FET430UIF debug interface is installed and ready to use. The Device Manager lists a new entry as shown in Figure E-5. Figure E-5. Device Manager SLAU138F – June 2004 – Revised March 2007 MSP-FET430UIF Installation Guide Submit Documentation Feedback...
  • Page 78: Document Revision History

    www.ti.com Document Revision History Document Revision History Version Changes/Comments • Renamed MSP-FET430U40 to MSP-FET430U23x0. • Replaced MSP-FET430U40 schematic and PCB figures with renamed MSP-FET430U23x0 images. SLAU138F • Added FAQ Hardware #2 Section A.1. • Added FAQ Debugging #3 Section A.3. NOTE: Page numbers for previous revisions may differ from page numbers in the current version.
  • Page 79: Important Notices

    EVALUATION BOARD/KIT IMPORTANT NOTICE Texas Instruments (TI) provides the enclosed product(s) under the following conditions: This evaluation board/kit is intended for use for ENGINEERING DEVELOPMENT, DEMONSTRATION, OR EVALUATION PURPOSES ONLY and is not considered by TI to be a finished end-product fit for general consumer use.
  • Page 80 TI product or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements. Following are URLs where you can obtain information on other Texas Instruments products and application solutions:...

Table of Contents