MSP430™ Microcontroller Serial Programming Adapter · Delivery: TI delivers TI evaluation boards, kits, or modules, including any accompanying demonstration software, components,

1SLAU048I–August 2000–Revised October 2018Submit Documentation Feedback

Copyright © 2000–2018, Texas Instruments Incorporated

MSP430™ Microcontroller Serial Programming Adapter

User's GuideSLAU048I–August 2000–Revised October 2018


This document describes how to use the MSP430™ Microcontroller Serial Programming Adapter(MSP430-PRGS430). Instructions include how to install the software and hardware for the programmerand how to use the programmer to read to and write from MSP MCUs.

Contents1 Installation and Setup ....................................................................................................... 3

1.1 Installing the Software.............................................................................................. 31.2 Installing the Hardware............................................................................................. 3

2 Operation ..................................................................................................................... 52.1 Software and Hardware Layers of the PRGS430 Environment .............................................. 52.2 Programming MSP430 Devices With the GUI .................................................................. 62.3 Command Line Options .......................................................................................... 112.4 PRGS430.DLL Description....................................................................................... 14

3 Hardware .................................................................................................................... 263.1 Specifications ...................................................................................................... 263.2 Hints................................................................................................................. 263.3 Programming Adapter Target Connector Signals ............................................................. 273.4 MSP-PRGS430 Circuit Diagrams ............................................................................... 293.5 Location of Components on MSP-PRGS430 .................................................................. 293.6 Interconnection of MSP-PRGS430 to OTP or EPROM-Based MSP430 Devices ........................ 303.7 Interconnection of MSP-PRGS430 to Flash-Based MSP430 Devices ..................................... 31

4 Hex Object Format ......................................................................................................... 324.1 Intel-Hex Object Format .......................................................................................... 324.2 TI-TXT File Format ................................................................................................ 33

5 Schematics.................................................................................................................. 33

List of Figures

1 ADT430 Program Icons ..................................................................................................... 32 Serial Programming Adapter ............................................................................................... 43 Software and Hardware Layers ............................................................................................ 54 MSP430 Programmer Dialog Box ......................................................................................... 65 Communication Error Box .................................................................................................. 96 Communication Error Box for Blown Fuse ............................................................................... 97 Erase Check Error Message ............................................................................................... 98 Data Error..................................................................................................................... 99 25-Pin Sub-D at Programming Adapter ................................................................................. 2710 14-Pin Connector at End of Interconnect Cable ....................................................................... 2711 MSP-PRGS430 Components............................................................................................. 2912 MSP-PRGS430 Used to Program OTP or EPROM-Based MSP430 Devices ..................................... 3013 MSP-PRGS430 Used to Program Flash-Based MSP430 Devices .................................................. 3114 Intel-Hex Object Format ................................................................................................... 3215 Schematics (1 of 2) ........................................................................................................ 3416 Schematics (2 of 2) ........................................................................................................ 35

http://www.go-dsp.com/forms/techdoc/doc_feedback.htm?litnum=SLAU048I

www.ti.com

2 SLAU048I–August 2000–Revised October 2018Submit Documentation Feedback



List of Tables

1 MSP430 Function Buttons and Descriptions............................................................................. 72 Error Messages............................................................................................................. 103 Command Line Options ................................................................................................... 114 SetNotificationWnd Status Codes........................................................................................ 235 Return Values and Error Codes .......................................................................................... 256 MSP430 Hardware Specifications ....................................................................................... 267 Target Connector Signal Functions ...................................................................................... 288 Programming Adapter Signal Levels .................................................................................... 28

TrademarksMSP430 is a trademark of Texas Instruments.All other trademarks are the property of their respective owners.

http://www.ti.com


www.ti.com Installation and Setup




1 Installation and SetupThis section describes how to install and program the hardware and software for the MSP430-PRGS430programming adapter used with the MSP430 family of microcontrollers.

1.1 Installing the SoftwareTo install the MSP-PRGS430 software, perform the following steps.1. To ensure that you are using the latest version of the MSP-PRGS430 software, download the latest

software from http://www.ti.com/lit/zip/slac029 and extract the installation executable(PRGS430_Rxxx.exe).

2. Run PRGS430_Rxxx.exe. A welcoming message is displayed.3. Follow the setup instructions. The setup program guides you through the installation process.4. During setup, the MSP430 program icons are installed in the selected folder. Click on the PRGS430

Read Me First icon (see Figure 1) for important information about the program device hardware andsoftware.

Figure 1. ADT430 Program Icons

5. To start the programming adapter software, click the PRGS430 icon in the selected program group(default: ADT430).

1.2 Installing the HardwareTo 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 to

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. The center terminalof the supply connector at the programming adapter is the positive pole.

3. The red LED on the programming adapter illuminates if the power supply is properly connected. If theLED does not illuminate and the power supply is properly connected, check the F1 fuse on theprogramming adapter printed-wire board (PWB).

4. Connect the MSP430 MCUs, in a socket or on a PWB, to the programming adapter through the 14-pincable.The programming adapter provides the selected supply voltage VCC at pin 14 of the 25-pin SUB-Dconnector, or at pin 2 of the 14-pin connector to supply the MSP430 MCU. The signal name isVCC_MSP.If an external supply voltage VCC is used for the MSP430, the internal voltage VCC_MSP must be setto the same voltage level.

http://www.ti.com


http://www.ti.com/lit/zip/slac029)

Installation and Setup www.ti.com




Figure 2. Serial Programming Adapter

http://www.ti.com


www.ti.com Operation




2 OperationThis section describes the programming procedure for MSP430 MCUs and the error messages you mayencounter during the procedure.

2.1 Software and Hardware Layers of the PRGS430 EnvironmentFigure 3 shows the layers of the environment and the communication options.

Figure 3. Software and Hardware Layers

The options to handle and communicate with the PRGS430 hardware are:• Using the graphical user interface (see Section 2.2)• Using command line parameters (see Section 2.3)• Using the PRGS430.dll (see Section 2.4). This is the fastest way if the PRGS430 is used in an in-

system program and test environment.

http://www.ti.com


Operation www.ti.com




2.2 Programming MSP430 Devices With the GUI

2.2.1 Basic ProcedureTo program the MSP430 MCUs:1. Click 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 theactual or the most recent activity (see Figure 4). The status line displays the message "Connecting toadapter..." until the programming adapter is detected and the baud rate is set.

2. Select the correct device and supply voltage.3. Select the name of the object file (TI-TXT (.txt) or Intel-hex (.a43) format).4. Select the additional options to program, if necessary using Erase Flash, Erase Check, or Verify (see

Table 1).5. Click the Program button to start programming. The status line at the bottom of the window shows the

actual or most recent activity (see Figure 4).

Figure 4. MSP430 Programmer Dialog Box

http://www.ti.com






2.2.2 Description of the MSP-PRGS430 GUITo program an MSP430 MCU:1. Select the file that contains the data to program from the MSP430 programmer dialog box (see

Figure 4).2. Select the device. An error message appears on the screen if the device selected is different or not

connected.3. Set the required supply voltage, communication port COMx, and baud rate. The device configuration

and memory type are selected automatically according to the selected device.4. Click the Program button to start the programming operation.

Table 1 describes the function of the buttons for different options and combinations for the MSP430programmer dialog box.

Table 1. MSP430 Function Buttons and Descriptions

Button Name Functions DescriptionFile Name Selects the name of the file to program (Intel-hex or TI-TXT format)Device Select Selects the MSP430 MCU type to program from a list

Supply VoltageVCC switch off Selects the supply voltage for the MSP430

If selected (default), the supply voltage is switched off after each MSP430 access;otherwise, the supply voltage remains connected.

Program

An object code is programmed to the on-chip memory using the select options.

With Erase Flash Memory is erased before programming (only with flash devices). The followingoptions are possible:− Main and information memory− Main memory only

With Erase Check Erase check is performed before programming operation is executed.

With Verify Each section is verified after it is programmed, or an error message is displayed ifverification fails.

With Blow Fuse

The code-protection fuse is blown after the entire object code, with verify, isprogrammed. This action is irreversible and disables future on-chip memory access(reading or programming). This step is not performed if verify is disabled or verifyfails. A warning is displayed.

Erase Flash

Erase operation can be done only with flash devices, according to the selectedoption.

