Instruction/ maintenance manual of the product MSP430 Texas Instruments
Go to page of 53
July 2009 User ’ s G uide SLAU048H.
EV ALUA TION BOARD/KIT IMPORT ANT NOTICE T exas Instruments (TI) provides the enclosed product(s) under the following conditions:. This evaluation board/kit is intended for use for ENGINEERING DEVELOPMENT , DEMONSTRA TION, OR EV ALUA TION PURPOSES ONL Y and is not considered by TI to be a finished end−product fit for general consumer use.
EVM W ARNINGS AND RESTRICTIONS It is important to operate this EVM within the specified input and output ranges described in the EVM User ’s Guide. Exceeding the specified input range may cause unexpected operation and/or irreversible damage to the EVM.
.
T rademarks v Read This First Preface About This Manual This document describes the MSP430-family hardware, operation, and software installation and setup.
FCC Warning vi FCC Warning This evaluation board/kit is intended for use for ENGINEERING DEVELOPMENT , DEMONSTRA TION, OR EV ALUA TION PURPOSES O NL Y and is not considered by TI to be a finished end-product fit for general consumer use.
Running Title—Attribute Reference vii Chapter Title—Attribute Reference 1 Installation and Setup 1-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.
Running Title—Attribute Reference viii 1−1 ADT430 Program Icons 1-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1−2 Serial Programming Adapter 1-3 . . . . .
1-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.
Installing the Software 1-2 1.1 Installing the Software T o install the MSP-PRGS430 software, perform the following steps: NOTE: T o ensure that you are using the latest version of the MSP-PRGS430 software, you must download the installation executable from the TI web site.
Installing the Hardware 1-3 Installation and Setup 1.2 Installing the Hardware T o 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.
1-4.
2-1 Operation This chapter describes the programming procedure for MSP430 devices and the error messages you may encounter during the procedure. T opic Page 2.1 Software/Hardware Layers of the PRGS430 Environment 2-2 . . . .
Software/Hardware Layers of the PRGS430 Environment 2-2 2.1 Software/Hardware Layers of the PRGS430 Environment PRGS430.EXE PRGS430.INI PRGS430.DLL CommandLine MSP430 DEVICE.
Programming MSP430 Devices With the GUI 2-3 Operation 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 o n the Program Device icon during the installation-selected program group (default: ADT430).
Programming MSP430 Devices With the GUI 2-4 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.
Programming MSP430 Devices With the GUI 2-5 Operation T able 2−1. MSP430 Function Buttons and Descriptions (Continued) Button Name Sub-Functions Description V erify the data in the MSP430 device according to the selected option.
Programming MSP430 Devices With the GUI 2-6 2.2.3 Error Messages One of the following messages may show up if JT AG communication is not established correctly: If the MSP430 device to program can not be found, the message shown in Figure 2−2 appears.
Programming MSP430 Devices With the GUI 2-7 Operation Figure 2−5. Data Error.
Programming MSP430 Devices With the GUI 2-8 T able 2−2. Error Messages Error T ype Error Message Communication Communication failed! Communication Adapter not connected! Communication Synchronizatio.
Content of PRGS430.ini File 2-9 Operation 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.
Command Line Options 2-10 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 Th e PRGS430.ini file options are used if they are not specified in the command line.
Command Line Options 2-1 1 Operation T able 2−3. Command Line Options (Continued) Options for Program Command: /PE:{0,1,2} Option program with erase (flash only) 0: Without erase 1: Main and Info me.
2-12 2.3.2 Return V alues/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 0 Ok 2 Communica.
PRGS430.DLL—Description 2-13 Operation 2.4 PRGS430.DLL—Description The PRGS430.dll is used to communicate with the MSP−PRGS430 hardware and the connected MSP430 device. Th e initialization of the PRGS430 should be done with the following sequence: InitCom SetDeviceT ype SetV CC .
PRGS430.DLL—Description 2-14 /FN0004/ InitT arget long int InitT arget(char* lpszDeviceName) Initializes the JT AG access to the target device, detects the device type, and reports when the detected device does not match the parameter DeviceName passed.
PRGS430.DLL—Description 2-15 Operation 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.
PRGS430.DLL—Description 2-16 /FN0009/ EraseCheckFile long int EraseCheckFile(char* lpszFileName, long int iFileT ype) This function checks if all memory addresses, which are in the file, are erased.
PRGS430.DLL—Description 2-17 Operation /FN00012/ V erifyFile long int V erifyFile(char* lpszFileName, long int iFileT ype) This function checks if the memory contents of the target device are equal to the file contents.
PRGS430.DLL—Description 2-18 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 Allow.
PRGS430.DLL—Description 2-19 Operation 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.
PRGS430.DLL—Description 2-20 Example: lFuncReturn = ReadOutData(long:0xF000, long:0x1000, void* lpBuffer) /FN0019/ ReadOutFile long int ReadOutFile(long int wStart, long int wLength, char* lpszFileName, long int iFileT ype) Reads out data from the device and writes it to a file wStart: Start address of the area to be read out.
PRGS430.DLL—Description 2-21 Operation /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 .
PRGS430.DLL—Description 2-22 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.
PRGS430.DLL—Description 2-23 Operation 2.4.1 Return V alues/Error Codes From PRGS430.DLL Status Return V alue Comment OK 0 SUCCESS −1 Operation OK ERR_COMMUNICA TION −2 Communication error (SSP).
2-24.
3-1 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.
Specifications 3-2 3.1 Specifications The specifications for the MSP430 hardware are shown in T able 3−1. T able 3−1. MSP430 Hardware Specifications T emperature range 10 ° C–45 ° C Humidity 40%–70% Power supply 14 V–20 V , 200 mA minimum Dimensions 150 mm (W) × 30 mm (H) × 95 mm (D) 3.
Programming Adapter T arget Connector Signals 3-3 Hardware 3.3 Programming Adapter T arget 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.
Programming Adapter T arget Connector Signals 3-4 T able 3−2. T arget Connector Signal Functions Signal/T erminal Name Required Function/Comment TMS Mandatory T est mode select functions according to IEEE1 149.1 TCK Mandatory T est clock functions according to IEEE1 149.
MSP-PRGS430 Circuit Diagrams 3-5 Hardware 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.
Interconnection of MSP-PRGS430 to OTP/EPROM-Based 3-6 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 .
Interconnection of MSP−PRGS430 to Flash-Based MSP430 Devices 3-7 Hardware 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 .
3-8.
A-1 Hex Object Format This appendix discusses the hex object format. T opic Page A.1 Intel-Hex Object Format A-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2 TI-TXT File Format A-3 .
Intel-Hex Object Format A-2 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.
TI-TXT File Format A-3 Hex Object 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 ................
A-4.
B-1 Schematics This appendix contains the schematic diagrams for the serial programming adapter . Appendix B.
B-2.
B-3 Schematics.
B-4.
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.
An important point after buying a device Texas Instruments MSP430 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Texas Instruments MSP430 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Texas Instruments MSP430 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Texas Instruments MSP430 you will learn all the available features of the product, as well as information on its operation. The information that you get Texas Instruments MSP430 will certainly help you make a decision on the purchase.
If you already are a holder of Texas Instruments MSP430, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Texas Instruments MSP430.
However, one of the most important roles played by the user manual is to help in solving problems with Texas Instruments MSP430. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Texas Instruments MSP430 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
