SLAU318G July   2010  – March 2016

 

  1.   MSP-EXP430G2 LaunchPad™ Development Kit
    1.     Trademarks
    2. 1 Preface: Read This First
      1. 1.1 If You Need Assistance
      2. 1.2 Related Documentation From TI
    3. 2 MSP-EXP430G2 LaunchPad™ Development Kit Overview
      1. 2.1 Overview
      2. 2.2 Features
      3. 2.3 Kit Contents
      4. 2.4 Revisions
    4. 3 Installation
      1. 3.1 Download the Required Software
      2. 3.2 Install the Software
      3. 3.3 Install the Hardware
    5. 4 Getting Started With MSP-EXP430G2 LaunchPad™ Development Kit
      1. 4.1 Getting Started
      2. 4.2 Demo Application, Internal Temperature Measurement
    6. 5 Develop an Application With the MSP-EXP430G2 LaunchPad™ Development Kit
      1. 5.1 Developing an Application
      2. 5.2 Program and Debug the Temperature Measurement Demo Application
      3. 5.3 Disconnect Emulator From Target With Jumper J3
      4. 5.4 Program Connected eZ430™ Target Boards
      5. 5.5 Connecting a Crystal Oscillator
      6. 5.6 Connecting a BoosterPack™ Plug-in Module
      7. 5.7 Supported Devices
      8. 5.8 MSP-EXP430G2 On-Board Emulator
    7. 6 MSP-EXP430G2 Hardware
      1. 6.1 Device Pinout
      2. 6.2 Schematics
      3. 6.3 PCB Layout
      4. 6.4 Bill of Materials (BOM)
    8. 7 Suggested Reading
    9. 8 Frequently Asked Questions (FAQ)
  2.   Revision History

8 Frequently Asked Questions (FAQ)

  1. Can other programming tools like the MSP-FET430UIF interface the socket device on the MSP-EXP430G2 LaunchPad development kit?

    2. The LaunchPad development kit works with any programming tool that supports the 2-wire Spy-Bi-Wire interface. Both the MSP430 USB FET (MSP-FET430UIF) and the Gang Programmer (MSP-GANG430) support these devices, but the connection must be made directly to the dedicated Spy-Bi-Wire ports. See MSP-FET430 Flash Emulation Tool User's Guide (SLAU138) for details on using MSP430 USB FET and the Gang Programmer for a 2-wire Spy-Bi-Wire interface. Do not try to connect the standard JTAG connector to the MSP-EXP430G2 pinheads, as this could result in damage to the attached hardware.

  2. Does the MSP-EXP430G2 support fuse blow?

    3. The onboard debugging interface of the MSP-EXP430G2 LaunchPad development kit lacks the JTAG security fuse-blow capability. To ensure firmware security on devices going to production, the USB Flash Emulation Tool or the Gang Production Programmer, which support the fuse-blow feature, are recommended.

  3. What versions of IAR Embedded Workbench IDE and Code Composer Studio IDE are supported?

    4. The hardware of the MSP-EXP430G2 LaunchPad development kit is supported by IAR Embedded Workbench KickStart Version 6.00 or higher and Code Composer Studio v4 or higher. To download the IDEs, visit http://www.ti.com/mspds.

  4. What are the part numbers for the connectors between the emulator board of the LaunchPad development kit and the other eZ430 target boards?

    5. Header: MALE CONN HEADER .050" 6POS PCB R/A (for example, Digi-Key: S9016E-06-ND)

    Socket: FEMALE CONN HEADER .050" 6POS PCB R/A (for example, Digi-Key: S9010E-06-ND)

  5. I am not able to select the MSP430 Application UART and cannot receive data.

    6. Ensure that the Application UART driver is correctly installed. This is done by installing either IAR Embedded Workbench or Code Composer Studio v4.

    To determine if the driver is correctly installed:

    a. Plug in the MSP-EXP430G2 LaunchPad development kit with the included mini USB cable.

    b. Right click My Computer and select Properties.

    c. Select the Hardware tab and click on Device Manager.

    d. Under Ports (COM & LPT) should be an entry for "MSP430 Application UART (COM xx)".

    If the entry is there, but no characters are received, reconnect the LaunchPad development kit to the PC and restart the application to reload the drivers. If the Application UART is not listed, install the driver by following the instructions in Section 3.2.

    If the application UART is installed but not receiving UART data, ensure that the jumpers on J3 are configured for the proper UART communication. The two UART jumpers are configured vertically for a software (SW) UART, and horizontally for a hardware (HW) UART. The application implementation and J3 jumpers should match for UART data to be properly transmitted.

  6. The device is not answering to any communication, JTAG or UART.

    7. If you are experiencing difficulties in communicating to the attached MSP430 target device, even though all the communication drivers for the MSP-EXP430G2 are loaded correctly, the emulator is probably set to a wrong communication state. This can be fixed by reconnecting the LaunchPad development kit and restarting the communicating application. Also make sure that all the jumpers on J3 are connected properly between the emulator and the target device. On revision 1.5 and newer, the orientation of the UART jumpers must align with the software implementation on the target device.

  7. I soldered the 32-kHz crystal to the board and the oscillation is not starting.

    8. The capability of the MSP430 MCU to drive the low-frequency crystal is limited, because this MCU is designed for low-power applications. To ensure proper operation, the load on these pins must be as small as possible, the matching capacitors (12.5 pF for 32.768 kHz) for the crystal must be soldered to the board, and the resistors R28 and R29 must be removed. Measuring the frequency of the oscillation with an oscilloscope typically disturbs the oscillation.

  8. The power consumption of the board is much higher than specified in the device data sheet, or I am not measuring a current at all.

    9. The MSP430 MCU in the socket of the LaunchPad development kit can be powered with an external power supply at header J6 or J4. To measure the power consumption in this mode, the VCC jumper, usually used to measure the power consumption, must be removed, and the current must be measured directly at the power supply. If the jumper J3 is not removed, the emulator circuitry of the LaunchPad development kit is powered as well. Measuring the current consumption during a debug session is not possible, because the cross current through the JTAG connection influences the measurement. The most accurate results are achieved with all jumpers on J3 removed. If the measurement is still not matching the data sheet parameters, make sure that the code is aligned with all the power saving recommendations on the website MSP430™ - The World's Lowest Power MCU.

    LaunchPad development kit revisions 1.3 and 1.4 come with R34 populated. The 47-kΩ resistor is used as a pullup for the button S2. If the port P1.3 is driven to ground, as suggested to keep the power consumption down, the pullup resistor generates an additional current of approximately 77 µA. To reduce the power consumption, the port should stay in input mode or the resistor should be removed if button S2 is not used. The internal pullup of the MSP430G2xx can be used instead.