By file Only the memory locations corresponding to the selected object file are erased. Allother memory locations keep their old data (smart erase).

By device The entire flash memory of the device is erased.By range An erase is performed depending on the values entered in the range fields.

Erase Check

Checks if memory locations are erased.By file Checks only the memory locations used by the selected object file.By device Checks the entire programmable memory of the device. (No RAM is checked.)

By range An erase check is performed according to the range of memory locations in therange for Erase Check/Readout field.

Verify

Verify the data in the MSP430 MCU according to the selected option.

By file A verification of the memory locations vs the selected object file is performed. (Byfile and by device are the same functions.)

By device

By rangeVerify memory locations defined in the range field vs the data in the selected file.The defined range should not contain memory locations outside the data stored inthe selected file, otherwise an error is reported.

Blow FuseThe on-chip security fuse is irreversibly disabled and any access, such as readingor programming of the MSP430, is impossible through JTAG. Access throughbootstrap loader interface is possible for devices that support that interface.

http://www.ti.com






Table 1. MSP430 Function Buttons and Descriptions (continued)Button Name Functions Description

Read

Read data from MSP430 MCU. When this function is executed, a dialog boxappears; the file name for the data to store should be selected.

By device Read the entire memory of the device and store the data into the file selected inthe file name field.

By range Read the memory locations selected by the range field and store the data in the fileselected in the file name field.

Reset

The reset of a MSP430 can be performed in two ways. After reset, the MSP430may remain under JTAG control or can be released to operate normally andexecute the program.

PUC A software reset of the chip is generated.RST/NMI Generates a hardware reset by applying a low pulse on RST/NMI pin.With JTAG release JTAG is released after the execution of the reset (through JTAG or RST/NMI).

COM Port Selects the COM port to which the programming adapter is connectedBaud Rate Selects the baud rate for communication with the programming adapter hardware

Help

Help is available for programming MSP430 MCUs, command buttons, selectors,and the object file format used. The Help menu can be found in the system menuof the serial programming adapter software (right click on the symbol at the upper-left corner of the program window) or with the F1 function key.

NOTE: For some MSP430 family members, for example, MSP430F2xxx devices, portions of flashinformation memory are factory preprogrammed with calibration data. Depending on whichmethod is used for erasing the flash memory, this calibration data may be erased. Should thecalibration data be conserved, it must be read prior to the information memory erase or aflash erase method that does not affect the calibration data memory locations must be used.See the device-specific data sheet for further information on preprogrammed calibration datamemory locations.

If it should be saved, the following erase options must not be used as the Info memory willbe entirely erased:• Program with Erase Flash (flash-erase options: Main and Info Memory)

or• Erase Flash by Device

Instead, "Erase Flash by File" or "Erase Flash by Range" should be used.

http://www.ti.com






2.2.3 Error MessagesOne of the following messages may show if JTAG communication is not established correctly:• If the MSP430 MCU to program can not be found, the message shown in Figure 5 appears. This

problem can be caused by the PRGS430 not being connected to the hardware, the device not insertedor incorrectly inserted into the socket, or the device not powered.

• The problem could be that the PRGS430 is not connected to the hardware, the device is not insertedor is incorrectly inserted into the socket, or the device is not powered.

Figure 5. Communication Error Box

If the fuse is already blown, the error message shown in Figure 6 appears.

Figure 6. Communication Error Box for Blown Fuse

Additional message boxes appear for general error messages, such as erase check (see Figure 7).

Figure 7. Erase Check Error Message

When a read error is detected in the input file, such as a format error, the following message is displayed(see Figure 8).

Figure 8. Data Error

http://www.ti.com






Table 2. Error Messages

Error Type Error MessageCommunication Communication failed!Communication Adapter not connected!Communication Synchronization with adapter failed!Communication The present adapter is not an MSP-PRGS430!Communication Missing setting of VCC!

MSP430 Target not connected!MSP430 Wrong JTAG version!MSP430 PUC failed!MSP430 Wrong target!MSP430 Target fuse is blown!MSP430 Blown fuse failed!MSP430 Supply voltage to low!MSP430 Fuse not released for this device!Setting Unknown target!Setting No target selected!Setting Wrong VCC selected!Setting Wrong baud rate!Setting Communication port error!Setting The selected range is invalid!Setting Wrong argument!Setting Error at target address (during erase check or verify)Setting Unknown command line optionSetting Command line option out of valid rangeSystem DEVICE.CFG corruptedSystem General error!System File type could not be detected!System Unexpected end of file!System PROJECT.INI corrupted!System Filename mismatchSystem Error in DEVICE.CFG

Windows Error during file I/O

2.2.4 Content of PRGS430.ini FileThe last settings of the PRGS430 graphical user interface (GUI) are stored in the .ini file before exiting theprogram. 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 → The blow fuse button in the GUI is disabled to prevent accidental blow of the irreversiblefuse.

LastResult = 0 → If the program is called with command-line parameter, the error code that is returned tothe system when exiting the program is also stored here.

http://www.ti.com






2.2.5 Use of a [Project].ini FileSome default options could be changed within a [Project].ini file. This file has to be in the same directoryas the object code file. The following variables could be defined or redefined there.

The name of the file should have the same name as the object file with the extension .ini.[ProgramDevice]UserMemProtect = Start, SizeUserMemProtect2 = Start, SizeUserMemProtect3 = Start, SizeUserMemProtectn = Start, SizeDisableTIMemProtect = 0

Memory ranges defined in the UserMemProtect and UserMemProtect [n] option are read andreprogrammed after erase (flash device only). [n] could be a number ≥2 and be in ascending order.

If a memory protection is activated in the device definition file from TI, it can be switched off with theDisableTIMemProtect = 1 option.

2.3 Command Line Options

2.3.1 General Definitions

0: Off 1: First selectable option1: 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. The command lineoption overwrites the .ini file options.

The program exits automatically if a command is passed in the command line and the command wasexecuted. There is only a small status window opened during the execution.

Only one command identifier (/cmd:) is allowed within the command line. Otherwise, the execution iscanceled and an error is returned.

If an error in the command line parameter is detected, the program exits with an error message.

The filename may also contain a path. If special characters are used, the string has to be inside quotes(for example, \\server\adt430\PRG files\test.txt).

If an error is detected in the filename, the operation is canceled and an error is returned.

Table 3. Command Line Options

Command/cmd:PRG Program command/cmd:VFY Verify command/cmd:ERS Erase command/cmd:CHK Erase check command/cmd:READ Read command/cmd:RST Reset command/cmd:BLOW Blow fuse commandOptions/COM:x Specifies the serial port: /COM:1, /COM:2, /COM:3, or /COM:4/BR:xxxxxx Sets baud rate to be used: 9600/19200/38400/57600/115200, for example, /BR:57600/Dev: Selects the device according to the name in the device.cfg file, for example, /Dev:MSP430F1121

/SVolt:x.x Selects supply voltage MSP_VCC of the programming adapter. The voltage is supplied between GNDand MSP VCC, for example, /Svolt: 3.0.

http://www.ti.com






Table 3. Command Line Options (continued)

/SVoff:{0,1}Switches off supply voltage MSP_VCC after execution0: Disable (do not switch off)1: Enable (switch off)

filename Specifies name of the object file to be programmed or verified/FILE filename (Second way to define the filename − space separated)Options for Program Command

/PE:{0,1,2}

Option program with erase (flash only)0: Without erase1: Main and Info memory2: Main memory only

/PC:{0,1}Option program with erase check0: Disable1: Enable

/PV:{0,1}Option program with verify0: Disable1: Enable

/PB:{0,1}Option program with blow fuse (only valid with verify successful)0: Disable1: Enable

Options for Erase, Erase Check, and Verify Command

/E:{1,2,..}

Option for the erase, erasecheck, or verify by file/device/range1: File2: Device3: Range

/ERange:0xXXX, 0xYYYY Option for the erase, erasecheck, or verify range (start: 0xXXXX, length: 0xYYYY)Options for Read Command

/RO:{1,2}Option read by device or range1: Device2: Range

/RRange:0xXXXX,0xYYYY Option read range (start: 0xXXXX, length: 0xYYYY)

/Rfile:filename,{1,2}Specifies read file name1: TI-TXT2: Intel-hex (default directory should be the last object file directory)

