SLAU647O July   2015  – April 2020

 

  1.   MSP Debuggers
    1.     Trademarks
    2. 1 Introduction
      1. 1.1 Related Documentation From Texas Instruments
      2. 1.2 Terms and Abbreviations
      3. 1.3 If You Need Assistance
    3. 2 MSP Debug Probe Overview
      1. 2.1 Known Limitations
    4. 3 Hardware Identification
      1. 3.1 How to Determine If Your Hardware is Based on eZ-FET or eZ-FET Lite
      2. 3.2 How to Determine If Your Hardware is Based on eZ430
      3. 3.3 Signal Connections for In-System Programming and Debugging
      4. 3.4 Using the Power Supply Feature of the eZ-FET and eZ-FET Lite
      5. 3.5 Using the Power Supply Feature of the MSP-FET430UIF and MSP-FET
    5. 4 Hardware Installation
      1. 4.1 MSP-FET430PIF
      2. 4.2 MSP-FET430UIF, MSP-FET, eZ-FET, and eZ-FET Lite
      3. 4.3 eZ430-Based Experimenter Boards and LaunchPad Kits
      4. 4.4 Hardware Installation Using the MSP Flasher
      5. 4.5 Hardware Installation Using CCS Cloud
    6. 5 Debug Probes Hardware and Software
      1. 5.1  MSPDebugStack
      2. 5.2  Ultra-Low-Power (ULP) Debug Support
      3. 5.3  EnergyTrace™ Technology
      4. 5.4  Unlimited Software Breakpoints in Flash, FRAM, and RAM
      5. 5.5  JTAG Access Protection (Fuse Blow)
      6. 5.6  MSP-FET Stand-Alone Debug Probe
        1. 5.6.1 General Features
        2. 5.6.2 Backchannel UART
          1. 5.6.2.1 UART Backchannel Activation Commands
        3. 5.6.3 Target BSL Connection and BSL-Scripter Support
        4. 5.6.4 LED Signals
        5. 5.6.5 Hardware
          1. 5.6.5.1 JTAG Target Connector
          2. 5.6.5.2 MSP-FET Pin States After Power Up
          3. 5.6.5.3 MSP-FET HID Cold Boot
          4. 5.6.5.4 Schematics
            1. 5.6.5.4.1 MSP-FET Rev 2.5 Schematics
            2. 5.6.5.4.2 MSP-FET Rev 1.2 Schematics
        6. 5.6.6 Specifications
          1. 5.6.6.1 Hardware
          2. 5.6.6.2 MSP430 MCUs
          3. 5.6.6.3 SimpleLink MSP432 MCUs
      7. 5.7  MSP-FET430UIF Stand-Alone Debugger
        1. 5.7.1 General Features
        2. 5.7.2 LED Signals
        3. 5.7.3 Hardware
          1. 5.7.3.1 JTAG Target Connector
          2. 5.7.3.2 Pin States After Power Up
          3. 5.7.3.3 Schematics
      8. 5.8  eZ-FET and eZ-FET Lite Onboard Emulation
        1. 5.8.1 General Features
        2. 5.8.2 Backchannel UART
          1. 5.8.2.1 eZ-FET and eZ-FET Lite UART Backchannel Activation Commands
        3. 5.8.3 LED Signals
        4. 5.8.4 Hardware
          1. 5.8.4.1 JTAG Target Connector
          2. 5.8.4.2 Connecting MSP-FET to LaunchPad Development Kit
          3. 5.8.4.3 Pin States After Power Up
          4. 5.8.4.4 Schematics
            1. 5.8.4.4.1 eZ-FET Rev 1.2 Schematics
            2. 5.8.4.4.2 eZ-FET Lite Schematics
            3. 5.8.4.4.3 eZ-FET Rev 1.4 Schematic
            4. 5.8.4.4.4 eZ-FET Rev 2.0 ET Schematics
      9. 5.9  eZ430 Onboard Emulation
        1. 5.9.1 General Features
        2. 5.9.2 Backchannel UART
        3. 5.9.3 Hardware
          1. 5.9.3.1 JTAG Target Connector
          2. 5.9.3.2 Pin States After Power Up
          3. 5.9.3.3 Schematics
      10. 5.10 MSP-FET430PIF
        1. 5.10.1 General Features
        2. 5.10.2 Schematics
  2.   Revision History

4.2 MSP-FET430UIF, MSP-FET, eZ-FET, and eZ-FET Lite

NOTE

The built-in DC-DC converter of the MSP-FET and eZ-FET emulators causes a load-dependent amount of ripple on the output voltage (fripple = 1 kHz to 50 kHz, Vrms_ripple = 5 mV to 50 mV), which might affect sensitive analog and RF circuits that are supplied by the emulator. For such sensitive circuits, TI recommends temporarily increasing the amount of power supply decoupling used during development, using an emulator with an integrated linear regulator (MSP-FET430UIF or eZ-FET430), or using a separate bench supply.

eZ-FET 2.0 supports LDO mode and can be used for development purposes.

Installation steps for the MSP-FET430UIF, MSP-FET, eZ-FET or eZ-FET Lite:

  1. Install the IDE (TI CCS or IAR EW430) before connecting the debug probe to the PC. During IDE installation, the USB drivers for the debug probes are installed automatically. Make sure to use the latest IDE version; older versions might install USB drivers that do not recognize the connected debug probe.
  2. Connect the debug probe to a USB port on the PC using the provided USB cable.
  3. The following procedure applies to operation under Windows:
    1. After connecting to the PC, the debug probe should be recognized automatically, as the USB device driver has been already installed together with the IDE.
    2. However, if the driver is not automatically detected, the "Found New Hardware wizard" starts. Follow the instructions and point the wizard to the driver files.

      3. The default location for CCS is: c:\ti\ccsv6\ccs_base\emulation\drivers\msp430\USB_CDC.

      The default location for IAR Embedded Workbench is: <Installation Root>\Embedded Workbench x.x\430\drivers\<Win_OS>.

  4. The following procedure applies to operation under Linux:
    • Installation as root
      1. If installing TI CCS as root, make sure that the debug probe is not connected to the computer during installation.
      2. If you start installation with the debug probe connected to the computer, disconnect the probe and reconnect after installation finishes.
    • Installation as user
      1. If installing TI CCS without root access, install the debug probe UDEV rules manually after the CCS TI installation has finished.
      2. Make sure that the debug probe is disconnected from the computer during this step.
      3. Open the shell and go to: <CSS installation directory>/ccsv7/install_scripts.sh
      4. Execute msp430uif_install.sh as sudo.
      5. Connect the debug probe and make sure that the debug probe is detected as other than "modem". Use the dmseg command to check the system log.
      6. The debug probe is ready for use.
  5. After connecting the debug probe to a PC, the probe performs a self-test. If the self-test passes, the green LED stays on. For a complete list of LED signals, see the LED Signals section of each debug probe in Section 5.6 through Section 5.8.
  6. Connect the debug probe with the target board using the 14-pin ribbon cable.
  7. When using a target socket board, make sure that the MSP430 MCU is properly inserted in the socket and that pin 1 of the device (indicated with a circular indentation on the top surface) aligns with the "1" mark on the PCB.

NOTE

To use the debug probe without an IDE, install the stand-alone driver package. The stand-alone driver installer can be found at www.ti.com/mspds under the heading MSPDS-USB-DRIVERS.