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

5.6.3 Target BSL Connection and BSL-Scripter Support

The MSP-FET can be used for communication with the target device bootloader (BSL) through the I2C and UART protocols. The activation of the different protocols is equivalent to the MSP-FET backchannel UART. See Table 6 for command details.

The BSL-Scripter software implements support for these activation commands and performs the correct sequence according to the communication interface (UART, I2C) that is specified in the script.

In MSP-FET BSL communication mode, flow control is not available, because this is not supported by the MSP target device BSL.

UART BSL: The MSP-FET BSL UART mode supports the following baud rates: 9600, 14400, 19200, 28800, 38400, 56000, 57600, and 115200. For the BSL UART, 8 + 1 + even parity is used.

I2C BSL: The MSP-FET is always the I2C master, and the target device BSL is always the I2C slave. 7-bit I2C addressing mode is used with a fixed I2C slave address of 0x48.

NOTE

If the MSP-FET is configured to support BSL communication, debugger functionality is disabled. To switch to debugger mode, either perform a power cycle (unplug the USB cable) or configure the baud rate to 8001. The BSL mode is disabled until sending a BSL entry baud rate command.

NOTE

MSP-FET BSL I2C pullup resistors must not exceed 2-kΩ resistance.

The typical I2C clock rate is 330 kHz.

Table 6. MSP-FET MSP Target BSL Activation Commands

Baud Rate Command
9620 Set all UART or I2C pins to high impedance – no current flow into target device
9601 BSL entry sequence and power up 3.3 V (UART BSL) – debugger is disabled
100000 or 100001 BSL entry sequence and power up 3.3 V (I2C BSL) – debugger is disabled
400000 or 400001 BSL entry sequence and power up 3.3 V (I2C BSL) – debugger is disabled
9623 Power up 3.3 V
8001 Activate debugger
100002 or 400002 Configure communication and power up 3.3 V (MSP432 I2C BSL) – debugger is disabled, no BSL entry sequence
9602 Configure communication and power up 3.3 V (MSP432 UART BSL) – debugger is disabled, no BSL entry sequence

NOTE

The MSP-FET I2C interface is a software I2C implementation, which always runs with a speed of approximately 330 kHz. The four different speed configurations are supported for compatibility purposes with BSL-Scripter and the BSL-Rocket.