Log Options/Log:filename Specifies log file name (default directory should be the PRGS430.exe directory)

/ALog:{0,1}Option accumulative Log file0: Disable1: Enable

ExamplePRGS430.exe "C:\adt430\test\test.txt" /Dev:MSP430F1121 /cmd:PRG /PE:1 /PC:0/PV:1 /COM:2

This command programs the file test.txt, located in the directory C:adt430\test, into a MSP430F149device. The device is erased before programming. The erase check is disabled. The code is verified afterprogramming. The programming adapter is connected to ComPort 2. The baud rate is not passed with thecommand line, so the setting in the PRGS430.ini file is used.

http://www.ti.com






2.3.2 Return Values and Error Codes in .ini FileThe error code is returned to the PC operating system and also is stored in PRGS430.ini file in the[Options] section:LastResult=0

0 Ok2 Communication failed!3 Target not connected!4 Adapter not connected!5 Wrong JTAG version!6 PUC failed!7 Synchronization with adapter failed!8 The present adapter is not an MSP-PRGS430!9 Unknown target!10 Wrong target!11 No target selected!12 Target fuse is blown!13 Blow fuse failed!14 Missing setting of VCC!15 Wrong VCC selected!16 Wrong baudrate!17 Communication port error!18 DEVICE.CFG corrupted!19 General error!20 The selected range is invalid!21 Wrong argument!22 Error during file I/O23 File type could not be detected!24 Unexpected end of file!25 PROJECT.INI corrupted!26 Vcc voltage too low for selected function!27 Fuse not release for this device!101 Error at target address (during erase check or verify)102 Unknown command line option103 Command line option out of valid range104 Filename mismatch105 Error in device.cfg

http://www.ti.com






2.4 PRGS430.DLL DescriptionThe PRGS430.dll is used to communicate with the MSP-PRGS430 hardware and the connected MSP430MCU.

The initialization of the PRGS430 should be done with this sequence:InitComSetDeviceTypeSetVCC. InitTarget. .... ReleaseTargetReleaseCom

Several examples showing how the DLL could be used are located in the DLL_Usage_Examples folder ofthe PRGS430 system. This dll can be used separately using the conventions in the following sections.

2.4.1 /FN0001/ InitComInitCom initializes (opens) the given communications port, establishes communication with the PRGS430hardware, and sets the baud rate of the MSP-PRGS430. If successful, the MSP-PRGS430 is reset andVCC is set to 0.0 V (the voltage should be set after the first user action to validate the correct value).long int InitCom(char* lpszComPort, long int lBaudRate)

lBaudRateValid baud rates are: 9600, 19200, 38400, 56800, and 115200 baud. The default baud rate afterinstallation is 115200 baud.

lpszComPortThe name of the communication port—COM1, COM2, COM3, or COM4.

ExamplelFuncReturn = InitCom("COM1" 115200)

2.4.2 /FN0002/ ReleaseComThis new function is the counterpart to InitCom. It allows to close a communication with the MSP-PRGS430 hardware. VCC is set to 0 and all outputs are set to the Hi-Z state.long int ReleaseCom (void)

ExamplelFuncReturn = ReleaseComm()

2.4.3 /FN0003/ SetDeviceTypeSelects the device type.lFuncReturn = SetDeviceType(char* lpszDeviceName)

lpszDeviceNameName of the device in file device.cfg

ExamplelFuncReturn = SetDeviceType("MSP430F1121")

http://www.ti.com






2.4.4 /FN0004/ InitTargetInitializes the JTAG access to the target device, detects the device type, and reports when the detecteddevice does not match the parameter DeviceName passed.long int InitTarget(char* lpszDeviceName)

lpszDeviceNameName of the device in file device.cfg

ExamplelFuncReturn = InitTarget ("MSP430F1121")

2.4.5 /FN0005/ ReleaseTargetThis function performs a PUC and releases the JTAG access to the target device. All JTAG signals fromthe serial programming adapter are switched to Hi-Z. The device starts program execution if it is stillconnected to VCC.long int ReleaseTarget(void)

ExamplelFuncReturn = ReleaseTarget()

2.4.6 /FN0006/ EraseThis function erases flash memory (if available). The protection of areas can be disabled by setting theDISABLE_TI_MEM_PROTECT−Bit in Flags.long int Erase(long int wStart, long int wLength, long int Flags)

wStartStart address of the area to be erased. Allowed values are 0x0000 to 0xFFFE (see the memory map inthe device-specific data sheet for the supported memory size).

wLengthLength of the area. Allowed values are 0x0000 to 0xFFFE (see the memory map of the correspondingdevice).

If erasing information and main memory segments, first erase the information memory segments, thenerase the main memory segments.

The mass erase sequence then would be:Erase(InfoStart,InfoLength,0);Erase(MainStart,MainLength,0);

The function invokes a mass erase for information or main memory if the start address and the completememory range of the information or main memory is specified. If the range specified is not complete forthat device, a segment erase of the individual segments is performed.

FlagsDISABLE_TI_MEM_PROTECT (0x01)If this bit is set, the memory protection settings in device.cfg are ignored.

ExamplelFuncReturn = Erase(long:0xF000, long:0x1000, long:1)

For some MSP430 family members (for example, MSP430F2xxx devices) portions of flash informationmemory are factory preprogrammed with calibration data. Depending on which method is used for erasingthe flash memory, this calibration data may be erased. Should the calibration data be conserved, it mustbe read prior to the information memory erase or a flash erase method that does not affect the calibrationdata memory locations must be used. See the device-specific data sheet for further information onpreprogrammed calibration data memory locations.

http://www.ti.com






2.4.7 /FN0007/ EraseFileErases all addresses used in the specified file.long int EraseFile(char* lpszFileName, long int iFileType, long int Flags,char* lpszProjectIni)

iFileTypeFILETYPE_AUTO (0x00): Autodetection of file type (Intel-hex or TI-TXT)FILETYPE_TI_TXT (0x01): File type is TI-TXTFILETYPE_INTEL_HEX (0x02): File type is Intel-hex

FlagsDISABLE_TI_MEM_PROTECT (0x01)If this bit is set, the memory protection setting device.cfg is ignored. lpszProjectIni: name of the{project}.ini file, if protection settings from this file shall be used. If there is no protection, replacelpszProjectIni with NULL.

ExamplelFuncReturn = EraseFile("text.txt", long:0, long:0, NULL)

For some MSP430 family members, for example MSP430F2xxx devices, portions of flash informationmemory are factory preprogrammed with calibration data. Depending on which method is used for erasingthe flash memory, this calibration data may be erased. Should the calibration data be conserved, it mustbe read prior to the information memory erase or a flash erase method that does not affect the calibrationdata memory locations must be used. See the device-specific data sheet for further information onpreprogrammed calibration data memory locations.

2.4.8 /FN0008/ EraseCheckPerforms an erase check of an area of the target memorylong int EraseCheck(long int wStart, long int wLength)

wStartStart address of the memory area. Allowed values are 0x0000 to 0xFFFE (see the memory map in thedevice-specific data sheet for the supported memory size).

wLengthSize of the area. Allowed values are 0x0000 to 0xFFFE (see the memory map in the device-specificdata sheet for the supported memory size).

The function EraseCheck() simply uses PatternCheck(), with 0xFFFF as pattern.EraseCheck(long int wStart, long int wLength){return PatternCheck(wStart, wLength, 0xFFFF);}

ExamplelFuncReturn = EraseCheck(long:0xF000, long:0x1000)

http://www.ti.com






2.4.9 /FN0009/ EraseCheckFileChecks if all memory addresses in the file are erased.long int EraseCheckFile(char* lpszFileName, long int iFileType)

lpszFileNameName of the file

iFileTypeFILETYPE_AUTO (0x00): autodetection of file type (Intel-hex or TI-TXT) FILETYPE_TI_TXT (0x01):file type is TI-TXTFILETYPE_INTEL_HEX (0x02): file type is Intel-hex

The function returns success or the first address with mismatching data.

ExamplelFuncReturn = EraseCheckFile("test.txt", long:0)

2.4.10 /FN00010/ PatternCheckChecks a memory range with word pattern passed.long int PatternCheck(long int wStart, long int wLength, long int wPattern)

