manualshive.com logo in svg

Texas Instruments MSP-FET430PIF, User Manual

Share
Download
Texas Instruments MSP-FET430PIF User Manual Download Page 12

www.ti.com

1.6

Software Installation

1.7

Hardware Installation, MSP-FET430X110

1.8

Hardware Installation, MSP-FET430PIF

Software Installation

•

Four or eight headers
MSP-FET430U14: Four PCB 1

×

7-pin headers (two male and two female)

MSP-FET430U28: Four PCB 1

×

14-pin headers (two male and two female)

MSP-FET430U38: Four PCB 1

×

19-pin headers (two male and two female)

MSP-FET430U23x0: Eight PCB 1

×

10-pin headers (four male and four female)

MSP-FET430U48: Four PCB 2

×

24-pin headers (two male and two female)

MSP-FET430U64: Eight PCB 1x16-pin headers (four male and four female)
MSP-FET430U80: Eight PCB 1x20-pin headers (four male and four female)
MSP-FET430U100: Eight PCB 1x25-pin headers (four male and four female)

•

One small box containing two or four MSP430 device samples
MSP-FET430U14: MSP430F2013IPW
MSP-FET430U28: MSP430F123IDW and/or MSP430F1232IDW
MSP-FET430U38: MSP430F2274IDA
MSP-FET430U23x0: MSP430F2370IRHA
MSP-FET430U48: MSP430F4270IDL
MSP-FET430U64: MSP430F417IPM and MSP430F169IPM
MSP-FET430U80: MSP430FG439IPN
MSP-FET430U100: MSP430F449IPZ and MSP430FG4619IPZ
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. Depending on the device, errata may
also be found in the device bug database at

www.ti.com/sc/cgi-bin/buglist.cgi

.

Follow the instructions on the supplied READ ME FIRST document to install the IAR Embedded
Workbench™ KickStart. Read the file <Installation Root>\Embedded Workbench x.x\430\doc\readme.htm
from IAR for the latest information about the Workbench. The term KickStart refers to the function-limited
version of Embedded Workbench (including C-SPY™ debugger). KickStart is supplied on the CD-ROM
included with each FET, and the latest version is available from the MSP430 web site.

The documents mentioned in the previous paragraph (and this document) can be accessed using: Start

→

Programs

→

IAR Systems

→

IAR Embedded Workbench KickStart for MSP430 V3.

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.

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. Note that a
restart is required after the IAR Embedded Workbench installation for the driver to become active.

2. Ensure that the MSP430F1121AIDW is securely seated in the socket and that its pin 1 (indicated with

a circular indentation on the top surface) aligns with the "1" mark on the PCB.

3. Ensure that jumpers J1 (near the non-socketed IC on the FET) and J5 (near the LED) are in place.

Schematics of the FET and its parts are presented in

Appendix B

.

1. Use the 25-conductor cable to connect the FET interface module to the parallel port of your PC. The

necessary driver for accessing the PC parallel port will be installed automatically during IAR Embedded
Workbench installation. Note that a restart is required after the IAR Embedded Workbench installation
for the driver to become active.

2. Use the 14-conductor cable to connect the parallel port debug interface module to a target board, such

as an MSP-TS430xxx target socket module.

Get Started Now!

12

SLAU138F – June 2004 – Revised March 2007

Submit Documentation Feedback

Summary of Contents for MSP-FET430PIF

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: ...2 SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 3: ...Settings 16 2 2 2 Creating a Project From Scratch 18 2 2 3 Using an Existing IAR V1 x V2 x Project 19 2 2 4 Stack Management and xcl Files 19 2 2 5 How to Generate Texas Instruments TXT and Other Format Files 19 2 2 6 Overview of Example Programs 19 2 3 Using C SPY 20 2 3 1 Breakpoint Types 20 2 3 2 Using Breakpoints 20 2 3 3 Using Single Step 21 2 3 4 Using Watch Windows 21 3 Design Consideration...

