SLAU678C March   2016  – November 2022

 

  1.   Abstract
  2.   Trademarks
  3. 1Getting Started
    1. 1.1 Introduction
    2. 1.2 Key Features
    3. 1.3 What's Included
      1. 1.3.1 Kit Contents
      2. 1.3.2 Software Examples
    4. 1.4 First Steps: Out-of-Box Experience
      1. 1.4.1 Connecting to the Computer
      2. 1.4.2 Running the Out-of-Box Demo
        1. 1.4.2.1 Live Temperature Mode
        2. 1.4.2.2 FRAM Data Log Mode
        3. 1.4.2.3 SD Card Data Log Mode
    5. 1.5 Next Steps: Looking Into the Provided Code
  4. 2Hardware
    1. 2.1 Block Diagram
    2. 2.2 Hardware Features
      1. 2.2.1 MSP430FR5994 MCU
      2. 2.2.2 eZ-FET Onboard Debug Probe With EnergyTrace++ Technology
      3. 2.2.3 Debug Probe Connection: Isolation Jumper Block
      4. 2.2.4 Application (or Backchannel) UART
      5. 2.2.5 Special Features
        1. 2.2.5.1 microSD Card
        2. 2.2.5.2 220-mF Super Capacitor
    3. 2.3 Power
      1. 2.3.1 eZ-FET USB Power
      2. 2.3.2 BoosterPack Plug-in Module and External Power Supply
      3. 2.3.3 Super Cap (C1)
        1. 2.3.3.1 Charging the Super Cap
        2. 2.3.3.2 Using the Super Cap
        3. 2.3.3.3 Disabling the Super Cap
    4. 2.4 Measure MSP430 Current Draw
    5. 2.5 Clocking
    6. 2.6 Using the eZ-FET Debug Probe With a Different Target
    7. 2.7 BoosterPack Plug-in Module Pinout
    8. 2.8 Design Files
      1. 2.8.1 Hardware
      2. 2.8.2 Software
    9. 2.9 Hardware Change Log
  5. 3Software Examples
    1. 3.1 Out-of-Box Software Example
      1. 3.1.1 Source File Structure
      2. 3.1.2 Out-of-Box Demo GUI
      3. 3.1.3 Power Up and Idle
      4. 3.1.4 Live Temperature Mode
      5. 3.1.5 FRAM Log Mode
      6. 3.1.6 SD Card Log Mode
    2. 3.2 Blink LED Example
      1. 3.2.1 Source File Structure
    3. 3.3 BOOSTXL-AUDIO Audio Record and Playback Example
      1. 3.3.1 Source File Structure
      2. 3.3.2 Operation
    4. 3.4 Filtering and Signal Processing With LEA Reference Design Example
      1. 3.4.1 Source File Structure
      2. 3.4.2 Operation
    5. 3.5 Emulating EEPROM Reference Design Example
      1. 3.5.1 Source File Structure
      2. 3.5.2 Operation
  6. 4Resources
    1. 4.1 Integrated Development Environments
      1. 4.1.1 TI Cloud Development Tools
        1. 4.1.1.1 TI Resource Explorer Cloud
        2. 4.1.1.2 Code Composer Studio Cloud
      2. 4.1.2 Code Composer Studio™ IDE
      3. 4.1.3 IAR Embedded Workbench for MSP430
    2. 4.2 LaunchPad Websites
    3. 4.3 MSPWare and TI Resource Explorer
    4. 4.4 FRAM Utilities
      1. 4.4.1 Compute Through Power Loss (CTPL)
    5. 4.5 MSP430FR5994 MCU
      1. 4.5.1 Device Documentation
      2. 4.5.2 MSP430FR5994 Code Examples
      3. 4.5.3 MSP430 Application Notes and TI Reference Designs
    6. 4.6 Community Resources
      1. 4.6.1 TI E2E Support Forums
      2. 4.6.2 Community at Large
  7. 5FAQ
  8. 6Schematics
  9. 7Revision History

2.2.4 Application (or Backchannel) UART

The backchannel UART allows communication with the USB host that is not part of the target application's main functionality. This is very useful during development, and also provides a communication channel to the PC host side. This can be used to create graphical user interfaces (GUIs) and other programs on the PC that communicate with the LaunchPad development kit.

Figure 2-5 shows the pathway of the backchannel UART. The backchannel UART is the UART on eUSCI_A0. This UART channel is separate from the UART on the 40-pin BoosterPack plug-in module connector (eUSCI_A3).

On the host side, a virtual COM port for the application backchannel UART is generated when the LaunchPad development kit enumerates on the host. You can use any PC application that interfaces with COM ports, including terminal applications like Hyperterminal or Docklight, to open this port and communicate with the target application. You need to identify the COM port for the backchannel. On Windows PCs, Device Manager can assist (see Figure 2-6).

GUID-2F302A6F-993C-48CF-8EA0-3A48EA161156-low.pngFigure 2-6 Application Backchannel UART in Device Manager

The backchannel UART is the MSP Application UART1 (COM13) port. In this case, Figure 2-6 shows COM13, but this port can vary from one host PC to the next. Identify the correct COM port and configure it in the host application according to its documentation. Then open the port and begin communication to it from the host.

On the target MSP430FR5994 side, the backchannel is connected to the eUSCI_A0 module. The eZ-FET has a configurable baud rate; therefore, it is important that the PC application configures the baud rate to be the same as what is configured on the eUSCI_A0.