wStartStart address of the memory area. Allowed values are 0x0000 to 0xFFFE (see the memory map in thedevice-specific data sheet for the supported memory size).

wLengthSize of the area. Allowed values are 0x0000 to 0xFFFE (see the memory map in the device-specificdata sheet for the supported memory size).

wPatternWord pattern for check


ExamplelFuncReturn = PatternCheck(long:0xF000, long:0x1000, long:0xFFFF)

2.4.11 /FN00011/ VerifyDataThis function verifies the content of the device with the data stored at passed pointer to data.long int VerifyData(long int wStart, long int wLength, void* lpData)

wStartStart address of memory area. Allowed values are 0x0000 to 0xFFFE (see the memory map in thedevice-specific data sheet for the supported memory size).

wLengthLength of the memory area to be checked. Allowed values are 0x0000 to 0xFFFE (see the memorymap in the device-specific data sheet for the supported memory size).

lpDataPointer to buffer with data bytes in it


ExamplelFuncReturn = VerifyData(long:0xF000, long:0x1000, void* lpData)

http://www.ti.com






2.4.12 /FN00012/ VerifyFileThis function checks if the memory contents of the target device are equal to the file contents.long int VerifyFile(char* lpszFileName, long int iFileType)


iFileTypeFILETYPE_AUTO (0x00): autodetection of file type (Intel-hex or TI-TXT)FILETYPE_TI_TXT (0x01): file type is TI-TXTFILETYPE_INTEL_HEX(0x02): file type is Intel-hex


ExamplelFuncReturn = VerifyFile("test.txt", long:0)

2.4.13 /FN00013/ VerifyFileRangeThis function evaluates if the memory contents of the target device are equal to the file contents in apassed range.long int VerifyFileRange(char* lpszFileName, long int iFileType, long intwStart, long int wLength)


iFileTypeFILETYPE_AUTO (0x00): autodetection of file type (Intel-hex orTI-TXT) FILETYPE_TI_TXT (0x01): file type is TI-TXTFILETYPE_INTEL_HEX (0x02): file type is Intel-hex

wStartStart address of memory area. Allowed values are 0x0000 to 0xFFFE (see the memory map in thedevice-specific data sheet for the supported memory size).

wLengthLength of the memory area to be checked. Allowed values are 0x0000 to 0xFFFE (see the memorymap in the device-specific data sheet for the supported memory size).


ExamplelFuncReturn = VerifyFileRange("test.txt", long:0, long:0xF000, long:0x1000)

http://www.ti.com






2.4.14 /FN0014/ ProgramDataThis function writes data into an MSP430 MCU. Protection of ranges of memory locations defined in theDEVICE.CFG file can be disabled by setting the DISABLE_TI_MEM_PROTECT−Bit in Flags.long int ProgramData(long int wStart, long int wLength, void* lpData)

wStart

Start address of the range that is to be erased. Allowed values are 0x0000 to 0xFFFE (see the memorymap in the device-specific data sheet for the supported memory size).

wLengthLength of the range. Allowed values are 0x0000 to 0xFFFE (see the memory map in the device-specific data sheet for the supported memory size).

lpDataPointer to the Data to be programmed

FlagsThe bits in Flags control the operation of ProgramData().

ExamplelFuncReturn = ProgramData(long:0xF000, long:0x1000, void* lpData)

http://www.ti.com






2.4.15 /FN0015/ ProgramFileThis function writes data from the file to the MSP430 MCU. The protection of ranges of memory locationsdefined in the DEVICE.CFG file can be disabled by setting the DISABLE_TI_MEM_PROTECT−Bit inFlags.

If the PGM_WITH_ERASE option are not selected the program data is preserved. This means that thedata is read from the flash and replaced with the new data. All other information is restored automatically.The handling of the information memory works with the same mechanism.

For the fastest programming speed, select the PGM_WITH_ERASE and PGM_ERASE_INFO options.long int ProgramFile(char* lpszFileName, long int iFileType, long int iFlags,char* lpszProjectIni)

lpszFileNameName of the file to be written into the target

iFileTypeFILETYPE_AUTO (0x00): autodetection of file type (Intel-hex orTI-TXT) FILETYPE_TI_TXT (0x01): file type is TI-TXTFILETYPE_INTEL_HEX (0x02): file type is Intel-hex

iFlagsDISABLE_TI_MEMPROTECT (0x01)PGM_WITH_ERASE (0x02) // Erases the main memory before programmingPGM_ERASE_INFO (0x04) // Erases the info memory before programmingPGM_WITH_ERASECHECK (0x08) // Erase check by device and the programs the devicePGM_WITH_Verify (0x10) // Read device, merge with file to be programmed, and write back to deviceUse PGM_ERASE_INFO only together with the PGM_WITH_ERASE flag.

lpszProjectIniName 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 example, to call ProgramFile according to olderspecification, call:

ProgramFile(FileName, FileType, 0, NULL)

If no {project}.ini file or erase check is used, call:lFuncReturn = ProgramFile(FileName, 0, 0, NULL); // with autodetect file type

If an erase or erase-check function reports an error, the function ProgramFile() is aborted beforeprogramming is started.

http://www.ti.com






2.4.16 /FN0016/ BlowFuseThis function blows the security fuse of the target device.long int BlowFuse(void)

ExamplelFuncReturn = BlowFuse(void)

2.4.17 /FN0017/ SetVccSets the VCC_MSP voltage of the programming adapter to the given value.long int SetVcc(long int iVoltage)

iVoltageVCC in mV (for example, 3000 = 3 V)The voltage range is limited to the voltage allowed for the selected MSP430 MCU.

ExamplelFuncReturn = SetVcc(Long:3000)

2.4.18 /FN0018/ ReadOutDataReads data from the device and writes it to the buffer.long int ReadOutData(long int wStart, long int wLength, void* lpBuffer)

wStartStart address of the area to be read. Allowed values are 0x0000 to 0xFFFE (see the memory map inthe device-specific data sheet for the supported memory size).

wLengthLength of the area. Allowed values are 0x0000 to 0xFFFE (see the memory map in the device-specificdata sheet for the supported memory size).

lpBufferPointer points to a buffer that receives the data. The buffer must be large enough to hold the entiredata; otherwise, a fatal error of the operating system may occur.

ExamplelFuncReturn = ReadOutData(long:0xF000, long:0x1000, void* lpBuffer)

http://www.ti.com






2.4.19 /FN0019/ ReadOutFileReads data from the device and writes it to a file.long int ReadOutFile(long int wStart, long int wLength, char* lpszFileName,long int iFileType)

wStartStart address of the area to be read. Allowed values are 0x0000 to 0xFFFE (see the memory map inthe device-specific data sheet for the supported memory size).

wLengthLength of the area. Allowed values are 0x0000 to 0xFFFE (see the memory map in the device-specificdata sheet for the supported memory size).

lpszFileNameName of the file to receive data. If the file does not exist, it is created; If the file already exists, it isoverwritten.

iFileTypeFILETYPE_TI_TXT (0x01): file type is TI-TXTFILETYPE_INTEL_HEX (0x02): file type is Intel-hex

ExamplelFuncReturn = ReadOutFile(long:0xF000, long:0x1000, "test.out", long:1)

2.4.20 /FN0020/ ResetThis function provides the reset functionality for the target. Flags: Flags is a bitmap and determines thetype of reset.long int Reset(long int Flags)

FlagsPUC 0x01RST_NMI 0x02WITH_RELEASE 0x04

Reset | PUC means that the JTAG sends the command to the MSP430. Reset | RST_NMI performs areset through the RST/NMI pin of the MSP430 MCU. The JTAG is also reset.

If the WITH_RELEASE option is selected, the device is released from the JTAG access after the reset.

ExamplelFuncReturn = Reset(long:5)

http://www.ti.com






2.4.21 /FN0022/ SetNotificationWndSetNotificationWnd() enables the status notification of a window. Each time a notification of the statuswindow is necessary, the DLL sends a IMessageID message to the hWnd window. The execution statusof an operation is passed in the WParam of this message. Completion status of the current operation ispassed (0..100) in the LParam.LONG SetNotificationWnd(LONG hWnd, LONG IMessageID)

hWndA window handle

ImessageIDA message identifier

Table 4 lists the status codes.

Table 4. SetNotificationWnd Status Codes

