Texas Instruments MSP430 Series User Manual
  1. Manuals
  2. Brands
  3. Texas Instruments Manuals
  4. Microcontrollers
  5. MSP430 series
  6. User manual
Texas Instruments MSP430 Series User Manual

Texas Instruments MSP430 Series User Manual

Serial programming adapter manual
Hide thumbs Also See for MSP430 Series:
Table of Contents

Advertisement

Quick Links

Download this manual
微控设计网 http://www.Microcontrol.cn
微控技术论坛 http://bbs.Microcontrol.cn
主题:基于模拟前端信号处理与控制技术的专业论坛,网站.
基于模拟前端信号处理与控制技术的专业论坛、网站.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MSP430 Series and is the answer not in the manual?

Questions and answers

Related Manuals for Texas Instruments MSP430 Series

Summary of Contents for Texas Instruments MSP430 Series

  • Page 1 微控设计网 http://www.Microcontrol.cn 微控技术论坛 http://bbs.Microcontrol.cn 主题:基于模拟前端信号处理与控制技术的专业论坛,网站. 基于模拟前端信号处理与控制技术的专业论坛、网站.
  • Page 2 MSP430 Family Serial Programming Adapter Manual User’s Guide January 2003 Mixed Signal Products SLAU048C...
  • Page 3 IMPORTANT NOTICE Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements, improvements, and other changes to its products and services at any time and to discontinue any product or service without notice. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete.
  • Page 4 EVM IMPORTANT NOTICE Texas Instruments (TI) provides the enclosed product(s) under the following conditions: This evaluation kit being sold by TI is intended for use for ENGINEERING DEVELOPMENT OR EVALUATION PURPOSES ONLY and is not considered by TI to be fit for commercial use. As such, the goods being provided may not be complete in terms of required design-, marketing-, and/or manufacturing-related protective considerations, including product safety measures typically found in the end product incorporating the goods.
  • Page 5 EVM schematic located in the EVM User’s Guide. When placing measurement probes near these devices during operation, please be aware that these devices may be very warm to the touch. Mailing Address: Texas Instruments Post Office Box 655303 Dallas, Texas 75265 Copyright  2003, Texas Instruments Incorporated...
  • Page 6 Trademarks Preface Read This First About This Manual This document describes the MSP430-family hardware, operation, and software installation and setup. How to Use This Manual This document contains the following chapters: Chapter 1 – Installation and Setup Chapter 2 – Operation Chapter 3 –...

  • Page 8: Table Of Contents

    Running Title—Attribute Reference Contents Installation and Setup ............Installing the Software .
  • Page 9 Running Title—Attribute Reference Figures 1–1 ADT430 Program Icons ............1–2 Serial Programming Adapter .
  • Page 10 Running Title—Attribute Reference Tables 2–1 MSP430 Function Buttons and Descriptions ........2–2 Error Messages .

  • Page 12: Installation And Setup

    Chapter 1 Installation and Setup This chapter describes the process of installing and programming the hardware and software for the MSP430-PRGS430 programming adapter used with the MSP430 family of microcontrollers. Topic Page Installing the Software ......... Installing the Hardware .

  • Page 13: Installing The Software

    Installing the Software 1.1 Installing the Software To install the MSP-PRGS430 software, perform the following steps: 1) Insert the MSP-PRGS430 CD-ROM in the computer’s CD drive. It should start automatically. A setup routine checks if you have an HTML browser installed on your computer.

  • Page 14: Installing The Hardware

    Installing the Hardware 1.2 Installing the Hardware To install the programming adapter hardware, perform the following steps: 1) Using the 9-pin SUB-D connector, connect the programming adapter to the serial port (COM1–COM4) of the PC. 2) Connect an external power supply to the programming adapter. The voltage of the power supply must be between 14 V and 20 V dc and must provide a minimum of 200 mA of power.

  • Page 16: Operation

    Chapter 2 Operation This chapter describes the programming procedure for MSP430 devices and the error messages you may encounter during the procedure. Topic Page Software/Hardware Layers of the PRGS430 Environment ..Programming the MSP430 Devices With the GUI .

  • Page 17: Software / Hardware Layers Of The Prgs430 Environment

    Software / Hardware Layers of the PRGS430 Environment 2.1 Software / Hardware Layers of the PRGS430 Environment PC – Software PRGS430.EXE PRGS430.INI CommandLine Function DEVICE.CFG PRGS430.DLL [Project] .INI RS232 Serial Programming Adapter PRGS430 JTAG Target Socket or Application MSP430 There are three ways to handle and communicate with the PRGS430 hard- ware: Using the graphical user interface (see Section 2.2) Using command line parameters (see Section 2.3)

  • Page 18: Programming The Msp430 Devices With The Gui

    Programming the MSP430 Devices With the GUI 2.2 Programming the MSP430 Devices With the GUI 2.2.1 Basic Procedure The following steps should be used to program the MSP430 devices: 1) Click on the Program Device icon during the installation selected program group (default: ADT430).

  • Page 19: Description Of The Msp-Prgs430 Gui

    Programming the MSP430 Devices With the GUI 2.2.2 Description of the MSP-PRGS430 GUI An MSP430 device is commonly programmed as follows: 1) Select the file that contains the data to program from the MSP430 programmer dialog box (see Figure 2–1). 2) Select the device.

  • Page 20: Error Messages

    Programming the MSP430 Devices With the GUI Table 2–1. MSP430 Function Buttons and Descriptions (Continued) Button Name Sub-Functions Description Verify Verify the data in the MSP430 device according to the selected option A verification of the memory locations vs. the selected object file is By file performed.

  • Page 21: Communication Error Box

    Programming the MSP430 Devices With the GUI The problem could be that the PRGS430 is not connected to the hardware, the device is not inserted or is incorrectly inserted into the socket, or the device is not powered. Figure 2–2. Communication Error Box If the fuse is already blown, the error message shown in Figure 2–3 appears.

  • Page 22: Error Messages

    Programming the MSP430 Devices With the GUI Table 2–2. Error Messages Error Type Error Message Communication Communication failed! Communication Adapter not connected! Communication Synchronization with adapter failed! Communication The present adapter is not an MSP-PRGS430! Communication Missing setting of V MSP430 Target not connected! MSP430...

  • Page 23: Content Of The Prgs430.Ini File

    Content of the PRGS430.ini File 2.2.4 Content of the PRGS430.ini File The last settings of the PRGS430 graphical user interface (GUI) is stored in the .ini file before exiting the program. This information is stored under the Program Device System section. Additionally, the following parameters are in the [Options] section and may be modified: [Options]...

  • Page 24: Command Line Options

    Command Line Options 2.3 Command Line Options 2.3.1 General Definitions 0: Off 1: First selectable option 1: On 2: Second selectable option 3: Third selectable option The PRGS430.ini file options are used if they are not specified in the command line.
  • Page 25 Command Line Options Table 2–3. Command Line Options (Continued) Options for Program Command: /PE:{0,1,2} Option program with erase (flash only) Without erase Main and Info memory Main memory only /PC:{0,1} Option program with erase check Disable Enable /PV:{0,1} Option program with verify Disable Enable /PB:{0,1}...

  • Page 26: Return Values / Error Codes In The .Ini File

    2.3.2 Return Values / Error Codes in the .ini File The error code will be returned to the PC operating system and is also stored in PRGS430.ini File in the [Options] section: LastResult=0 Communication failed! Target not connected! Adapter not connected! Wrong JTAG version! PUC failed! Synchronization with adapter failed!

  • Page 27: Prgs430.Dll-Description

    PRGS430.DLL—Description 2.4 PRGS430.DLL—Description The PRGS430.dll is used to communicate with the MSP–PRGS430 hardware and the connected MSP430 device. The initialization of the PRGS430 should be done with the following sequence: InitCom SetDeviceType SetV . InitTarget ..ReleaseTarget ReleaseCom Several examples showing how the DLL could be used are located in the “DLL_Usage_Examples’...
  • Page 28 PRGS430.DLL—Description Example: lFuncReturn = SetDeviceType(”MSP430F1121”) /FN0004/ InitTarget long int InitTarget(char* lpszDeviceName ) Initializes the JTAG access to the target device, detects the device type, and reports when the detected device does not match the parameter DeviceName passed. lpszDeviceName: name of the device in file device.cfg. Example: lFuncReturn = InitTarget (”MSP430F1121”) /FN0005/ ReleaseTarget long int ReleaseTarget(void)
  • Page 29 PRGS430.DLL—Description /FN0007/ EraseFile long int EraseFile(char* lpszFileName, long int iFileType, long int Flags, char* lpszProjectIni) EraseFile() erases all addresses used in the specified file. iFileType: FILETYPE_AUTO (0x00) – Autodetection of file type (Intel-hex or TI-text) FILETYPE_TI_TXT (0x01) – File type is TI-txt FILETYPE_INTEL_HEX(0x02) –...
  • Page 30 PRGS430.DLL—Description lpszFilName: Name of the file iFileType: FILETYPE_AUTO (0x00) – autodetection of file type (Intel-hex or TI-text) FILETYPE_TI_TXT (0x01) – file type is TI-txt FILETYPE_INTEL_HEX(0x02) – file type is Intel-hex Function returns success or first address with mismatching data Example: lFuncReturn = EraseCheckFile(”test.txt”, long:0) /FN00010/ PatternCheck long int PatternCheck(long int wStart, long int wLength, long int wPattern)
  • Page 31 PRGS430.DLL—Description This function checks if the memory contents of the target device are equal to the file contents. lpszFileName: Name of the file iFileType FILETYPE_AUTO (0x00) – autodetection of file type (Intel-hex or TI-text) FILETYPE_TI_TXT (0x01) – file type is TI-txt FILETYPE_INTEL_HEX(0x02) –...
  • Page 32 PRGS430.DLL—Description wLength: Length of the range Allowed values : 0x0000 – 0xFFFE (see memory map of the corresponding device) lpData: Pointer to the Data to be programmed Flags: The bits in Flags control the operation of ProgramData(). Example: lFuncReturn = ProgramData(long:0xF000, long:0x1000, void* lpData) /FN0015/ ProgramFile long int ProgramFile(char* lpszFileName, long int iFileType,...
  • Page 33 PRGS430.DLL—Description lpszProjectIni Name of the {project}.ini file, if protection settings from this file are used. If no protection is required, replace lpszProjectIni by NULL. The added features do not need to be used—for ProgramFile according to older specification just call ProgramFile(FileName, FileType, 0, NULL); if no {project}.ini file or erase check should be used, just call: Example: lFuncReturn = ProgramFile(FileName, 0, 0, NULL);...
  • Page 34 PRGS430.DLL—Description /FN0019/ ReadOutFile long int ReadOutFile(long int wStart, long int wLength, char* lpszFileName, long int iFileType) Read-out data from the device and writes it to a file. wStart: Start address of the area to be read out. Allowed values : 0x0000 – 0xFFFE (see memory map of the corresponding device).
  • Page 35 PRGS430.DLL—Description The following status codes are defined: Status WParam Current Operation STATUS_CONNECTSPA Connecting to SPA430 STATUS_CONNECTTARGET Connecting to target STATUS_RELEASETARGET Releasing target STATUS_RELEASESPA Releasing SPA430 STATUS_RESETTARGET Resetting target STATUS_ERASE Erasing target STATUS_ERASECHECK Erase checking target STATUS_PATTERNCHECK Pattern checking target STATUS_VERIFY Verifying target STATUS_PROGRAM Programming target...
  • Page 36 PRGS430.DLL—Description DEVICE_VPP (0x0B) GetDeviceCfgInfo() returns the Vpp setting for selected device in mV; lpBuf and InfoIdx are ignored. DEVICE_VFUSE (0x0C) GetDeviceCfgInfo() returns the blow-fuse setting for the selected device; lpBuf and InfoIdx are ignored. /FN0024/ AccessSFR long int AccessSFR(LONG wAddr, void *IpData, LONG iFlags); This function writes or reads data into the special function registers of the MSP430 device.

  • Page 37: Return Values / Error Codes From The Prgs430.Dll

    PRGS430.DLL—Description 2.4.1 Return Values / Error Codes From the PRGS430.DLL Status Return Value Comment SUCCESS –1 Operation ok ERR_COMMUNICATION –2 Communication error (SSP) ERR_TARGET_NOT_CONNECTED –3 No target connected ERR_SPA430_NOT_CONNECTED –4 No SPA430 connected ERR_WRONG_JTAG_VERSION –5 JTAG version above 3 ERR_PUC_FAILED –6 PUC did not succeed ERR_SPA430_SYNC_FAILED...

  • Page 38: Hardware

    Chapter 3 Hardware This chapter describes the hardware for the MSP430 family of micro- controllers, including specifications, components of the programming adapters, and connection of the programming adapter to the MSP430 device families. Topic Page Specifications ..........Basic Hints .

  • Page 39: Specifications

    Specifications 3.1 Specifications The specifications for the MSP430 hardware are shown in Table 3–1. Table 3–1. MSP430 Hardware Specifications Temperature range 10°C–45°C Humidity 40%–70% Power supply 14 V–20 V, 200 mA minimum 150 mm (W) × 30 mm (H) × 95 mm (D) Dimensions 3.2 Basic Hints These basic hints are useful for programming MSP430 devices or MSP430...

  • Page 40: Programming Adapter Target Connector Signals

    Programming Adapter Target Connector Signals 3.3 Programming Adapter Target Connector Signals The target connector signals for the programming adapter ensure communication between programming adapter and MSP430 devices and supply low energy to systems without extra supply sources. Figure 3–1 and Figure 3–2 show the target connector signals for the programming adapter.

  • Page 41: Target Connector Signal Functions

    Programming Adapter Target Connector Signals Table 3–2. Target Connector Signal Functions Signal/Terminal Name Required Function/Comment Mandatory Test mode select functions according to IEE1149.1. Mandatory Test clock functions according to IEE1149.1. TDI/VPP Mandatory Test data input functions according to IEE1149.1, but with additional programming voltage for 3xx devices.

  • Page 42: Msp-Prgs430 Circuit Diagrams

    MSP-PRGS430 Circuit Diagrams 3.4 MSP-PRGS430 Circuit Diagrams The MSP-PRGS430 circuit diagrams are found in Appendix B. 3.5 Location of Components, MSP-PRGS430 Figure 3–3. MSP-PRGS430 Components MSP430P337 Note: Do not use J2 pin 9 as RST/NMI pullup. Hardware...

  • Page 43: Interconnection Of Msp-Prgs430 To Msp430X31X

    Interconnection of MSP-PRGS430 to MSP430x31x 3.6 Interconnection of MSP-PRGS430 to MSP430x31x The circuit diagrams in Figure 3–4 through Figure 3–6 show the connections required to program the MSP430x31x device with programming adapter MSP-PRGS430. Figure 3–4. MSP-PRGS430 Used to Program the MSP430x31xIDL Device MSP430P313IDL MSP430P315IDL Xout...

  • Page 44: Msp-Prgs430 Used To Program The Msp430X31Xsidl Device

    Interconnection of MSP-PRGS430 to MSP430x31x Figure 3–5. MSP-PRGS430 Used to Program the MSP430x31xSIDL Device MSP430P315SIDL Xout 10 µF 100 nF – ~100k RST/NMI Connector, male, for Socket for DL–Package, 48SSOP TI’s programming adapter ~68 kΩ e.g. Yamaichi, Order–# IC51–1387.KS–15186 e.g. 3M, Order–# 2514–6002 for OTP/EPROM devices (P/E) The RST/NMI terminal on the MSP430 device has to be held high by an...

  • Page 45: Msp-Prgs430 Used To Program The Pmsp430E31Xfz Device

    Interconnection of MSP-PRGS430 to MSP430x31x Figure 3–6. MSP-PRGS430 Used to Program the PMSP430E31xFZ Device 10 µF 100 nF Xout – (68-Pin CLCC) RST/NMI ~100k Connector, male, for ~68 kΩ TI’s programming adapter for OTP/EPROM PMS430E313FZ e.g. 3M, Order–# 2514–6002 devices (P/E) PMS430E315FZ Socket for FZ–Package, 68CLCC e.g.

  • Page 46: Interconnection Of Msp-Prgs430 To Mps430X32X And Msp430X32Xa

    Interconnection of MSP-PRGS430 to MPS430x32x and MSP430x32xA 3.7 Interconnection of MSP-PRGS430 to MPS430x32x and MSP430x32xA The circuit diagrams in Figure 3–7 through Figure 3–9 show the connections required to program the MSP430x32x and MSP43x32xA devices using the PRGS430 programming adapter. Ensure that both positive terminals AVCC and DVCC are connected.

  • Page 47: Msp-Prgs430 Used To Program The Msp430X32Xipm Or Msp430X32Xaipm

    Interconnection of MSP-PRGS430 to MPS430x32x and MSP430x32xA Figure 3–8. MSP-PRGS430 Used to Program the MSP430x32xIPM or MSP430x32xAIPM Devices 100 nF DVCC 10 µF Xout AVCC – DVSS AVSS RST/NMI MSP430P325IPM MSP430P325AIPM (64-Pin PQFP) ~100k Connector, male, for TI’s programming adapter ~68 kΩ...

  • Page 48: Msp-Prgs430 Used To Program The Pms430E32Xfz And Pms430E32Xafz

    Interconnection of MSP-PRGS430 to MPS430x32x and MSP430x32xA Figure 3–9. MSP-PRGS430 Used to Program the PMS430E32xFZ and PMS430E32xAFZ Devices DVCC Xout 10 µF AVCC 100 nF PMS430E325FZ – DVSS PMS430E325AFZ AVSS RST/NMI ~100k Connector, male, for TI’s programming adapter ~68 kΩ e.g.

  • Page 49: Msp-Prgs430 Used To Program The Msp430X33Xipjm And Msp430X33Xaipjm, Or The Pms430E33Xhfd, Pms430E33Xahfd Devices

    nterconnection of MSP-PRGS430 to MSP430x33x and MSP430x33xA nterconnection of MSP-PRGS430 to MSP430x33x and MSP430x33xA The circuit diagram in Figure 3–10 show the connections required to program the MSP430x33x or MSP430x33xA devices with programming adapter PRGS430 in a separate socket. Since the device is not connected to a power supply in this configuration, the necessary supply comes from the PRGS430.

  • Page 50: Msp-Prgs430 Used To Program The Msp430X11Xidw, Msp430X11X1Idw

    Interconnection of MSP-PRGS430 to MSP430x11x or MSP430x11x1 3.9 Interconnection of MSP-PRGS430 to MSP430x11x or MSP430x11x1 The circuit diagram in Figure 3–11 shows the connections required to program with the programming adapter PRGS430 in a separate socket. Special attention must be given to the design for the four JTAG pins, TDO/TDI, TDI, TMS, and TCK, since they are shared between the application’s hardware and the programming adapter.

  • Page 51: Msp-Prgs430 Used To Program The Msp430X12Xidw, Msp430X12Xipw

    Interconnection of MSP-PRGS430 to MSP430x12x or MSP430x12x2 3.10 Interconnection of MSP-PRGS430 to MSP430x12x or MSP430x12x2 The circuit diagram in Figure 3–12 shows the connections required to program with the programming adapter PRGS430 in a separate socket. Special attention must be given to the design for the four JTAG pins, TDO/TDI, TDI, TMS, and TCK, since they are shared between the application’s hardware and the programming adapter.

  • Page 52: Interconnection Of Msp-Prgs430 To Msp430X13Xipm And Msp430X14Xipm Devices

    Interconnection of MSP-PRGS430 to the MSP430x13x or MSP430x14x 3.11 Interconnection of MSP-PRGS430 to the MSP430x13x or MSP430x14x The circuit diagram in Figure 3–13 shows the connections required to program the MSP430x13x and MSP430x14x devices using TI’s programming adapter MSP-PRGS430. The RST/NMI pin on the MSP430 device must be held high by an external resistor.

  • Page 53: Interconnection Of Msp-Prgs430 To Msp430X41Xipm

    Interconnection of MSP-PRGS430 to the MSP430x41x 3.12 Interconnection of MSP-PRGS430 to the MSP430x41x The circuit diagram in Figure 3–14 shows the connections required to program the MSP430x41 device with TI’s programming adapter MSP-PRGS430. The RST/NMI pin on the MSP430 device must be held high by an external resistor.

  • Page 54: Interconnection Of Msp-Prgs430 To The Msp430X43X Or Msp430X44X

    Interconnection of MSP-PRGS430 to the MSP430x43x or MSP430x44x 3.13 Interconnection of MSP-PRGS430 to the MSP430x43x or MSP430x44x The circuit diagram in Figure 3–15 shows the connections required to program the MSP430x43x or MSP430x44x device with TI’s programming adapter MSP-PRGS430. The RST/NMI pin on the MSP430 device must be held high by an external resistor.
  • Page 55 3-18...

  • Page 56: Intel Hex Object Format

    Appendix A Intel Hex Object Format This appendix discusses the Intel hex object format. Topic Page Intel Hex Object Format ........TI-TXT File Format .
  • Page 57 Intel Hex Object Format A.1 Intel Hex Object Format The Intel hex object format supports 16-bit addresses and consists of a 9-character (4-field) prefix which defines the start of record, byte count, load address, record type, and a 2-character sumcheck suffix. The two record types, which are represented in the 9-character prefix, are described below: 00 = Data record (begins with the colon start character)

  • Page 58: Ti-Txt File Format

    TI-TXT File Format A.2 TI-TXT File Format The TI-TXT file format used by the tool is shown as follows: @ADDR1 DATA01 DATA02 ..DATA16 DATA17 DATA32 ..DATA32 ..DATAm ..DATAn @ADDR2 DATA01 ....DATAn Whereas: @ADDR is the start address of a section (hexadecimal) DATAn represents a data byte (hexadecimal) q is the termination of the file For example:...

  • Page 60: Schematics

    Appendix B Schematics This appendix contains the schematic diatrams for the serial programming adapter. Schematics...

Table of Contents