Texas Instruments Serial Programming Adapter MSP430 User Manual
  1. Manuals
  2. Brands
  3. Texas Instruments Manuals
  4. Adapter
  5. Serial Programming Adapter MSP430
  6. User manual
Texas Instruments Serial Programming Adapter MSP430 User Manual

Texas Instruments Serial Programming Adapter MSP430 User Manual

Family serial programming adapter
Hide thumbs Also See for Serial Programming Adapter MSP430:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
MSP430 Family

Serial Programming Adapter

User's Guide
July 2009
SLAU048H

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Serial Programming Adapter MSP430 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Texas Instruments Serial Programming Adapter MSP430

Summary of Contents for Texas Instruments Serial Programming Adapter MSP430

  • Page 1: Serial Programming Adapter

    MSP430 Family Serial Programming Adapter User’s Guide July 2009 SLAU048H...
  • Page 2 EVALUATION BOARD/KIT IMPORTANT NOTICE Texas Instruments (TI) provides the enclosed product(s) under the following conditions:. This evaluation board/kit is intended for use for ENGINEERING DEVELOPMENT, DEMONSTRATION, OR EVALUATION PURPOSES ONLY and is not considered by TI to be a finished end−product fit for general consumer use.
  • Page 3 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...
  • Page 5 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 6 FCC Warning FCC Warning 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. It generates, uses, and can radiate radio frequency energy and has not been tested for compliance with the limits of computing devices pursuant to part 15 of FCC rules, which are designed to provide reasonable protection against radio frequency interference.

  • Page 7: Table Of Contents

    Running Title—Attribute Reference Contents Installation and Setup ............Installing the Software .
  • Page 8 Running Title—Attribute Reference Figures 1−1 ADT430 Program Icons ............1−2 Serial Programming Adapter .

  • Page 9: 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 10: Installing The Software

    Installing the Software 1.1 Installing the Software To install the MSP-PRGS430 software, perform the following steps: NOTE: To ensure that you are using the latest version of the MSP-PRGS430 software, you must download the installation executable from the TI web site. 1) Browse MSP-PRGS430 page...

  • Page 11: 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 13: 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 MSP430 Devices With the GUI .

  • Page 14: 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 hardware: Using the graphical user interface (see Section 2.2) Using command line parameters (see Section 2.3)

  • Page 15: Programming Msp430 Devices With The Gui

    Programming MSP430 Devices With the GUI 2.2 Programming 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). The MSP430 programmer dialog box appears. The status line at the bottom of the window shows the actual or the most recent activity (see Figure 2−1).

  • Page 16: Description Of The Msp-Prgs430 Gui

    Programming 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. An error message appears on the screen if the device selected is different or not connected.
  • Page 17 Programming MSP430 Devices With the GUI Table 2−1. MSP430 Function Buttons and Descriptions (Continued) Button Name Sub-Functions Description Verify the data in the MSP430 device according to the selected option. By file A verification of the memory locations vs the selected object file is A verification of the memory locations vs the selected object file is performed.

  • Page 18: Error Messages

    Programming MSP430 Devices With the GUI 2.2.3 Error Messages One of the following messages may show up if JTAG communication is not established correctly: If the MSP430 device to program can not be found, the message shown in Figure 2−2 appears. This problem can be caused by the PRGS430 not being connected to the hardware, the device not inserted or incorrectly inserted into the socket, or the device not powered.

  • Page 19: Data Error

    Programming MSP430 Devices With the GUI Figure 2−5. Data Error Operation...

  • Page 20: Error Messages

    Programming 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 Wrong JTAG version!

  • Page 21: Content Of Prgs430.Ini File

    Content of PRGS430.ini File 2.2.4 Content of PRGS430.ini File The last settings of the PRGS430 graphical user interface (GUI) are 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] \BlowFuse = 1 →...

  • Page 22: 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 23 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 24: Return Values/Error Codes In .Ini File

    2.3.2 Return Values/Error Codes in .ini File The error code is returned to the PC operating system and also is 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! The present adapter is not an MSP−PRGS430!

  • Page 25: 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 26 PRGS430.DLL—Description /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 27 PRGS430.DLL—Description Note: For some MSP430 family members, e.g., MSP430F2xxx devices, portions of flash information memory are factory preprogrammed with calibration data. Depending on which method is used for erasing the flash memory, this calibration data may be erased. Should the calibration data be conserved, it must be read out prior to the information memory erase or a flash erase method that does not affect the calibration data memory locations must be used.
  • Page 28 PRGS430.DLL—Description /FN0009/ EraseCheckFile long int EraseCheckFile(char* lpszFileName, long int iFileType) This function checks if all memory addresses, which are in the file, are erased. lpszFilName: Name of the file iFileType: FILETYPE_AUTO (0x00) − autodetection of file type (Intel-hex or TI-TXT) FILETYPE_TI_TXT (0x01) −...
  • Page 29 PRGS430.DLL—Description /FN00012/ VerifyFile long int VerifyFile(char* lpszFileName, long int iFileType) 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-TXT) FILETYPE_TI_TXT (0x01) −...
  • Page 30 PRGS430.DLL—Description wStart: Start address of the range that is to be erased. Allowed values : 0x0000−0xFFFE (see memory map of the corresponding device) wLength: Length of the range Allowed values : 0x0000−0xFFFE (see memory map of the corresponding de- vice) lpData: Pointer to the Data to be programmed Flags: The bits in Flags control the operation of ProgramData().
  • Page 31 PRGS430.DLL—Description Note: Use PGM_ERASE_INFO only together with the PGM_WITH_ERASE flag. lpszProjectIni Name of the {project}.ini file, if protection settings from this file are used. If no protection is required, replace lpszProjectIni with NULL. The added features do not need to be used—for ProgramFile according to older specification, just call ProgramFile(FileName, FileType, 0, NULL);...
  • Page 32 PRGS430.DLL—Description Example: lFuncReturn = ReadOutData(long:0xF000, long:0x1000, void* lpBuffer) /FN0019/ ReadOutFile long int ReadOutFile(long int wStart, long int wLength, char* lpszFileName, long int iFileType) Reads 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) wLength: Length of the area.
  • Page 33 PRGS430.DLL—Description /FN0022/ SetNotificationWnd LONG SetNotificationWnd(LONG hWnd, LONG IMessageID) SetNotificationWnd() enables the status notification of a window. hWnd passes a window handle and IMessageID passes a message identifier. Each time a notification of the status window is necessary, the DLL sends a IMessageID message to the hWnd window.
  • Page 34 PRGS430.DLL—Description DEVICE_MEMDEF (0x07) Fills the definition of a memory definition (index passed by InfoIdx) into lpBuf. DEVICE_MEMPROTECT_COUNT(0x08) GetDeviceCfgInfo() returns the number of memory-protection definitions for the selected device; lpBuf and InfoIdx are ignored. DEVICE_MEMPROTECT (0x09) Fills the definition of a memory protection definition (index passed by InfoIdx) into lpBuf.

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

    PRGS430.DLL—Description 2.4.1 Return Values/Error Codes From 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 −7 Could not sync SPA430...
  • Page 36 2-24...

  • Page 37: Hardware

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

  • Page 38: 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 39: 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 the 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 40: 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 IEEE1149.1 Mandatory Test clock functions according to IEEE1149.1 TDI/VPP Mandatory Test data input functions according to IEEE1149.1, but with additional programming voltage for 3xx devices.

  • Page 41: 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 42: Interconnection Of Msp-Prgs430 To Otp/Eprom-Based Msp430 Devices

    Interconnection of MSP-PRGS430 to OTP/EPROM-Based 3.6 Interconnection of MSP-PRGS430 to OTP/EPROM-Based MSP430 Devices The circuit diagram in Figure 3−4 shows the connections required to program OTP (MSP430Pxxx) and EPROM (MSP430Exxx) based MSP430 devices with the MSP-PRGS430 programming adapter. Consult the device data sheet for the specific device location of the supply and JTAG pins.

  • Page 43: Interconnection Of Msp−Prgs430 To Flash-Based Msp430 Devices

    Interconnection of MSP−PRGS430 to Flash-Based MSP430 Devices 3.7 Interconnection of MSP−PRGS430 to Flash-Based MSP430 Devices The circuit diagram in Figure 3−5 shows the connections required to program flash-based MSP430 devices (MSP430Fxxx) with the MSP−PRGS430 programming adapter. Consult the device data sheet for the specific device location of the power supply and JTAG pins.

  • Page 45: Hex Object Format

    Appendix A Hex Object Format This appendix discusses the hex object format. Topic Page Intel-Hex Object Format ........TI-TXT File Format .

  • Page 46: Intel-Hex Object Format

    Intel-Hex Object Format A.1 Intel-Hex Object Format The Intel-hex object format supports 16-bit addresses and consists of a nine-character (four field) prefix that defines the start of record, byte count, load address, record type, and a two character sumcheck suffix. The two record types, which are represented in the nine-character prefix, are described below: 00 = Data record (begins with the colon start character)

  • Page 47: A.2 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 49: B Schematics

    Appendix B Schematics This appendix contains the schematic diagrams for the serial programming adapter. Schematics...
  • Page 51 Schematics...

  • Page 53: Important Notice

    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.

Table of Contents