Status WParam Current OperationSTATUS_CONNECTSPA 1 Connecting to SPA430STATUS_CONNECTTARGET 3 Connecting to targetSTATUS_RELEASETARGET 5 Releasing targetSTATUS_RELEASESPA 7 Releasing SPA430STATUS_RESETTARGET 9 Resetting targetSTATUS_ERASE 11 Erasing targetSTATUS_ERASECHECK 13 Erase checking targetSTATUS_PATTERNCHECK 15 Pattern checking targetSTATUS_VERIFY 17 Verifying targetSTATUS_PROGRAM 19 Programming targetSTATUS_READOUT 21 Reading target outSTATUS_BLOWFUSE 23 Blowing fuse

http://www.ti.com






2.4.22 /FN0023/ GetDeviceCfgInfolong int GetDeviceCfgInfo(long int InfoCmd, long int InfoIdx, void* lpBuf)

InfoTypeDEVICE_COUNT (0x01): GetDeviceCfgInfo returns number of devices in Device.cfg; InfoIdx and lpBufare ignored.SELECT_DEVICE (0x02): Selects the given device for further commands (device number in InfoIndex,first device is number 0; lpBuf is ignored).DEVICE_NAME (0x03): Fills the name of the selected device into lpBuf; InfoIdx is ignored.DEVICE_ID (0x04): Fills the DeviceID into lpBuf, InfoIdx is ignored.DEVICE_DEFAULTOPTIONS (0x05): Fills the default options into lpBuf, InfoIdx is ignored.DEVICE_MEMDEF_COUNT (0x06): GetDeviceCfgInfo() returns the number of memory definitions forselected device; lpBuf and InfoIdx are ignored.DEVICE_MEMDEF (0x07): Fills the definition of a memory definition (index passed by InfoIdx) intolpBuf.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 byInfoIdx) into lpBuf.DEVICE_VCC (0x0A): GetDeviceCfgInfo() returns the Vcc setting for selected device in mV; lpBuf andInfoIdx are ignored.DEVICE_VPP (0x0B): GetDeviceCfgInfo() returns the Vpp setting for selected device in mV; lpBuf andInfoIdx are ignored.DEVICE_VFUSE (0x0C): GetDeviceCfgInfo() returns the blow-fuse setting for the selected device;lpBuf and InfoIdx are ignored.

2.4.23 /FN0024/ AccessSFRThis function writes or reads data into the special function registers of the MSP430 MCU. (implemented inPRGS320.dll versions 1.05 and higher).long int AccessSFR(LONG wAddr, void *IpData, LONG iFlags);

wAddrSFR address that should be accessed. Allowed values are 0x0000 to 0x1FE (see the memory map ofthe corresponding device)

IpDataPointer to the data to be written, or buffer which should receive the read data

FlagsThe bits in Flags control the operation of AccessSFR()

iFlagsSFR_READ (0x00)SFR_Write 0x01)

ExampleIFuncReturn = AccessSFR(long:0x0020, &IpData, 0)

http://www.ti.com






2.4.24 Return Values and Error Codes From PRGS430.DLLTable 5 lists the return values and error codes from PRGS430.DLL.

Table 5. Return Values and Error Codes

Status Return Value CommentOK 0SUCCESS −1 Operation OKERR_COMMUNICATION −2 Communication error (SSP)ERR_TARGET_NOT_CONNECTED −3 No target connectedERR_SPA430_NOT_CONNECTED −4 No SPA430 connectedERR_WRONG_JTAG_VERSION −5 JTAG version above 3ERR_PUC_FAILED −6 PUC did not succeedERR_SPA430_SYNC_FAILED −7 Could not sync SPA430ERR_NO_SPA430 −8 Adapter is not SPA430ERR_UNKNOWN_TARGET −9 Target type unknownERR_WRONG_TARGET −10 Target type does not matchERR_NO_TARGET_SELECTED −11 No target selected (missing SetDeviceType() call)ERR_TARGET_FUSE_BLOWN −12 No target access because of blown fuseERR_BLOW_FUSE_FAILED −13 Blown-fuse command failedERR_VCC_NOT_SET −14 No VCC selected (missing SetVolt() call)ERR_WRONG_VCC −15 VCC out of allowed rangeERR_WRONG_BAUDRATE −16 Invalid baud rateERR_COMPORT −17 Error accessing the communications portERR_DEVICE_CFG −18 Device.cfg corruptedERR_GENERAL −19 General error (should not occur!)ERR_RANGE −20 Wrong range specifiedERR_ARGUMENT −21 Wrong argumentERR_FILE_IO −22 Error during file I/OERR_FILE_DETECT −23 File type could not be detectedERR_FILE_END −24 Unexpected end of fileERR_PROJECT_INI −25 Error reading {project}.iniERR_VCC_BELOW_VCCMINPROG −26 VCC to low for selected functionERR_FUSE_NOT_RELEASED −27 Fuse not release for this deviceSTATUS_CONNECTSPA 1 Connecting to SPA430STATUS_CONNECTTARGET 3 Connecting to targetSTATUS_RELEASETARGET 5 Releasing targetSTATUS_RELEASESPA 7 Releasing SPA430STATUS_RESETTARGET 9 Resetting targetSTATUS_ERASE 11 Erasing targetSTATUS_ERASECHECK 13 Erase checking targetSTATUS_PATTERNCHECK 15 Pattern checking targetSTATUS_VERIFY 17 Verifying targetSTATUS_PROGRAM 19 Programming targetSTATUS_READOUT 21 Reading out targetSTATUS_BLOWFUSE 23 Blowing fuseERR_READOUT_LOCKED −28 Read prohibited

http://www.ti.com


Hardware www.ti.com




3 HardwareThis section describes the hardware for the MSP430 family of microcontrollers, including specifications,components of the programming adapters, and connection of the programming adapter to the MSP430MCU families.

3.1 SpecificationsTable 6 lists the specifications for the MSP430 hardware.

Table 6. MSP430 Hardware Specifications

Specification ValueTemperature Range 10°C to 45°CHumidity 40% to 70%Power supply 14 V to 20 V, 200 mA minimumDimensions 150 mm (W) × 30 mm (H) × 95 mm (D)

3.2 HintsThese hints are useful for programming MSP430 MCUs or MSP430 MCUs on printed-wire boards (PWB).• All VCC pins of an MSP430 MCU are tied together and connected to the most positive terminal of the

supply.• All VSS pins of an MSP430 MCU are tied together and connected to the most negative terminal of the

supply.• The interface should supply the MSP430 with proper conditions according to the device data sheet, in

terms of current, voltage levels, and timing conditions.• Make sure the proper signal connections (see Section 3.3) are made.• Short cables to interconnect the interface to the MSP430 MCU or PWB; less than 20 cm is

recommended.• Ensure low-impedance interconnections, especially for the path of the programming and fuse blow

voltage.• When a device with a transparent window (MSP430E3xx family) is programmed, the window should be

already covered with an opaque label while the device is programmed. Because ambient light containsthe correct wavelength for erasure, keep the transparent window covered after the device isprogrammed.

http://www.ti.com


www.ti.com Hardware




3.3 Programming Adapter Target Connector SignalsThe target connector signals for the programming adapter ensure communication between theprogramming adapter and MSP430 MCUs and supply low energy to systems without extra supplysources.

Figure 9 and Figure 10 show the target connector signals for the programming adapter.

Figure 9. 25-Pin Sub-D at Programming Adapter

Figure 10. 14-Pin Connector at End of Interconnect Cable

http://www.ti.com


Hardware www.ti.com




Table 7 lists the target connector signals and describes their requirement statuses and functions.

Table 7. Target Connector Signal Functions

Signal Required CommentTMS Mandatory Test mode select functions according to IEEE1149.1TCK Mandatory Test clock functions according to IEEE1149.1

TDI/VPP Mandatory Test data input functions according to IEEE1149.1, but with additional programmingvoltage for 3xx devices.

TDO/TDI Mandatory Test data output functions according to IEEE1149.1, but additional data input is usedwhen programming voltage is applied by TDI/VPP.

GND Mandatory GND is the most negative terminal.

VCC_MSPMandatory (if

internal supplyvoltage is used)

Voltage source is used with MSP430 MCUs or PWBs. The voltage level is set bysoftware.