Page 4: ...reakpoint Combiner 67 C 1 11 Emulator State Storage Control 67 C 1 12 Emulator State Storage Window 67 C 1 13 Emulator Sequencer Control 67 C 1 14 Emulator Power on Reset 67 C 1 15 Emulator GIE on off 67 C 1 16 Emulator Leave Target Running 67 C 1 17 Emulator Force Single Stepping 67 D 80 Pin MSP430F44x and MSP430F43x Device Emulation 69 D 1 F4xx 80 Pin Signal Mapping 70 E MSP FET430UIF Installati...

Page 5: ...MSP TS430PM64 Target Socket Module Schematic 50 B 14 MSP TS430PM64 Target Socket Module PCB 51 B 15 MSP TS430PN80 Target Socket Module Schematic 52 B 16 MSP TS430PN80 Target Socket Module PCB 53 B 17 MSP TS430PZ100 Target Socket Module Schematic 54 B 18 MSP TS430PZ100 Target Socket Module PCB 55 B 19 MSP FET430PIF FET Interface Module Schematic 56 B 20 MSP FET430PIF FET Interface Module PCB 57 B 2...

Page 6: ...List of Tables 2 1 Number of Device Breakpoints and Other Emulation Features 20 D 1 F4xx 80 pin Signal Mapping 70 6 List of Tables SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 7: ... interface MSP FET430PIF and the respective target socket module MSP FET430X110 for the MSP430F11xIDW MSP430F11x1AIDW and MSP430F11x2IDW devices MSP FET430P120 for the MSP430F12xIDW and MSP430F12x2IDW devices MSP FET430P140 for the MSP430F13xIPM MSP430F14xIPM MSP430F15xIPM MSP430F16xIPM and MSP430F161xIPM devices MSP FET430P410 for the MSP430F41xIPM devices MSP FET430P430 for the MSP430F43xIPN dev...

Page 8: ... 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 Note KickStart is supported by Texas Instruments Although KickStart is a product of IAR Texas Instruments provides the support for it Therefore please do not request support for KickStart from IAR Please consult the extensive documentation provi...

Page 9: ...10 1 4 Kit Contents MSP FET430UIF 11 1 5 Kit Contents MSP FET430Uxx U14 U28 U38 U23x0 U48 U64 U80 U100 11 1 6 Software Installation 12 1 7 Hardware Installation MSP FET430X110 12 1 8 Hardware Installation MSP FET430PIF 12 1 9 Hardware Installation MSP FET430UIF 13 1 10 Hardware Installation MSP FET430Uxx U14 U28 U38 U23x0 U48 U64 U80 U100 MSP FET430Pxx0 P120 P140 P410 P430 P440 13 1 11 Flashing th...

Page 10: ...get socket module This is the PCB on which is mounted a 64 pin clam shell style socket for the MSP430F13xIPM MSP430F14xIPM MSP430F15xIPM MSP430F16xIPM or MSP430F161xIPM device A 2 7 pin male connector is also present on the PCB MSP FET430P410 One MSP TS430PM64 target socket module This is the PCB on which is mounted a 64 pin clam shell style socket for the MSP430F41xIPM device A 2 7 pin male conne...

Page 11: ...ket It fits all MSP430 devices in 20 and 28 pin DW packages A 2 7 pin male connector is also present on the PCB MSP FET430U38 One MSP TS430DA38 target socket module This is the PCB on which is mounted a 38 pin ZIF socket It fits all MSP430 devices in 38 pin DA packages A 2 7 pin male connector is also present on the PCB MSP FET430U23x0 One MSP TS430QFN23x0 former name MSP TS430QFN40 target socket ...

