Debug Probes Hardware and Software
18
SLAU647L – July 2015 – Revised February 2018
Copyright © 2015–2018, Texas Instruments Incorporated
MSP Debuggers
Table 4. MSP-FET MSP Target BSL Activation Commands
Baud Rate
Command
9620
Set all UART or I
2
C 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 (I
2
C BSL) – debugger is disabled
400000 or 400001
BSL entry sequence and power up 3.3 V (I
2
C 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 I
2
C 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 I
2
C interface is a software I
2
C implementation, which always runs with a
speed of approximately 55 kHz. The four different speed configurations are supported for
compatibility purposes with BSL-Scripter and the BSL-Rocket.
5.6.4
LED Signals
The MSP-FET shows its operating states using two LEDs, one green and one red.
lists all
available operation modes. An
or
icon indicates that the LED is off, an
or
icon indicates that
the LED is on, and an
or
icon indicates that the LED flashes.
Table 5. MSP-FET LED Signals
Power
LED
Mode LED
Function
MSP-FET not connected to PC or MSP-FET not ready; for example, after a major firmware update.
Connect or reconnect MSP-FET to PC.
MSP-FET connected and ready
MSP-FET waiting for data transfer
Ongoing data transfer – during active debug session
An error has occurred; for example, target V
CC
over current. Unplug MSP-FET from target, and cycle the
power off and on. Check target connection, and reconnect MSP-FET.
Firmware update in progress. Do not disconnect MSP-FET while both LEDs are blinking slowly.
FPGA update in progress. Do not disconnect MSP-FET while both LEDs are blinking rapidly.