XOUT Mandatory Signal supplies the MSP430 system with clock signals.RST/NMI Optional If not connected, RST/NMI must be held high.

Test/VPPMandatory

(depending ondevice)

Signal used to select pin or JTAG function or to apply VPP

The output signal levels of the programming adapter are near GND or VCC_MSP.• The RST/NMI terminal of the device must be high; otherwise, the access to the device through JTAG

system may fail.• The programming procedure (handling of the SW) is described in Chapters 1 and 2 of this manual.• The connections from the MSP430 terminals must follow EMI rules, such as short lines and ground

planes. If TMS line receives one negative pulse by EMI strike, the fuse current is activated (with fuseversion 1.0). The fuse current flows from TDI(/VPP) pin to GND (or VSS).

Table 8. Programming Adapter Signal Levels

Signal Signal LevelTMS VSS or VCC_MSPTCK VSS or VCC_MSP

TDI/VPP VSS or VCC_MSP or VPPTDO/TDI VSS or VCC_MSP

XOUT VSS or VCC_MSPRST/NMI VSS or VCC_MSPTest/VPP VSS or VCC_MSP or VPP

http://www.ti.com


www.ti.com Hardware




3.4 MSP-PRGS430 Circuit DiagramsSee Section 5 for the MSP-PRGS430 circuit diagrams.

3.5 Location of Components on MSP-PRGS430Figure 11 shows the locations of the components.

NOTE: Do not use J2 pin 9 as RST/NMI pullup.

Figure 11. MSP-PRGS430 Components

http://www.ti.com


Hardware www.ti.com




3.6 Interconnection of MSP-PRGS430 to OTP or EPROM-Based MSP430 DevicesThe circuit diagram in Figure 12 shows the connections required to program OTP (MSP430Pxxx) andEPROM (MSP430Exxx) based MSP430 MCUs with the MSP-PRGS430 programming adapter. Consultthe device data sheet for the specific device location of the supply and JTAG pins. Ensure that all positiveand negative supply pins are connected together.

Figure 12. MSP-PRGS430 Used to Program OTP or EPROM-Based MSP430 Devices

The RST/NMI terminal on the MSP430 MCU has to be held high by an external resistor during access ofthe device through JTAG. In a noisy environment, consider using an additional capacitor from RST/NMI toVSS.

NOTE: The example schematic shows a system where the target voltage is supplied by the MSP-PRGS430. For in-system programming with an external supply voltage, do not connect pin 2of the JTAG connector. In this case, the supply voltage setting in the PRGS430 must beadjusted to the external supply voltage level. The TEST/VPP connection is only required onlower pin-count devices with multiplexed JTAG pins.

http://www.ti.com


www.ti.com Hardware




3.7 Interconnection of MSP-PRGS430 to Flash-Based MSP430 DevicesThe circuit diagram in Figure 13 shows the connections required to program flash-based MSP430 MCUs(MSP430Fxxx) with the MSP-PRGS430 programming adapter. Consult the device data sheet for thespecific device location of the power supply and JTAG pins. Ensure that all positive and negative powersupply pins are connected together.

The signal TEST/VPP is only required on lower pin-count devices with multiplexed JTAG pins. In thiscase, special attention must be given to the circuit design around the four JTAG pins (TDO/TDI, TDI, TMS,and TCK), because they are shared between the applications hardware and the JTAG interface used byprogramming adapter.

Figure 13. MSP-PRGS430 Used to Program Flash-Based MSP430 Devices

NOTE: The example schematic shows a system where the target voltage is supplied by the MSP-PRGS430. For in-system programming with an external supply voltage, do not connect pin 2of the JTAG connector. In this case, the PRGS430 supply voltage setting must be adjustedto the external supply voltage level. The TEST/VPP connection is only required on lower pin-count devices with multiplexed JTAG pins.

http://www.ti.com


Hex Object Format www.ti.com




4 Hex Object FormatThis section describes the hex object format.

4.1 Intel-Hex Object FormatThe Intel-hex object format supports 16-bit addresses and consists of a nine-character (four field) prefixthat defines the start of record, byte count, load address, record type, and a two character sumchecksuffix.

The two record types, which are represented in the nine-character prefix, are described below:

00 = Data record (begins with the colon start character)

01 = End-of-file record

Record type 00, the data record, begins with the colon (:) start character and is followed by the byte count,the address of the first data byte, the record type (00), and the sumcheck. The sumcheck is the 2scomplement (in binary) of the preceding bytes in the record, including the byte count, address, and databytes.

Record type 01, the end-of-file record, also begins with the colon (:) start character. The colon is followedby the byte count, address, record type (01), and sumcheck.

Figure 14. Intel-Hex Object Format

http://www.ti.com


www.ti.com Hex Object Format




4.2 TI-TXT File FormatThe TI-TXT file format used by the tool is shown as follows:@ADDR1DATA01 DATA02 ........ DATA16DATA17 DATA32 ........ DATA32

........DATAm ........DATAn@ADDR2DATA01 .................... DATAnq

Where@ADDR is the start address of a section (hexadecimal)DATAn represents a data byte (hexadecimal)q is the termination of the file

Example@F00031 40 00 03 B2 40 80 5A 20 01 D2 D3 22 00 D2 E321 00 3F 40 E8 FD 1F 83 FE 23 F9 3F@FFFE00 F0Q

Restrictions:• The number of sections is unlimited.• The start address must be even.• Each line must have 16 data bytes, except the last line of a section.• Data bytes are separated by a single space.• The termination tag q indicates end-of-file is mandatory.

5 SchematicsThis following figures show the schematic diagrams for the serial programming adapter.

http://www.ti.com


Schematics www.ti.com




Figure 15. Schematics (1 of 2)

http://www.ti.com


www.ti.com Schematics




Figure 16. Schematics (2 of 2)

http://www.ti.com


Revision History www.ti.com



Revision History

Revision HistoryNOTE: Page numbers for previous revisions may differ from page numbers in the current version.

Changes from July 27, 2009 to October 8, 2018 ............................................................................................................. Page

• Formatting and editorial changes throughout document ............................................................................. 1

http://www.ti.com


STANDARD TERMS FOR EVALUATION MODULES1. Delivery: TI delivers TI evaluation boards, kits, or modules, including any accompanying demonstration software, components, and/or

documentation which may be provided together or separately (collectively, an “EVM” or “EVMs”) to the User (“User”) in accordancewith the terms set forth herein. User's acceptance of the EVM is expressly subject to the following terms.1.1 EVMs are intended solely for product or software developers for use in a research and development setting to facilitate feasibility

evaluation, experimentation, or scientific analysis of TI semiconductors products. EVMs have no direct function and are notfinished products. EVMs shall not be directly or indirectly assembled as a part or subassembly in any finished product. Forclarification, any software or software tools provided with the EVM (“Software”) shall not be subject to the terms and conditionsset forth herein but rather shall be subject to the applicable terms that accompany such Software

1.2 EVMs are not intended for consumer or household use. EVMs may not be sold, sublicensed, leased, rented, loaned, assigned,or otherwise distributed for commercial purposes by Users, in whole or in part, or used in any finished product or productionsystem.

2 Limited Warranty and Related Remedies/Disclaimers:2.1 These terms do not apply to Software. The warranty, if any, for Software is covered in the applicable Software License

Agreement.2.2 TI warrants that the TI EVM will conform to TI's published specifications for ninety (90) days after the date TI delivers such EVM

to User. Notwithstanding the foregoing, TI shall not be liable for a nonconforming EVM if (a) the nonconformity was caused byneglect, misuse or mistreatment by an entity other than TI, including improper installation or testing, or for any EVMs that havebeen altered or modified in any way by an entity other than TI, (b) the nonconformity resulted from User's design, specificationsor instructions for such EVMs or improper system design, or (c) User has not paid on time. Testing and other quality controltechniques are used to the extent TI deems necessary. TI does not test all parameters of each EVM.User's claims against TI under this Section 2 are void if User fails to notify TI of any apparent defects in the EVMs within ten (10)business days after delivery, or of any hidden defects with ten (10) business days after the defect has been detected.