Page 12: ...e term KickStart refers to the function limited version of Embedded Workbench including C SPY debugger KickStart is supplied on the CD ROM included with each FET and the latest version is available from the MSP430 web site The documents mentioned in the previous paragraph and this document can be accessed using Start Programs IAR Systems IAR Embedded Workbench KickStart for MSP430 V3 KickStart is ...

Page 13: ...rcular indentation on the top surface aligns with the 1 mark on the PCB 3 Ensure that the two jumpers LED and VCC near the 2 7 pin male connector are in place Schematics of the target socket module and its parts are presented in Appendix B Note Regarding U38 see FAQ Hardware 2 This section demonstrates on the FET the equivalent of the C language Hello World introductory program An application that...

Page 14: ... web site www ti com msp430 contain the most recent version of these documents Documents describing the IAR tools Workbench C SPY the assembler the C compiler the linker and the librarian are located in the common doc and 430 doc folders The documents are in PDF format Supplements to the documents i e the latest information are available in HTML format in the same directories 430 doc readme_start ...

Page 15: ... This chapter describes how to use KickStart to develop application software and how to use C SPY to debug it Topic Page 2 1 Overview 16 2 2 Using KickStart 16 2 3 Using C SPY 20 SLAU138F June 2004 Revised March 2007 Development Flow 15 Submit Documentation Feedback ...

Page 16: ... icc430 htm icc430_msg htm C library CLibrary htm Linker and Librarian xlink pdf xlink htm xman htm xar htm The KickStart development environment is function limited The following restrictions are in place The C compiler does not generate an assembly code list file The linker links a maximum of 4K bytes of code originating from C source but an unlimited amount of code originating from assembler so...

Page 17: ...Virtual Breakpoints FET Debugger Breakpoints Use virtual breakpoints and disable all System Breakpoints FET Debugger Breakpoints System breakpoints on Note Use Factory Settings to quickly configure a project Use the Factory Settings button to quickly configure a project to a usable state The following steps can be used to quickly configure a project Note that the General Options tab does not have ...

Page 18: ...rogram text file to the project Project Add Files Select the program text file and click Open Alternatively double click on the file to add it to the project Note How to add assembler source files to your project The default file type presented in the Add Files window is C C Files To view assembler files s43 select Assembler Files in the Files of type drop down menu 8 Save the workspace File Save ...

Page 19: ...M for the stack regardless if this amount of stack is actually required or if it is sufficient There is no runtime checking of the stack The stack can overflow the 50 reserved bytes and possibly overwrite the other segments No error is output The supplied xcl files can be modified to tune the size of the stack to the needs of the application edit D_STACK_SIZE xx to allocate xx bytes for the stack ...

Page 20: ...points and Other Emulation Features 4 Wire 2 Wire Breakpoints Range Clock State Trace Device JTAG Spy Bi Wire N Breakpoints Control Sequencer Buffer MSP430F11x1 X 2 MSP430F11x2 X 2 MSP430F12x X 2 MSP430F12x2 X 2 MSP430F13x X 3 X MSP430F14x X 3 X MSP430F15x X 8 X X X X MSP430F16x X 8 X X X X MSP430F161x X 8 X X X X MSP430F20xx X X 2 X MSP430F21x1 X 2 X MSP430F22x4 X X 2 X MSP430F23x0 X 2 X MSP430F4...

Page 21: ...e View Disassembly a step operation of a CALL instruction places if possible a hardware breakpoint after the CALL instruction and then executes Go The called function executes at full device speed If no hardware breakpoint is available prior to the Go the called function is executed in non realtime mode In either case execution stops at the instruction following the CALL It is only possible to sin...

Page 22: ...d it is possible to extend the concept of watching variables to watching peripherals Be aware that there may be side effects when peripherals are read and written by C SPY see FAQ Debugging 24 CPU core registers can be specified for watching by preceding their name with i e PC SR SP R5 etc Variables watched within the Watch Window are only updated when C SPY gets control of the device for example ...

