Hello, everyone. On this video, we would like to present a high-level knowledge about using the MSP-FET debug probe with MSP432 devices.

The MSP-FET is a powerful emulation development tool, often called a debug probe, which allows users to quickly begin application development on MSP low-power microcontrollers, or MCUs. Creating MCU software usually requires downloading the binary firmware image to the MSP device for validation and debugging. The MSP-FET provides a debug communication pathway between a host computer and the target MSP.

On this video, we would like to cover these topics-- MSP-FET hardware ecosystem, software development ecosystem, and the programming ecosystem. Afterwards, we'll discuss about how to use the MSP-FET with MSP432 devices. The last part, we will show you a demo example-- how to program the MSP432 target device with MSP-FET using Code Composer Studio.

From a hardware perspective, MSP-FET supports debugging and programming for all MSP430 Flash and FRAM devices with the following debug communication protocols available-- JTAG 4-wire, and TI proprietary Spy-Bi-Wire. It also supports MSP432 target devices. The protocols available are the JTAG 4-wire and Serial-Wire-Debug, or SWD. For the MSP432 devices, the MSP-FET 432 adapter is required.

The other features that MSP-FET offers are the adjustable target power supply in a range from 1.8 to 3.6 volts at 100 milliamps, the capability to detect the external power supply, overcurrent protection and detection, backchannel UART with and without handshake, JTAG speed of up to 10 megahertz for MSP432, and the EnergyTrace feature.

MSP-FET is compatible with the following IDEs and software development environments-- CCS Desktop and CCS Cloud, EW430 and EW-ARM by IAR Systems, and GCC. Many features that are supported by MSP-FET are code download, factory reset, debug interface secure, debugging capabilities such as applying breakpoints, performing single steps, viewing the files and [? our ?] [? core ?] registers, and setting data watchpoints.

The EnergyTrace, EnergyTrace+, and EnergyTrace++ support are now available for the MSP430 device. The EnergyTrace and EnergyTrace+ support are now available for MSP432 devices.

MSP-FET can be used as a pure programming tools using the following software. MSP Flasher and CCS UniFlash are now compatible to program the MSP432 devices by using the backchannel UART in MSP-FET. The MSP-FET also supports the UART and I2C bootloader communication with BSL Scripter. At the end of this presentation, we will provide you the link to the documentations of each tool mentioned here.

I've told you general knowledge about the MSP-FET ecosystem. We would like to mention the optional software [? that's ?] [? capable ?] for MSP432 debugging and programming using the MSP-FET-- Code Composer Studio version 6.1.3 or higher with MSP430 and 432 support installed, EW-ARM version 7.70.1 or higher with TI MSP432P401x support installed, MSP Flasher version 1.3.10.0 or higher, CCS Cloud, and BSL Scripter version 3.01.00.00 or higher.

As mentioned in the hardware ecosystem section before, we need the MSP-FET 432 adapter that supports the JTAG and SWD debug protocols. This hardware tool offers you the 10- and 20-pin ARM standard connection. Other than that, it can switch between MSP-FET or an external power supply.

On this demo example, we would like to show you how we are using CCS and MSP-FET to program and debug the MSP432 device that we have on the target socket board. In a new workspace, go to File and choose New CCS Project. On the text field of Target Device, write MSP432, and then choose MSP432P401r. For your connection, choose the [? MSP432 ?] USB 1 to communicate with the attached MSP-FET. Give the project name. And here we name it [? blink_led. ?]

Under the Project Templates and Examples, choose the basic examples [? Blink ?] the LED. You'll get a new project set up in the workspace. Build the project to create the .out file that will be programmed to the device. Once the build is complete, click the Debug button. Then the programming is executed, and the debug session starts. You can see the blink LED program is downloaded, and you can debug the device through the CCS.

Here we'll list the links that might be useful for you to get more information for each tools that were mentioned on this video. If you have any further questions, please use the E2E forum in www.e2e.ti.com. Thank you for watching this video.