2.3 TI's sole liability shall be at its option to repair or replace EVMs that fail to conform to the warranty set forth above, or creditUser's account for such EVM. TI's liability under this warranty shall be limited to EVMs that are returned during the warrantyperiod to the address designated by TI and that are determined by TI not to conform to such warranty. If TI elects to repair orreplace such EVM, TI shall have a reasonable time to repair such EVM or provide replacements. Repaired EVMs shall bewarranted for the remainder of the original warranty period. Replaced EVMs shall be warranted for a new full ninety (90) daywarranty period.

3 Regulatory Notices:3.1 United States

3.1.1 Notice applicable to EVMs not FCC-Approved:FCC NOTICE: This kit is designed to allow product developers to evaluate electronic components, circuitry, or softwareassociated with the kit to determine whether to incorporate such items in a finished product and software developers to writesoftware applications for use with the end product. This kit is not a finished product and when assembled may not be resold orotherwise marketed unless all required FCC equipment authorizations are first obtained. Operation is subject to the conditionthat this product not cause harmful interference to licensed radio stations and that this product accept harmful interference.Unless the assembled kit is designed to operate under part 15, part 18 or part 95 of this chapter, the operator of the kit mustoperate under the authority of an FCC license holder or must secure an experimental authorization under part 5 of this chapter.3.1.2 For EVMs annotated as FCC – FEDERAL COMMUNICATIONS COMMISSION Part 15 Compliant:

CAUTIONThis device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may notcause harmful interference, and (2) this device must accept any interference received, including interference that may causeundesired operation.Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority tooperate the equipment.

FCC Interference Statement for Class A EVM devicesNOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 ofthe FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment isoperated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if notinstalled and used in accordance with the instruction manual, may cause harmful interference to radio communications.Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required tocorrect the interference at his own expense.

FCC Interference Statement for Class B EVM devicesNOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 ofthe FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residentialinstallation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordancewith the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interferencewill not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, whichcan be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or moreof the following measures:

• Reorient or relocate the receiving antenna.• Increase the separation between the equipment and receiver.• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.• Consult the dealer or an experienced radio/TV technician for help.

3.2 Canada3.2.1 For EVMs issued with an Industry Canada Certificate of Conformance to RSS-210 or RSS-247

Concerning EVMs Including Radio Transmitters:This device complies with Industry Canada license-exempt RSSs. Operation is subject to the following two conditions:(1) this device may not cause interference, and (2) this device must accept any interference, including interference that maycause undesired operation of the device.

Concernant les EVMs avec appareils radio:Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitationest autorisée aux deux conditions suivantes: (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doitaccepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.

Concerning EVMs Including Detachable Antennas:Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser)gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users, the antenna typeand its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary forsuccessful communication. This radio transmitter has been approved by Industry Canada to operate with the antenna typeslisted in the user guide with the maximum permissible gain and required antenna impedance for each antenna type indicated.Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibitedfor use with this device.

Concernant les EVMs avec antennes détachablesConformément à la réglementation d'Industrie Canada, le présent émetteur radio peut fonctionner avec une antenne d'un type etd'un gain maximal (ou inférieur) approuvé pour l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillageradioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotroperayonnée équivalente (p.i.r.e.) ne dépasse pas l'intensité nécessaire à l'établissement d'une communication satisfaisante. Leprésent émetteur radio a été approuvé par Industrie Canada pour fonctionner avec les types d'antenne énumérés dans lemanuel d’usage et ayant un gain admissible maximal et l'impédance requise pour chaque type d'antenne. Les types d'antennenon inclus dans cette liste, ou dont le gain est supérieur au gain maximal indiqué, sont strictement interdits pour l'exploitation del'émetteur

3.3 Japan3.3.1 Notice for EVMs delivered in Japan: Please see http://www.tij.co.jp/lsds/ti_ja/general/eStore/notice_01.page 日本国内に

輸入される評価用キット、ボードについては、次のところをご覧ください。http://www.tij.co.jp/lsds/ti_ja/general/eStore/notice_01.page

3.3.2 Notice for Users of EVMs Considered “Radio Frequency Products” in Japan: EVMs entering Japan may not be certifiedby TI as conforming to Technical Regulations of Radio Law of Japan.

If User uses EVMs in Japan, not certified to Technical Regulations of Radio Law of Japan, User is required to follow theinstructions set forth by Radio Law of Japan, which includes, but is not limited to, the instructions below with respect to EVMs(which for the avoidance of doubt are stated strictly for convenience and should be verified by User):1. Use EVMs in a shielded room or any other test facility as defined in the notification #173 issued by Ministry of Internal

Affairs and Communications on March 28, 2006, based on Sub-section 1.1 of Article 6 of the Ministry’s Rule forEnforcement of Radio Law of Japan,

2. Use EVMs only after User obtains the license of Test Radio Station as provided in Radio Law of Japan with respect toEVMs, or

3. Use of EVMs only after User obtains the Technical Regulations Conformity Certification as provided in Radio Law of Japanwith respect to EVMs. Also, do not transfer EVMs, unless User gives the same notice above to the transferee. Please notethat if User does not follow the instructions above, User will be subject to penalties of Radio Law of Japan.

http://www.tij.co.jp/lsds/ti_ja/general/eStore/notice_01.page


【無線電波を送信する製品の開発キットをお使いになる際の注意事項】開発キットの中には技術基準適合証明を受けていないものがあります。技術適合証明を受けていないもののご使用に際しては、電波法遵守のため、以下のいずれかの措置を取っていただく必要がありますのでご注意ください。1. 電波法施行規則第6条第1項第1号に基づく平成18年3月28日総務省告示第173号で定められた電波暗室等の試験設備でご使用

いただく。2. 実験局の免許を取得後ご使用いただく。3. 技術基準適合証明を取得後ご使用いただく。

なお、本製品は、上記の「ご使用にあたっての注意」を譲渡先、移転先に通知しない限り、譲渡、移転できないものとします。上記を遵守頂けない場合は、電波法の罰則が適用される可能性があることをご留意ください。日本テキサス・イ

ンスツルメンツ株式会社東京都新宿区西新宿６丁目２４番１号西新宿三井ビル

3.3.3 Notice for EVMs for Power Line Communication: Please see http://www.tij.co.jp/lsds/ti_ja/general/eStore/notice_02.page電力線搬送波通信についての開発キットをお使いになる際の注意事項については、次のところをご覧ください。http://www.tij.co.jp/lsds/ti_ja/general/eStore/notice_02.page

3.4 European Union3.4.1 For EVMs subject to EU Directive 2014/30/EU (Electromagnetic Compatibility Directive):

This is a class A product intended for use in environments other than domestic environments that are connected to alow-voltage power-supply network that supplies buildings used for domestic purposes. In a domestic environment thisproduct may cause radio interference in which case the user may be required to take adequate measures.

4 EVM Use Restrictions and Warnings:4.1 EVMS ARE NOT FOR USE IN FUNCTIONAL SAFETY AND/OR SAFETY CRITICAL EVALUATIONS, INCLUDING BUT NOT

LIMITED TO EVALUATIONS OF LIFE SUPPORT APPLICATIONS.4.2 User must read and apply the user guide and other available documentation provided by TI regarding the EVM prior to handling

or using the EVM, including without limitation any warning or restriction notices. The notices contain important safety informationrelated to, for example, temperatures and voltages.

4.3 Safety-Related Warnings and Restrictions:4.3.1 User shall operate the EVM within TI’s recommended specifications and environmental considerations stated in the user

guide, other available documentation provided by TI, and any other applicable requirements and employ reasonable andcustomary safeguards. Exceeding the specified performance ratings and specifications (including but not limited to inputand output voltage, current, power, and environmental ranges) for the EVM may cause personal injury or death, orproperty damage. If there are questions concerning performance ratings and specifications, User should contact a TIfield representative prior to connecting interface electronics including input power and intended loads. Any loads appliedoutside of the specified output range may also result in unintended and/or inaccurate operation and/or possiblepermanent damage to the EVM and/or interface electronics. Please consult the EVM user guide prior to connecting anyload to the EVM output. If there is uncertainty as to the load specification, please contact a TI field representative.During normal operation, even with the inputs and outputs kept within the specified allowable ranges, some circuitcomponents may have elevated case temperatures. These components include but are not limited to linear regulators,switching transistors, pass transistors, current sense resistors, and heat sinks, which can be identified using theinformation in the associated documentation. When working with the EVM, please be aware that the EVM may becomevery warm.