Page 23: ...ements for in circuit programming of the MSP430 Topic Page 3 1 Signal Connections for In System Programming and Debugging MSP FET430PIF MSP FET430UIF GANG430 PRGS430 24 3 2 External Power 26 3 3 Bootstrap Loader 27 SLAU138F June 2004 Revised March 2007 Design Considerations for In Circuit Programming 23 Submit Documentation Feedback ...

Page 24: ... or other local power supply and adjusts the output signals accordingly If the target board is to be powered by a local VCC the connection to pin 4 on the JTAG should be made and not the connection to pin 2 This utilizes the VCC sense feature and prevents any contention that might occur if the local on board VCC were connected to the VCC supplied from the FET interface module or the GANG430 If the...

Page 25: ...r s guide for the recommended configuration C The TEST VPP pin is only available on MSP430 family members with multiplexed JTAG pins See the device data sheet to determine if this pin is available D The connection to the JTAG connector RST pin is optional when using 4 wire JTAG communication mode capable only devices and is not required for device programming or debugging However this connection i...

Page 26: ...re Communication The PC parallel port can source only a limited amount of current Because of the ultralow power capability of the MSP430 a standalone FET does not exceed the available current However if additional circuitry is added to the tool this current limit could be exceeded In this case external power can be supplied to the tool via connections provided on the MSP FET430X110 and the target ...

Page 27: ...TAG pins most MSP430Fxxx devices contain a program a Bootstrap Loader that permits the Flash memory to be erased and programmed simply using a reduced set of signals Application reports SLAA089 and SLAA096 fully describe this interface TI does not produce a BSL tool However customers can easily develop their own BSL tools using the information in the application reports or BSL tools can be purchas...

Page 28: ...www ti com Design Considerations for In Circuit Programming 28 SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 29: ...solutions to frequently asked questions regarding hardware program development and debugging tools Topic Page A 1 Hardware 30 A 2 Program Development Assembler C Compiler Linker 31 A 3 Debugging C SPY 33 SLAU138F June 2004 Revised March 2007 Frequently Asked Questions 29 Submit Documentation Feedback ...

Page 30: ...while the application is running Note that in this mode a manual halt is required to see if a breakpoint was hit See the IDE documentation for more information on this feature 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 sh...

Page 31: ... not use the files with the FET see 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 resets the device if not disabled or properly handled by the application see FAQ Program Development 14 3 When adding source files to a project do not add files that are included by source files that have already been added ...

Page 32: ... CSTARTUP the source screen goes blank as C SPY is not able to locate the source code for CSTARTUP Be aware that CSTARTUP can take a significant amount of time to execute if a large number of initialized global variables are used int __low_level_init void Insert your low level initializations here WDTCTL WDTPW WDTHOLD Stop Watchdog timer Choose if segment initialization should be done or not Retur...

Page 33: ...the parallel port is located at LPT1 Ensure that no other software application has reserved taken control of the parallel port for example printer drivers ZIP drive drivers etc if a parallel port MSP FET430PIF interface is used Such software can prevent the C SPY FET driver from accessing the parallel port and hence communicating with the device It may be necessary to reboot the computer to comple...

Page 34: ... whose program reconfigures the function of the RST NMI pin to NMI 11 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 12 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 th...

Page 35: ...certain MSP430 devices such as MSP430F15x 16x and MSP430F43x 44x devices bits do not behave this way i e the bits are not cleared by C SPY read operations 25 C SPY cannot be used to debug programs that execute in the RAM of F12x and F41x devices A work around to this limitation is to debug programs in Flash 26 While single stepping with active and enabled interrupts it can appear that only the int...

Page 36: ...re statistical events 35 On devices without data breakpoint capabilities it s possible to associate with an instruction breakpoint an arbitrarily complex expression that C SPY evaluates when the breakpoint is hit This mechanism can be used to synthesize a data breakpoint See the C SPY documentation for a description of this complex breakpoint mechanism 36 The ROM Monitor referenced by the C SPY do...

