Texas Instruments MSP-FET430 User Manual
  1. Manuals
  2. Brands
  3. Texas Instruments Manuals
  4. Computer Hardware
  5. MSP-FET430
  6. User manual

Texas Instruments MSP-FET430 User Manual

Texas instruments flash emulation tool user's guide
Hide thumbs Also See for MSP-FET430:
Table of Contents

Advertisement

Quick Links

Download this manual
MSP-FET430 FLASH Emulation Tool (FET)
(
For use with IAR Workbench Version 3.x)
U
s e
r ' s
G
2004
u
i d
e
User's Guide
SLAU138A
Mixed Signal
Products

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MSP-FET430 and is the answer not in the manual?

Questions and answers

Related Manuals for Texas Instruments MSP-FET430

Summary of Contents for Texas Instruments MSP-FET430

  • Page 1 MSP-FET430 FLASH Emulation Tool (FET) For use with IAR Workbench Version 3.x) r ' s 2004 User's Guide SLAU138A 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 4 r ' s July 2004...

  • Page 5: Read This First

    About This Manual This manual documents the Texas Instruments MSP-FET430 Flash Emulation Tool (FET). The FET is the program development tool for the MSP430 ultra low power microcontroller. Both available interfaces, the Parallel-Port-Interface and the USB-Interface, are described here. How to Use This Manual Read and follow the Get Started Now! chapter.

  • Page 6: Information About Cautions And Warnings

    The information in a caution or a warning is provided for your protection. Read each caution and warning carefully. Related Documentation From Texas Instruments MSP430xxxx Device Data Sheets MSP430x1xx Family User’s Guide, SLAU049 MSP430x3xx Family User’s Guide, SLAU012...

  • Page 7: If You Need Assistance

    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.

  • Page 9: Table Of Contents

    Read This First ... iii About This Manual ...iii How to Use This Manual ...iii Information About Cautions and Warnings ... iv Related Documentation From Texas Instruments... iv If You Need Assistance ... v FCC Warning ... v Contents ... vii Figures...
  • 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-5 Hardware... B-1 B.1 History of changes to MSP-TS430PM64 Target Socket module ... B-12 FET Specific Menus ... C-1 C.1 EMULATOR... C-2 C.1.1 EMULATOR->RELEASE JTAG ON GO ...
  • Page 11 Figures Figure 3-1. Signal connections for MSP-FET430X110..3-5 Figure 3-2. JTAG Signal Connections ...3-7 Figure A-1. Modification to FET Interface module ... A-7 Figure B-1. MSP-FET430X110, Schematic... B-2 Figure B-2. MSP-FET430X110, PCB Pictorials ... B-3 Figure B-3. MSP-FET430IF FET Interface module, Schematic ... B-4 Figure B-4.

  • Page 13: 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 1.1 Kit Contents, MSP-FET430X110 1.2 Kit Contents, MSP-FET430Pxx0 (‘P120, ‘P140, ‘P410, ‘P430, ‘P440) 1.3 Kit Contents, MSP-FET430UIF 1.4 Software Installation...

  • Page 14: Kit Contents, Msp-Fet430X110

    Get Started Now! 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.

  • Page 15: Kit Contents, Msp-Fet430Uif

    MSP-FET430P430: Eight PCB 1x20 pin headers (Four male and four female). MSP-FET430P440: Eight PCB 1x25 pin headers (Four male and four female). 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...

  • Page 16: Hardware Installation, Msp-Fet430Pxx0 ('P120, 'P140, 'P410, 'P430, 'P440)1-4

    Get Started Now! 1.6 Hardware Installation, MSP-FET430Pxx0 (‘P120, ‘P140, ‘P410, ‘P430, ‘P440) 1) Use the 25-conductor cable to connect the FET Interface module to the parallel port of your PC. 2) Use the 14-conductor cable to connect the FET Interface module to the supplied Target Socket module.
  • Page 17 3) Click on the tab at the bottom of the workspace window that corresponds to your tool (FETxxx) and desired language (assembler or C). 4) Use PROJECT->OPTIONS->FET Debugger->Setup->Connection to select the appropriate port: LPTx for the parallel FET Interface or TI USB FET for the USB Interface.

  • Page 18: Important Msp430 Documents On The Cd-Rom And Web

    Get Started Now! 1.9 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.

  • Page 19: Development Flow

    Development Flow This chapter discusses how to use Kickstart to develop your application software, and how to use C-SPY to debug it. Topic Overview Using Kickstart 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 within the .xcl Files 2.2.5 How to Generate Texas Instrument .TXT (and other format) Files...

  • Page 20: Overview

    Development Flow 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). C- SPY can be configured to operate with the FET (i.e., an actual MSP430 device), or with a software simulation of the device.

  • Page 21: Project Settings

    The simulator will input a maximum of 4K bytes of code. A “Full” (i.e., unrestricted) version of the software tools can be purchased from IAR. A mid-featured tool set – called “Baseline”, with a 12K byte C code size limitation and basic floating-point operations – is also available from IAR. Consult the IAR web site (www.iar.se) for more information.
  • Page 22 Development Flow Enable the Device Description file. This file makes C-SPY “aware” of the specifics of the device it is debugging. This file will correspond to the specified target device (DEBUGGER->SETUP->DEVICE DESCRIPTION- >OVERRIDE DEFAULT) 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...

  • Page 23: Creating A Project From Scratch

    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).

  • Page 24: Using An Existing Iar V1.X/V2.X Project

    Development Flow 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->OPTIONS).

  • Page 25: How To Generate Texas Instrument .Txt (And Other Format) Files

    system stack within C programs. CSTACK can also be used in assembler programs [MOV #SFE(CSTACK), SP]. CSTACK is defined to extend from the last location of RAM for 50 bytes (i.e., the stack extends downwards through RAM for 50 bytes). Other statements in the .xcl file define other relocatable regions that are allocated from the first location of RAM to the bottom of the stack.
  • Page 26 Development Flow Note: Some example programs require a 32KHz crystal on LFXT1, and not all FETs are supplied with a 32KHz crystal.

  • Page 27: Using C-Spy

    2.3 Using C-SPY Refer to 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, refer to Table 2-1 below).

  • Page 28: Using Single Step

    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.

  • Page 29: Using Watch Windows

    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 ;...

  • Page 31: Design Considerations For In-Circuit Programming

    Design Considerations for In-Circuit This chapter presents signal requirements for in-circuit programming of the MSP430. Topic 3.1 Bootstrap Loader 3.2 External Power 3.3 Device Signals 3.4 Signal Connections for In-System Programming and Debugging, MSP-FET430X110 3.5 Signal Connections for In-System Programming and Debugging, MSP-FETP430IF, MSP-FET430UIF Chapter 3 Programming...

  • Page 32: Bootstrap Loader

    Refer to the MSP430 web site for the Application Notes and a list of MSP430 3 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.
  • Page 33 Design Considerations for In-Circuit Programming levels accordingly). Again, refer to the Target Socket module schematic in Appendix B.

  • Page 34: Device Signals

    Design Considerations for In-Circuit Programming 3.3 Device Signals The following device signals should be brought out (i.e., made accessible) so that the FET, GANG430, and PRGS430 tools can be utilized: RST/NMI TEST† Notes: Design considerations to support the FET, GANG430, and PRGS430 1) Connections to XIN and XOUT are not required, and should not be made.

  • Page 35: Signal Connections For In-System Programming And Debugging, Msp- Fet430X110

    Design Considerations for In-Circuit Programming 3.4 Signal Connections for In-System Programming and Debugging, MSP- FET430X110 With the proper connections, you can use the C-SPY debugger and the MSP- FET430X110 to program and debug code on your own target board. In addition, the connections will support the GANG430 and PRGS430, thus providing an easy way to program prototype boards, if desired.

  • Page 36: Figure 3-1. Signal Connections For Msp-Fet430X110

    Design Considerations for In-Circuit Programming Disconnect if target has it's own 'local' power source TDO/TDI Test RST/NMI 14 pos. header (3M p/n 2514-6002) (Digi-Key p/n MHB14K-ND) *** Pulldown not required on all devices. Check device datasheet pin description. Note: Connection to XOUT is not required No JTAG connection is required to the XOUT pin of the MSP430 as shown on some schematics.

  • Page 37: Signal Connections For In-System Programming And Debugging, Msp- Fetp430If, Msp-Fet430Uif

    Design Considerations for In-Circuit Programming 3.5 Signal Connections for In-System Programming and Debugging, MSP- FETP430IF, MSP-FET430UIF With the proper connections, you can use the C-SPY debugger and an FET hardware JTAG interface such as the MSP-FETP430IF and MSP-FET430UIF to program and debug code on your own target board. In addition, the connections will support the GANG430 or PRGS430, thus providing an easy way to program prototype boards, if desired.

  • Page 38: Figure 3-2. Jtag Signal Connections

    Design Considerations for In-Circuit Programming Connect if target has it's own 'local' power source Connect to power target from FET or GANG430 if not using a local power source TDO/TDI CC(FromTool) CC(Local Sense) Test RST/NMI 14 pos. header (3M p/n 2514-6002) (Digi-Key p/n MHB14K-ND) *** Pulldown not required on all devices.

  • Page 39: Frequently Asked Questions

    Frequently Asked Questions This appendix presents solutions to frequently asked questions regarding hardware, program development, and debugging tools. Topic A.1 Hardware A.2 Program Development (Assembler, C-Compiler, Linker) A.3 Debugging (C-SPY) Appendix A Page...

  • Page 40: Hardware

    Frequently Asked Questions A.1 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.

  • Page 41: Program Development (Assembler, C-Compiler, Linker

    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: 20-pin device (DW package): Wells-CTI 652 D020 28-pin device (DW package): Wells-CTI 652 D028 64-pin device (PM package): Yamaichi IC51-0644-807 80-pin device (PN package): Yamaichi IC201-0804-014...
  • 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.

  • Page 43: Debugging (C-Spy

    Optimization: NONE is supported within PROJECT->OPTIONS- >C/C++ COMPILER->CODE->OPTIMIZATIONS. Alternatively, variables can be declared volatile. 16) The IAR Tutorial assumes a Full or Baseline version of the Workbench. Within a Kickstart system, it is not possible to configure the C compiler to output assembler mnemonics. 17) Existing projects from an IAR 1.x system can be used within the new IAR 2.x/3.x system;...
  • Page 44 Frequently Asked Questions 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 complete the installation of the required parallel port drivers. Revisions 1.0, 1.1, and 1.2 of the FET Interface module require a hardware modification;...

  • Page 45: Figure A-1. Modification To Fet Interface Module

    Frequently Asked Questions For revisions 1.0, 1.1, and 1.2 of the FET Interface module, install a 0.1uF capacitor between the indicated points (pins 4 and 5 of U1). 0.1u Figure A-1. Modification to FET Interface module...
  • 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.
  • Page 47 the JTAG pins and the measurements will be erroneous. Refer to FAQ, Debugging #12) and Hardware #11). 11) Most C-SPY settings (breakpoints, etc.) are now preserved between sessions. 12) 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.
  • Page 48 Frequently Asked Questions (RESYNCHRONIZE JTAG)) and before C-SPY has regained control of the device that the device will execute normally. This 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. 19) When programming the Flash, do not set a breakpoint on the instruction immediately following the write to Flash operation.
  • Page 49 26) 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 50 Frequently Asked Questions 35) Special Function Registers (SFRs) – or the peripheral registers – are now displayed in VIEW->REGISTER; there is no longer an SFR Window. 36) 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.
  • Page 51 This appendix contains information relating to the FET hardware, including schematics and PCB pictorials. Topic Figure 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 Figure B-6.

  • Page 52: Hardware

    Hardware Figure B-1. MSP-FET430X110, Schematic...

  • Page 53: Figure B-2. Msp-Fet430X110, Pcb Pictorials

    Ensure value is 82 ohms Jumper J1 Open to measure current P2.1 XOUT P2.5 P2.2 P2.0 Figure B-2. MSP-FET430X110, PCB Pictorials P2.4 P1.1 P2.3 P1.0 Hardware Connector J4 External power connector LED connected to P1.0 Jumper J5 Open to disconnect LED Orient Pin 1 of MSP430 device P1.3...

  • Page 54: Figure B-3. Msp-Fet430If Fet Interface Module, Schematic

    Hardware Figure B-3. MSP-FET430IF FET Interface module, Schematic...

  • Page 55: Figure B-4. Msp-Fet430If Fet Interface Module, Pcb Pictorial

    Hardware Ensure value is 82 ohms Figure B-4. MSP-FET430IF FET Interface module, PCB Pictorial...

  • Page 56: Figure B-5. Msp-Ts430Dw28 Target Socket Module, Schematic

    Hardware 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...

  • Page 57: Figure B-6. Msp-Ts430Dw28 Target Socket Module, Pcb Pictorials

    Jumper J4 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 Pictorials Hardware LED connected to P1.0 Jumper J5 Open to measure current...

  • Page 58: Figure B-7. Msp-Ts430Pm64 Target Socket Module, Schematic, Rev. 1.0

    Hardware Note: Connections between the JTAG header and pins XOUT and XIN are no longer required, and should not be made. Figure B-7. MSP-TS430PM64 Target Socket module, Schematic, Rev. 1.0...

  • Page 59: Figure B-8. Msp-Ts430Pm64 Target Socket Module, Pcb Pictorials, Rev. 1.0

    Jumper J6 Open to disconnect LED Orient Pin 1 of MSP430 device Figure B-8. MSP-TS430PM64 Target Socket module, PCB Pictorials, Rev. 1.0 Hardware Jumper J7 Open to measure current LED connected to pin 12 Connector J5 External power connector Remove R8 and jumper R9...

  • Page 60: Figure B-9. Msp-Ts430Pm64 Target Socket Module, Schematic, Rev. 1.1

    Hardware Note: Connections between the JTAG header and pins XOUT and XIN are no longer required, and should not be made. Figure B-9. MSP-TS430PM64 Target Socket module, Schematic, Rev. 1.1 B-10...

  • Page 61: Figure B-10. Msp-Ts430Pm64 Target Socket Module, Pcb Pictorials, Rev. 1.1

    LED connected to pin 12 Jumper J7 Open to measure current Jumper J6 Open to disconnect LED Orient Pin 1 of MSP430 device Figure B-10. MSP-TS430PM64 Target Socket module, PCB Pictorials, Rev. 1.1 Hardware Connector J5 External power connection Remove R8 and jumper R9 B-11...

  • Page 62: History Of Changes To Msp-Ts430Pm64 Target Socket Module

    Hardware B.1 History of changes to MSP-TS430PM64 Target Socket module Changes from Rev. 0.1 to 1.0: Connector J5 for external power was added Connectors FETJ2 and FETJ3 were removed C8 was changed from 100nF to 10nF R5 was changed from 100k to 47k R13 and R14 were added to support BSL usage on F413.

  • Page 63: Figure B-11. Msp-Tspn80 Target Socket Module, Schematic

    Hardware Figure B-11. MSP-TSPN80 Target Socket module, Schematic B-13...

  • Page 64: Figure B-12. Msp-Tspn80 Target Socket Module, Pcb Pictorials

    Hardware LED connected to pin 12 Jumper J6 Open to disconnect LED Orient Pin 1 of MSP430 device Figure B-12. MSP-TSPN80 Target Socket module, PCB Pictorials B-14 Jumper J7 Open to measure current Connector J5 External power connection Remove R8 and jumper R9...

  • Page 65: Figure B-13. Msp-Tspz100 Target Socket Module, Schematic

    Hardware Note: Connections between the JTAG header and pins XOUT and XIN are no longer required, and should not be made. Figure B-13. MSP-TSPZ100 Target Socket module, Schematic B-15...

  • Page 66: Figure B-14. Msp-Tspz100 Target Socket Module, Pcb Pictorials

    Hardware LED connected to pin 12 Connector J5 External power connection Remove R8 and jumper R9 Orient Pin 1 of MSP430 device Figure B-14. MSP-TSPZ100 Target Socket module, PCB Pictorials B-16 Jumper J6 Open to disconnect LED Jumper J7 Open to measure current...

  • Page 67: Figure B-15. Msp-Fet430Uif Usb Interface Schematics

    Hardware Figure B-15. MSP-FET430UIF USB Interface schematics B-17...
  • Page 68 Hardware B-18...
  • Page 69 Hardware B-19...
  • Page 70 Hardware B-20...
  • Page 71 Hardware B-21...

  • Page 73: Fet Specific Menus

    FET Specific Menus This appendix describes the C-SPY menus that are specific to the FET. Topic EMULATOR C.1.1 EMULATOR->RELEASE JTAG ON GO C.1.2 EMULATOR->RESYNCHRONIZE JTAG C.1.3 EMULATOR->INIT NEW DEVICE C.1.4 EMULATOR->SHOW USED BREAKPOINTS C.1.5 EMULATOR->ADVANCED->GENERAL CLOCK CONTROL C.1.6 EMULATOR->ADVANCED->EMULATION MODE C.1.7 EMULATOR->ADVANCED->MEMORY DUMP C.1.8 EMULATOR->ADVANCED->BREAKPOINT COMBINER C.1.9 EMULATOR->STATE STORAGE...

  • Page 74: Fet Specific Menus

    FET Specific Menus C.1 EMULATOR The current device type is displayed. C.1.1 EMULATOR->RELEASE JTAG ON GO C-SPY uses the device JTAG signals to debug the device. On some MSP430 devices, these JTAG signals are shared with the device port pins. Normally, C- SPY maintains the pins in JTAG mode so that the device can be debugged.

  • Page 75: Emulator->Advanced->Memory Dump

    Refer to Appendix D. C.1.7 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 76: Emulator->Gie On/Off

    FET Specific Menus C.1.14 EMULATOR->GIE on/off Enables or disables all interrupts. Needs to be restored manually before GO. C.1.15 EMULATOR->LEAVE TARGET RUNNING If C-SPY is closed, the target keeps running the user program. C.1.16 EMULATOR->FORCE SINGLE STEPPING On GO the program is executed by single steps. Only in this mode the cycle counter works correctly.

  • Page 77: 80-Pin Msp430F44X And Msp430F43X Device Emulation

    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.

  • Page 78: Table D-1. F4Xx/80-Pin Signal Mapping

    80-pin MSP430F44x and MSP430F43x Device Emulation Table D-1. F4xx/80-pin Signal Mapping F4xx/80-pin Signal 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 P4.6/S3 P4.5/S4 P4.4/S5 P4.3/S6 P4.2/S7 P4.1/S8 P4.0/S9 P2.7/ADC12CLK/S18 P2.6/CAOUT/S19 P3.7/S24 P3.6/S25 P3.5/S24 P3.4/S27 P3.3/UCLK0/S28 P3.2/SOMI0/S29 P3.1/SIMO0/S30 P3.0/STE0/S31...
  • Page 79 80-pin MSP430F44x and MSP430F43x Device Emulation 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 P1.7/CA1 P1.6/CA0 P1.5/TACLK/ACLK P1.4/TBCLK/SMCLK P1.3/TBOUTH/SVSOUT P1.2/TA1 P1.1/TA0/MCLK P1.0/TA0 XT2OUT XT2IN TDO/TDI RST/NMI P6.0/A0 P6.1/A1 P6.2/A2 Avss DVss1 Avcc † Note discontinuity of pin numbering sequence 74†...

  • Page 81: Ti To Iar 2.X/3.X Assembler Migration

    TI to IAR 2.x/3.x Assembler Migration Texas Instruments made a suite of development tools for the MSP430, including a comprehensive assembler and device simulator. The source of the TI assembler and the source of the Kickstart assembler are not 100% compatible;...

  • Page 82: Ti To Iar 2.X/3.X Assembler Migration

    For detailed descriptions of each directive, refer to either the MSP430 Assembly Language Tools User’s Guide, SLAUE12, from Texas Instruments, or the MSP430 Assembler User’s Guide from IAR. Note: Only the assembler directives require conversion Only the assembler directives require conversion - not the assembler instructions.

  • Page 83: Section Control Directives

    consecutive backslashes (\\). In Asm430 syntax, a quote is represented by two consecutive quotes (“”). See examples below: Character String PLAN “C” \dos\command.com Concatenated string (i.e. Error 41) E.2.3 Section Control Directives Asm430 has three predefined sections into which various parts of a program are assembled.

  • Page 84: Constant Initialization Directives

    TI to IAR 2.x/3.x Assembler Migration E.2.4 Constant Initialization Directives Description Initialize one or more successive bytes or text strings Initialize a 48-bit MSP430 floating-point constant Initialize a variable-length field Initialize a 32-bit MSP430 floating-point constant Reserve size bytes in the current section Initialize one or more text strings Initialize one or more 16-bit integers The 48-bit MSP430 format is not supported...

  • Page 85: File Reference Directives

    E.2.6 File Reference Directives Description Include source statements from another file Identify one or more symbols that are defined in the current module and used in other modules Identify one or more global (external) symbols Define a macro library Identify one or more symbols that are used in the current module but defined in another module The directive .global functions as either .def if the symbol is defined in the current module, or .ref...

  • Page 86: Symbol Control Directives

    TI to IAR 2.x/3.x Assembler Migration ENDR ENDM Additional A430 Directives (IAR) Repeatable block assembly: Formal argument is substituted by each character of a string. Repeatable block assembly: formal argument is substituted by each string of a list of actual arguments. See also Preprocessor Directives E.2.8 Symbol Control Directives...

  • Page 87: Macro Directives

    E.2.9 Macro Directives Description Define a macro Exit prematurely from a macro End macro definition Additional A430 Directives (IAR) Create symbol, local to a macro In Asm430 local symbols are suffixed by a question mark (?). E.2.10 Miscellaneous Directives Description Send user-defined error messages to the output device Send user-defined messages to the output...

  • Page 88: Alphabetical Listing And Cross Reference Of Asm430 Directives

    TI to IAR 2.x/3.x Assembler Migration Additional A430 Directives (IAR) Assign a value to a preprocessor symbol Undefine a preprocessor symbol Conditional assembly Assemble if a preprocessor symbol is defined (not defined) End a #if, #ifdef or #ifndef block Includes a file Generate an error E.2.12 Alphabetical Listing and Cross Reference of Asm430 Directives...
  • Page 89 LSTPAG (+/-) LSTXREF (+/-) TI to IAR 2.x/3.x Assembler Migration #if, #else, #elif #ifdef, #ifndef #endif #include #error COMMON STACK ALIGN...

  • Page 91: Msp-Fet430Uif Installation Guide

    Appendix F 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 F.1 Hardware Installation...

  • Page 92: Hardware Installation

    MSP-FET430UIF Installation Guide F.1 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 F-1). Figure F-1.

  • Page 93: Figure F-3. Winxp Driver Location Selection Folder

    Figure F-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 F-4).

  • Page 94: Figure F-4. Winxp Driver Installation

    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.

  • Page 95: Figure F-5. Device Manager

    MSP-FET430UIF Installation Guide Figure F-5. Device Manager...

Table of Contents