4.3.2 EVMs are intended solely for use by technically qualified, professional electronics experts who are familiar with thedangers and application risks associated with handling electrical mechanical components, systems, and subsystems.User assumes all responsibility and liability for proper and safe handling and use of the EVM by User or its employees,affiliates, contractors or designees. User assumes all responsibility and liability to ensure that any interfaces (electronicand/or mechanical) between the EVM and any human body are designed with suitable isolation and means to safelylimit accessible leakage currents to minimize the risk of electrical shock hazard. User assumes all responsibility andliability for any improper or unsafe handling or use of the EVM by User or its employees, affiliates, contractors ordesignees.

4.4 User assumes all responsibility and liability to determine whether the EVM is subject to any applicable international, federal,state, or local laws and regulations related to User’s handling and use of the EVM and, if applicable, User assumes allresponsibility and liability for compliance in all respects with such laws and regulations. User assumes all responsibility andliability for proper disposal and recycling of the EVM consistent with all applicable international, federal, state, and localrequirements.

5. Accuracy of Information: To the extent TI provides information on the availability and function of EVMs, TI attempts to be as accurateas possible. However, TI does not warrant the accuracy of EVM descriptions, EVM availability or other information on its websites asaccurate, complete, reliable, current, or error-free.




6. Disclaimers:6.1 EXCEPT AS SET FORTH ABOVE, EVMS AND ANY MATERIALS PROVIDED WITH THE EVM (INCLUDING, BUT NOT

LIMITED TO, REFERENCE DESIGNS AND THE DESIGN OF THE EVM ITSELF) ARE PROVIDED "AS IS" AND "WITH ALLFAULTS." TI DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, REGARDING SUCH ITEMS, INCLUDING BUTNOT LIMITED TO ANY EPIDEMIC FAILURE WARRANTY OR IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT OF ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADESECRETS OR OTHER INTELLECTUAL PROPERTY RIGHTS.

6.2 EXCEPT FOR THE LIMITED RIGHT TO USE THE EVM SET FORTH HEREIN, NOTHING IN THESE TERMS SHALL BECONSTRUED AS GRANTING OR CONFERRING ANY RIGHTS BY LICENSE, PATENT, OR ANY OTHER INDUSTRIAL ORINTELLECTUAL PROPERTY RIGHT OF TI, ITS SUPPLIERS/LICENSORS OR ANY OTHER THIRD PARTY, TO USE THEEVM IN ANY FINISHED END-USER OR READY-TO-USE FINAL PRODUCT, OR FOR ANY INVENTION, DISCOVERY ORIMPROVEMENT, REGARDLESS OF WHEN MADE, CONCEIVED OR ACQUIRED.

7. USER'S INDEMNITY OBLIGATIONS AND REPRESENTATIONS. USER WILL DEFEND, INDEMNIFY AND HOLD TI, ITSLICENSORS AND THEIR REPRESENTATIVES HARMLESS FROM AND AGAINST ANY AND ALL CLAIMS, DAMAGES, LOSSES,EXPENSES, COSTS AND LIABILITIES (COLLECTIVELY, "CLAIMS") ARISING OUT OF OR IN CONNECTION WITH ANYHANDLING OR USE OF THE EVM THAT IS NOT IN ACCORDANCE WITH THESE TERMS. THIS OBLIGATION SHALL APPLYWHETHER CLAIMS ARISE UNDER STATUTE, REGULATION, OR THE LAW OF TORT, CONTRACT OR ANY OTHER LEGALTHEORY, AND EVEN IF THE EVM FAILS TO PERFORM AS DESCRIBED OR EXPECTED.

8. Limitations on Damages and Liability:8.1 General Limitations. IN NO EVENT SHALL TI BE LIABLE FOR ANY SPECIAL, COLLATERAL, INDIRECT, PUNITIVE,

INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES IN CONNECTION WITH OR ARISING OUT OF THESETERMS OR THE USE OF THE EVMS , REGARDLESS OF WHETHER TI HAS BEEN ADVISED OF THE POSSIBILITY OFSUCH DAMAGES. EXCLUDED DAMAGES INCLUDE, BUT ARE NOT LIMITED TO, COST OF REMOVAL ORREINSTALLATION, ANCILLARY COSTS TO THE PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, RETESTING,OUTSIDE COMPUTER TIME, LABOR COSTS, LOSS OF GOODWILL, LOSS OF PROFITS, LOSS OF SAVINGS, LOSS OFUSE, LOSS OF DATA, OR BUSINESS INTERRUPTION. NO CLAIM, SUIT OR ACTION SHALL BE BROUGHT AGAINST TIMORE THAN TWELVE (12) MONTHS AFTER THE EVENT THAT GAVE RISE TO THE CAUSE OF ACTION HASOCCURRED.

8.2 Specific Limitations. IN NO EVENT SHALL TI'S AGGREGATE LIABILITY FROM ANY USE OF AN EVM PROVIDEDHEREUNDER, INCLUDING FROM ANY WARRANTY, INDEMITY OR OTHER OBLIGATION ARISING OUT OF OR INCONNECTION WITH THESE TERMS, , EXCEED THE TOTAL AMOUNT PAID TO TI BY USER FOR THE PARTICULAREVM(S) AT ISSUE DURING THE PRIOR TWELVE (12) MONTHS WITH RESPECT TO WHICH LOSSES OR DAMAGES ARECLAIMED. THE EXISTENCE OF MORE THAN ONE CLAIM SHALL NOT ENLARGE OR EXTEND THIS LIMIT.

9. Return Policy. Except as otherwise provided, TI does not offer any refunds, returns, or exchanges. Furthermore, no return of EVM(s)will be accepted if the package has been opened and no return of the EVM(s) will be accepted if they are damaged or otherwise not ina resalable condition. If User feels it has been incorrectly charged for the EVM(s) it ordered or that delivery violates the applicableorder, User should contact TI. All refunds will be made in full within thirty (30) working days from the return of the components(s),excluding any postage or packaging costs.

10. Governing Law: These terms and conditions shall be governed by and interpreted in accordance with the laws of the State of Texas,without reference to conflict-of-laws principles. User agrees that non-exclusive jurisdiction for any dispute arising out of or relating tothese terms and conditions lies within courts located in the State of Texas and consents to venue in Dallas County, Texas.Notwithstanding the foregoing, any judgment may be enforced in any United States or foreign court, and TI may seek injunctive reliefin any United States or foreign court.

Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265Copyright © 2018, Texas Instruments Incorporated

IMPORTANT NOTICE AND DISCLAIMER

TI PROVIDES TECHNICAL AND RELIABILITY DATA (INCLUDING DATASHEETS), DESIGN RESOURCES (INCLUDING REFERENCEDESIGNS), APPLICATION OR OTHER DESIGN ADVICE, WEB TOOLS, SAFETY INFORMATION, AND OTHER RESOURCES “AS IS”AND WITH ALL FAULTS, AND DISCLAIMS ALL WARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION ANYIMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT OF THIRDPARTY INTELLECTUAL PROPERTY RIGHTS.These resources are intended for skilled developers designing with TI products. You are solely responsible for (1) selecting the appropriateTI products for your application, (2) designing, validating and testing your application, and (3) ensuring your application meets applicablestandards, and any other safety, security, or other requirements. These resources are subject to change without notice. TI grants youpermission to use these resources only for development of an application that uses the TI products described in the resource. Otherreproduction and display of these resources is prohibited. No license is granted to any other TI intellectual property right or to any thirdparty intellectual property right. TI disclaims responsibility for, and you will fully indemnify TI and its representatives against, any claims,damages, costs, losses, and liabilities arising out of your use of these resources.TI’s products are provided subject to TI’s Terms of Sale (www.ti.com/legal/termsofsale.html) or other applicable terms available either onti.com or provided in conjunction with such TI products. TI’s provision of these resources does not expand or otherwise alter TI’s applicablewarranties or warranty disclaimers for TI products.

Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265Copyright © 2018, Texas Instruments Incorporated

http://www.ti.com/legal/termsofsale.html

http://www.ti.com

Documents

MSP430™ Microcontroller Serial Programming Adapter · Delivery: TI delivers TI evaluation boards, kits, or modules, including any accompanying demonstration software, components,