Page 37: ...This appendix contains information relating to the FET hardware including schematics and PCB pictorials Topic Page B 1 Schematics and PCBs 38 B 2 MSP FET430UIF Revision History 63 SLAU138F June 2004 Revised March 2007 Hardware 37 Submit Documentation Feedback ...

Page 38: ...www ti com B 1 Schematics and PCBs Schematics and PCBs Figure B 1 MSP FET430X110 Schematic 38 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 39: ...t LED Orient Pin 1 of MSP430 device Connector J4 External power connector Jumper J1 Open to measure current R6 Ensure value is 82 Ω Schematics and PCBs Figure B 2 MSP FET430X110 PCB SLAU138F June 2004 Revised March 2007 Hardware 39 Submit Documentation Feedback ...

Page 40: ...www ti com Schematics and PCBs Figure B 3 MSP TS430PW14 Target Socket Module Schematic 40 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 41: ...tor 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 Close 2 3 to debug in 4 wire JTAG mode Schematics and PCBs Figure B 4 MSP TS430PW14 Target Socket Module PCB SLAU138F June 2004 Revised March 2007 Hardware 41 Submit Documentation Feedback ...

Page 42: ...e 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 42 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 43: ...ice Jumper J5 Open to measure current Connector J3 External power connector Remove R8 and jumper R9 LED connected to P1 0 Schematics and PCBs Figure B 6 MSP TS430DW28 Target Socket Module PCB SLAU138F June 2004 Revised March 2007 Hardware 43 Submit Documentation Feedback ...

Page 44: ...www ti com Schematics and PCBs Figure B 7 MSP TS430DA38 Target Socket Module Schematic 44 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 45: ...Open to disconnect LED Jumper JP2 Open to measure current Jumpers JP4 to JP9 Close 1 2 to debug in Spy Bi Wire Mode Close 2 3 to debug in 4 wire JTAG Mode Schematics and PCBs Figure B 8 MSP TS430DA38 Target Socket Module PCB Note See Section A 1 note 2 SLAU138F June 2004 Revised March 2007 Hardware 45 Submit Documentation Feedback ...

Page 46: ...www ti com Schematics and PCBs Figure B 9 MSP TS430QFN23x0 Target Socket Module Schematic 46 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 47: ...power connector Jumper JP1 to ext Jumper JP3 Open to disconnect LED Jumper JP2 Open to measure current Schematics and PCBs Figure B 10 MSP TS430QFN23x0 Target Socket Module PCB SLAU138F June 2004 Revised March 2007 Hardware 47 Submit Documentation Feedback ...

Page 48: ...www ti com Schematics and PCBs Figure B 11 MSP TS430DL48 Target Socket Module Schematic 48 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 49: ...rient pin 1 of MSP430 device Jumper J5 Open to measure current Connector J3 External power connector Jumper JP1 to ext Schematics and PCBs Figure B 12 MSP TS430DL48 Target Socket Module PCB SLAU138F June 2004 Revised March 2007 Hardware 49 Submit Documentation Feedback ...

Page 50: ...e 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 50 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 51: ...9 LED connected to pin 12 Jumper J6 Open to disconnect LED Jumper J7 Open to measure current Orient Pin 1 of MSP430 device Schematics and PCBs Figure B 14 MSP TS430PM64 Target Socket Module PCB SLAU138F June 2004 Revised March 2007 Hardware 51 Submit Documentation Feedback ...

Page 52: ...www ti com Schematics and PCBs Figure B 15 MSP TS430PN80 Target Socket Module Schematic 52 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 53: ...e R8 and jumper R9 LED connected to pin 12 Jumper J6 Open to disconnect LED Orient Pin 1 of MSP430 device Schematics and PCBs Figure B 16 MSP TS430PN80 Target Socket Module PCB SLAU138F June 2004 Revised March 2007 Hardware 53 Submit Documentation Feedback ...

