Automotive mixed-signal microcontrollers with can-fd interface (88 pages)
Summary of Contents for Texas Instruments MSP-FET430
Page 1
MSP-FET430 FLASH Emulation Tool (FET) For use with IAR Workbench Version 3.x) User's Guide October 2006 SLAU138 Mixed Signal Products...
Page 2
IMPORTANT NOTICE Texas Instruments and its subsidiaries (TI) reserve the right to make changes to their products or to discontinue any product or service without notice, and advise customers to obtain the latest version of relevant information to verify, before placing orders, that information being relied on is current and complete.
Page 3
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.
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 ultra low power microcontroller. Both available interfaces, the Parallel-Port- Interface and the USB-Interface, are described here.
The following tools contain the USB debug interface (MSP-FET430UIF) and the respective target-socket module: MSP-FET430U14 (for MSP430 devices in 14 pin PW-Packages) MSP-FET430U28 (for MSP430 devices in 20 and 28 pin DW-Packages) MSP-FET430U38 (for MSP430 devices in 38 pin DA-Packages) MSP-FET430U40 (for MSP430F2330/F2350/F2370 devices in 40 pin RHA- Packages only) MSP-FET430U48 (for MSP430 devices in 48 pin DL-Package)
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 provided with Kickstart before requesting assistance.
Creating a Project from Scratch .................2-5 2.2.3 Using an Existing IAR V1.x/V2.x Project............2-6 2.2.4 Stack Management and .xcl Files ..............2-6 2.2.5 How to Generate Texas Instruments .TXT (and other format) Files....2-7 2.2.6 Overview of Example Programs.................2-7 2.3 Using C-SPY .....................2-8 2.3.1 Breakpoint Types ....................2-8 2.3.2...
Page 10
Frequently Asked Questions ..................A-1 A.1 Hardware......................A-2 A.2 Program Development (Assembler, C-Compiler, Linker) ......... A-3 A.3 Debugging (C-SPY)..................A-6 Hardware......................... B-1 FET Specific Menus ....................... C-1 C.1 Menus....................... C-2 C.1.1 EMULATOR--> DEVICE INFORMATION ............C-2 C.1.2 EMULATOR--> RELEASE JTAG ON GO............C-2 C.1.3 EMULATOR-->...
Page 11
Figures Figure 3-1. Signal Connections for 4-Wire JTAG Communication......3-3 Figure 3-2. Signal Connections for 2-Wire JTAG Communication (Spy-Bi-Wire) ..3-4 Figure B-1. MSP-FET430X110, Schematic ..............B-2 Figure B-2. MSP-FET430X110, PCB Pictorials ............B-3 Figure B-3. MSP-TS430PW14 Target Socket module, Schematic ......B-4 Figure B-4.
Chapter 1 Get Started Now! This chapter will enable you to inventory your FET, and then it will instruct you to install the software and hardware, and then run the demonstration programs. Topic Page 1.1 Kit Contents, MSP-FET430X110 1.2 Kit Contents, MSP-FET430PIF 1.3 Kit Contents, MSP-FET430Pxx0 (‘P120, ‘P140, ‘P410, ‘P430, ‘P440) 1.4 Kit Contents, MSP-FET430UIF...
1.1 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. One small box containing two MSP430F1121AIDW device samples.
MSP-FET430P440: One MSP-TS430PZ100 Target Socket module. This is the PCB on which is mounted a 100-pin ZIF socket for the MSP430F43xIPZ or MSP430F44xIPZ device. A 2x7 pin male connector is also present on the PCB. One 25-conductor cable. One 14-conductor cable. MSP-FET430P120: Four PCB 1x14 pin headers (Two male and two female).
1.5 Kit Contents, MSP-FET430Uxx (‘U14, ‘U28, ‘U38, ‘U40, ‘U48, ‘U64, ‘U80, ‘U100) One READ ME FIRST document. One MSP430 CD-ROM. One MSP-FETP430UIF USB-Interface module. This is the unit that has a USB B-connector on one end of the case, and a 2x7 pin male connector on the other end of the case.
MSP-FET430U28: Four PCB 1x14 pin headers (Two male and two female). MSP-FET430U38: Four PCB 1x19 pin headers (Two male and two female). MSP-FET430U40: Eight PCB 1x10 pin headers (Four male and four female). MSP-FET430U48: Four PCB 2x24 pin headers (Two male and two female).
1.7 Hardware Installation, MSP-FET430X110 1) Connect the 25-conductor cable originating from the FET 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.
1.10 Hardware Installation, MSP-FET430Uxx (‘U14, ‘U28, ‘U38, ‘U40, ‘U48, ‘U64, ‘U80, ‘U100), MSP-FET430Pxx0 (‘P120, ‘P140, ‘P410, ‘P430, ‘P440) 1) Connect the MSP-FET430PIF or MSP-FET430UIF debug interface to the appropriate port of your PC. Use the 14-conductor cable to connect the FET Interface module to the supplied Target Socket module.
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 available at the time of production have been provided on the CD-ROM included with this tool.
2.2.1 Project Settings 2.2.2 Creating a Project from Scratch 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...
2.1 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).
2.2.1 Project 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;...
Page 24
Enable the erasure of the Main and Information memories before object code download (FET DEBUGGER--> SETUP--> DOWNLOAD CONTROL--> ERASE MAIN AND INFORMATION MEMORY) In order to maximize system performance during debug, disable Virtual Breakpoints (FET DEBUGGER--> SETUP --> USE VIRTUAL BREAKPOINTS), and disable all System Breakpoints (FET DEBUGGER-->...
Note: Avoid the use of absolute pathnames when referencing files. Instead, use the relative pathname keywords $TOOLKIT_DIR$ and $PROJ_DIR$. Refer to the IAR documentation for a description of these keywords. The use of relative pathnames will permit projects to be moved easily, and projects will not require modification when IAR systems are upgraded (say, from Kickstart, or Baseline, to Full).
Note: How to add assembler source files to your project The default file type presented in the Add Files window is “C/C++ Files”. In order to view assembler files (.s43), select “Assembler Files” in the “Files of type” drop-down menu. 8) Configure the project options (PROJECT-->...
(say, 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. Select: PROJECT-->...
<Installation Root>\Embedded Workbench x.x\430\FET_examples\contents.htm conveniently organizes and documents the examples. Additional code examples can be found on the MSP430 home page under Design Resources. Note: Some example programs require a 32-kHz crystal on LFXT1, and not all FETs are supplied with a 32-kHz crystal. 2.3 Using C-SPY Refer to Appendix C for a description of FET-specific menus within C- SPY.
2.3.3 Using 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...
2.3.4 Using Watch Windows The C-SPY Watch Window mechanism permits C variables to be monitored during the debugging session. Although not originally designed to do so, the Watch Window mechanism can be extended to monitor assembler variables. Assume that the variables to watch are defined in RAM, say: RSEG DATA16_I varword ds 2 ;...
Chapter 3 Design Considerations for In-Circuit Programming This chapter presents signal requirements 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 3.2 External Power 3.3 Bootstrap Loader...
3.1 Signal Connections for In-System Programming and Debugging, MSP- FET430PIF, MSP-FET430UIF, GANG430, PRGS430 With the proper connections, you can use the C-SPY debugger and an FET hardware JTAG interface such as the MSP-FET430PIF and MSP- FET430UIF to program and debug code on your own target board. In addition, the connections will also support the GANG430 or PRGS430 production programmers, thus providing an easy way to program prototype boards, if desired.
J1† / AV / DV J2† 10μF 0.1μF R1‡ MSP430Fxxx 47kΩ JTAG RST/NMI VCC TOOL TDO/TDI TDO/TDI VCC TARGET TDI/VPP TDI/VPP TEST/VPP RST¶ TEST/VPP§ C1‡ / AV / DV 10nF/2.2nF# Figure 3-1. Signal Connections for 4-Wire JTAG Communication † Make either connection J1 in case a local target power supply is used OR connection J2 to power target from the debug/programming adapter.
Figure 3-2. Signal Connections for 2-Wire JTAG Communication (Spy-Bi-Wire) † Make either connection J1 in case a local target power supply is used OR connection J2 to power target from the debug/programming adapter. ‡ Note that the device RST/NMI/SBWTDIO pin is used in 2-wire mode for bi-directional communication with the device during JTAG access and that any capacitance attached to this signal may affect the ability to establish a connection with the device.
Refer to the MSP430 web site for the Application Notes and a list of MSP430 3 party tool developers. Texas Instruments suggests that MSP430Fxxx customers design their circuits with the BSL in mind (i.e., we suggest providing access to these signals, e.g. via a header).
Appendix A Frequently Asked Questions This appendix presents solutions to frequently asked questions regarding hardware, program development, and debugging tools. Topic Page A.1 Hardware A.2 Program Development (Assembler, C-Compiler, Linker) A.3 Debugging (C-SPY)
Hardware 1) The state of the device (CPU registers, RAM memory, etc.) is undefined following a reset. Exceptions to the above statement are that the PC is loaded with the word at 0xfffe (i.e., the reset vector), the status register is cleared, and the peripheral registers (SFRs) are initialized as documented in the device Family User’s Guides.
11) The device current increases by approximately 10uA when a device in low power mode is stopped (using ESC), and then the low power mode is restored (using GO). This behavior appears to happen on all devices except the MSP430F12x. 12) The following ZIF sockets are used in the FET tools and Target Socket modules: 14-pin device (PW package): ENPLAS OTS-14-065-01...
Page 42
Workbench. Refer to the Assembler Language Interface chapter of the C/C++ Compiler Reference Guide from IAR. 10) The Workbench can produce an object file in Texas Instruments .TXT format. C-SPY cannot input an object file in Texas Instruments .TXT format. An error message will be output in this case.
Page 43
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.
Debugging (C-SPY) 1) Debugging with C-SPY does not seem to affect an externally connected MSP430 device. Should this be the case, check whether the main debugger menu bar contains a menu item called SIMULATOR. If so, an actual C-SPY MSP430 core simulator session is running, and no actual communication with the target device is established.
Page 45
4) C-SPY can debug applications that utilize interrupts and low power modes. Refer to FAQ, Debugging #25). 5) 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.
Page 46
13) When C-SPY has control of the device, the CPU is ON (i.e., it is not in low power mode) regardless of the settings of the low power mode bits in the status register. Any low power mode conditions will be restored prior to STEP or GO.
Page 47
behavior may have side effects. Once C-SPY has regained control of the device, it will perform a reset of the device and retain control. 20) When programming the Flash, do not set a breakpoint on the instruction immediately following the write to Flash operation. A simple work-around to this limitation is to follow the write to Flash operation with a NOP, and set a breakpoint on the instruction following the NOP.
Page 48
27) On devices equipped with a Data Transfer Controller (DTC), the completion of a data transfer cycle will preempt a single step of a low power mode instruction. The device will advance beyond the low power mode instruction only after an interrupt is processed. Until an interrupt is processed, it will appear that the single step has no effect.
Page 49
ignored when using the FET and the FLASH-based MSP430F device. 36) Special Function Registers (SFRs) and the peripheral registers are displayed in VIEW--> REGISTER. 37) The putchar()/getchar() breakpoints are set only if these functions are present (and the mechanism is enabled). Note that putchar()/getchar() could be indirectly referenced by a library function.
Connector J4 External power connector LED connected to P1.0 Jumper J5 Open to disconnect LED Orient Pin 1 of MSP430 Ensure value is 82 ohms device Jumper J1 Open to measure current P2.1 XOUT P2.5 P2.4 P1.1 P1.3 P1.5 P1.7 P2.2 P2.0 P2.3...
Connector J3 External power connector Jumper J5 to ‘ext’ LED connected to P1.0 Jumpers J7-J12 Close 1-2 to debug in SpyBiWire-Mode, or Jumper J4 close 2-3 to debug in Open to disconnect LED 4Wire JTAG mode Jumper J6 Orient Pin 1 of MSP430 Open to measure current device Figure B-4.
Note: Connections between the JTAG header and pins XOUT and XIN are no longer required, and should not be made. Figure B-5. MSP-TS430DW28 Target Socket module, Schematic...
LED connected to P1.0 Jumper J4 Jumper J5 Open to disconnect LED Open to measure current 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 Pictorials...
Jumpers JP4-JP9 Close 1-2 to debug in SpyBiWire-Mode, or LED connected close 2-3 to debug in to P1.0 4Wire JTAG mode Jumper JP3 Open to disconnect Orient pin 1 of MSP430 device Jumper JP2 Open to measure current Connector J3 External power connector Jumper JP1 to ‘ext’...
Connector J5 Jumper JP2 External power Open to measure connector current Jumper JP1 to ‘ext’ Jumper JP3 Open to disconnect LED connected to P1.0 Figure B-10. MSP-TS430QFN40 Target Socket module, PCB Pictorials B-11...
Jumper J5 Open to measure current LED connected to Connector J3 P1.0 P1.0 External power connector Jumper JP1 to Jumper J4 ‘ext’ Open to disconnect Orient pin 1 of MSP430 device Figure B-12. MSP-TS430DL48 Target Socket module, PCB B-13...
Note: Connections between the JTAG header and pins XOUT and XIN are no longer required, and should not be made. Figure B-13. MSP-TS430PM64 Target Socket module, Schematic B-14...
LED connected to pin 12 Connector J5 External power connection Jumper J7 Remove R8 and jumper R9 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 Pictorials B-15...
LED connected to pin 12 Connector J5 External power connection Jumper J6 Remove R8 and jumper R9 Open to disconnect LED Orient Pin 1 of MSP430 device Figure B-16. MSP-TS430PN80 Target Socket module, PCB Pictorials B-17...
Note: Connections between the JTAG header and pins XOUT and XIN are no longer required, and should not be made. Figure B-17. MSP-TS430PZ100 Target Socket module, Schematic B-18...
Jumper J6 Jumper J7 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 Pictorials B-19...
Figure B-22. MSP-FET430UIF USB Interface, PCB Pictorial B-26...
Page 77
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 --> 1.4 (Aug 2005) J5: VBUS and RESET additionally connected R29, R51, R42, R21, R22, R74: value changed from 330R to 100R U1, U7: F1612 can reset TUSB3410;...
Appendix C FET Specific Menus This appendix describes the C-SPY menus that are specific to the FET. Topic Page 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 C.1.6 EMULATOR-->...
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.
C.1.5 EMULATOR--> SECURE Blows the fuse on the target device. After the fuse is blown, no communication with the device is possible. C.1.6 EMULATOR--> SHOW USED BREAKPOINTS List all used hardware and virtual breakpoints, as well as all currently defined EEM breakpoints. C.1.7 EMULATOR-->...
C.1.12 EMULATOR--> STATE STORAGE WINDOW Open the State Storage window, and display the stored state information as configured by the State Storage dialog. Refer to the IAR C-SPY FET Debugger section in the MSP430 IAR Embedded Workbench IDE User Guide. C.1.13 EMULATOR-->...
Appendix D 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. F4xx/80-pin Signal Mapping lists where the pin signals of an 80-pin device appear on the pins of an MSP-TS430PZ100 Target Socket module.
Appendix E 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. Topic Page E.1 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” (Figure E-1). Figure E-1. WinXP Hardware Recognition 3) The Hardware Wizard should start automatically and popup the “Found New Hardware Wizard”...
Figure E-3. WinXP Driver Location Selection Folder 6) The Wizard should generate a message that an appropriate driver has been found. 7) Note that WinXP shows a warning that the driver is not certified by Microsoft. Ignore this warning and click “Continue Anyway” (Figure E-4).
9) The Wizard now shows a message that it has finished the installation of the software for “MSP430 USB FET Adapter”. 10) After closing the Hardware Wizard, Windows automatically recognizes another new hardware device called “Texas Instruments UMP Serial Port”. 11) Depending on the current update version of the OS corresponding drivers are installed automatically or the Hardware Wizard pops up again.
Need help?
Do you have a question about the MSP-FET430 and is the answer not in the manual?
Questions and answers