Page 54: ... 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 54 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 55: ...9 LED connected to pin 12 Jumper J6 Open to disconnect LED Orient Pin 1 of MSP430 device Jumper J7 Open to measure current Schematics and PCBs Figure B 18 MSP TS430PZ100 Target Socket Module PCB SLAU138F June 2004 Revised March 2007 Hardware 55 Submit Documentation Feedback ...

Page 56: ...www ti com Schematics and PCBs Figure B 19 MSP FET430PIF FET Interface Module Schematic 56 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 57: ...www ti com Schematics and PCBs Figure B 20 MSP FET430PIF FET Interface Module PCB SLAU138F June 2004 Revised March 2007 Hardware 57 Submit Documentation Feedback ...

Page 58: ...www ti com Schematics and PCBs Figure B 21 MSP FET430UIF USB Interface Schematic 1 of 4 58 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 59: ...www ti com Schematics and PCBs Figure B 22 MSP FET430UIF USB Interface Schematic 2 of 4 SLAU138F June 2004 Revised March 2007 Hardware 59 Submit Documentation Feedback ...

Page 60: ...www ti com Schematics and PCBs Figure B 23 MSP FET430UIF USB Interface Schematic 3 of 4 60 Hardware SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 61: ...www ti com Schematics and PCBs Figure B 24 MSP FET430UIF USB Interface Schematic 4 of 4 SLAU138F June 2004 Revised March 2007 Hardware 61 Submit Documentation Feedback ...

Page 62: ...www ti com Schematics and PCBs Figure B 25 MSP FET430UIF USB Interface PCB Hardware 62 SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 63: ...e currently DNP Pullups on TCK and TMS R78 R79 added U2 Changed from SN75LVC1G125DBV to SN75LVC1G07DBV Assembly change on 1 4 January 2006 R62 not populated Note Using a locally powered target board with hardware revision 1 4 Using an MSP FET430UIF interface hardware revision 1 4 with populated R62 in conjunction with a locally powered target board is not possible In this case the target device RE...

Page 64: ...www ti com Hardware 64 SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 65: ...Appendix C SLAU138F June 2004 Revised March 2007 FET Specific Menus Topic Page C 1 Menus 66 SLAU138F June 2004 Revised March 2007 FET Specific Menus 65 Submit Documentation Feedback ...

Page 66: ...ol TEST pin is set to GND when Go is activated Any active on chip breakpoints are retained and the shared JTAG port pins revert to their port functions At this time C SPY has no access to the device and cannot determine if an active breakpoint if any has been reached C SPY must be manually commanded to stop the device at which time the state of the device will be determined i e was a breakpoint re...

Page 67: ...tate Storage dialog box permits one to use the state storage module The State Storage Module is not present on all MSP430 derivatives Refer to Table 2 1 for implementation details See the IAR C SPY FET Debugger section in the MSP430 IAR Embedded Workbench IDE User Guide Open the State Storage window and display the stored state information as configured by the State Storage dialog See the IAR C SP...

Page 68: ...www ti com FET Specific Menus 68 SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 69: ...s where the pin signals of an 80 pin device appear on the pins of an MSP TS430PZ100 target socket module Note The MSP TS430PZ100 must be modified as indicated See Section C 1 8 Emulator Advanced Emulation Mode to enable the emulation mode Topic Page D 1 F4xx 80 Pin Signal Mapping 70 SLAU138F June 2004 Revised March 2007 80 Pin MSP430F44x and MSP430F43x Device Emulation 69 Submit Documentation Feed...

Page 70: ... S2 14 14 14 46 P4 6 S3 15 15 15 47 P4 5 S4 16 16 16 48 P4 4 S5 17 17 17 49 P4 3 S6 18 16 18 50 P4 2 S7 19 19 19 51 P4 1 S8 20 20 20 62 P4 0 S9 21 21 21 63 S10 22 22 S11 23 23 S12 24 24 S13 25 25 S14 26 26 S15 27 27 S16 28 28 S17 29 29 P2 7 ADC12CLK S18 30 30 P2 6 CAOUT S19 31 31 S20 32 32 S21 33 33 S22 34 34 S23 35 35 P3 7 S24 36 36 36 64 P3 6 S25 37 37 37 65 P3 5 S24 38 38 38 66 P3 4 S27 39 39 3...

Page 71: ...Vss2 53 61 P2 5 URXD0 54 74 1 P2 4 UTXD0 55 75 P2 3 TB2 56 76 P2 2 TB1 57 77 P2 1 TB0 58 78 P2 0 TA2 59 79 P1 7 CA1 60 80 P1 6 CA0 61 81 P1 5 TACLK ACLK 62 82 P1 4 TBCLK SMCLK 63 83 P1 3 TBOUTH SVSOUT 64 84 P1 2 TA1 65 85 P1 1 TA0 MCLK 66 86 P1 0 TA0 67 87 XT2OUT 68 88 XT2IN 69 89 TDO TDI 70 90 TDI 71 91 TMS 72 92 TCK 73 93 RST NMI 74 94 P6 0 A0 75 95 P6 1 A1 76 96 P6 2 A2 77 97 Avss 78 98 DVss1 7...

Page 72: ...www ti com 80 Pin MSP430F44x and MSP430F43x Device Emulation 72 SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 73: ...llation 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 Topic Page E 1 Hardware Installation 74 SLAU138F June 2004 Revised March 2007 MSP FET430UIF Installation Guide 73 Submit Documentation Feedback ...

Page 74: ...ardware as an MSP430 USB FET x xx xx see Figure E 1 Figure E 1 WinXP Hardware Recognition 3 The Hardware Wizard starts automatically and opens the Found New Hardware Wizard window 4 Select Install from a list or specific location Advanced see Figure E 2 Figure E 2 WinXP Hardware Wizard 74 MSP FET430UIF Installation Guide SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 75: ...iles 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 The Wizard generates a message that an appropriate driver has been found SLAU138F June 2004 Revised March 2007 MSP FET430UIF Installation Guide 75 Submit Documentation Feedback ...

Page 76: ...tallation of the software for MSP FET430UIF TI USB FET Adapter 10 After closing the Hardware Wizard Windows automatically recognizes another new hardware device called MSP FET430UIF Serial Port 11 Depending on the current update version of the operating system corresponding drivers are installed automatically or the Hardware Wizard opens again If the Wizard starts again repeat the steps described ...

Page 77: ...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 77 Submit Documentation Feedback ...

Page 78: ... MSP FET430U40 schematic and PCB figures with renamed MSP FET430U23x0 images SLAU138F Added FAQ Hardware 2 in Section A 1 Added FAQ Debugging 3 in Section A 3 NOTE Page numbers for previous revisions may differ from page numbers in the current version Revision History 78 SLAU138F June 2004 Revised March 2007 Submit Documentation Feedback ...

Page 79: ... user s responsibility to take any and all appropriate precautions with regard to electrostatic discharge EXCEPT TO THE EXTENT OF THE INDEMNITY SET FORTH ABOVE NEITHER PARTY SHALL BE LIABLE TO THE OTHER FOR ANY INDIRECT SPECIAL INCIDENTAL OR CONSEQUENTIAL DAMAGES TI currently deals with a variety of customers for products and therefore our arrangement with the user is not exclusive TI assumes no l...

Page 80: ...om TI to use such products or services or a warranty or endorsement thereof Use of such information may require a license from a third party under the patents or other intellectual property of the third party or a license from TI under the patents or other intellectual property of TI Reproduction of information in TI data books or data sheets is permissible only if reproduction is without alterati...

Reviews:

No comments

Brands by name

Popular brands

Load more brands