SPRUJH0B April   2025  – September 2025

 

  1.   1
  2.   Description
  3.   Get Started
  4.   Features
  5.   Applications
  6.   6
  7. 1Evaluation Module Overview
    1. 1.1 Introduction
    2. 1.2 Kit Contents
    3. 1.3 Specification
      1. 1.3.1 External Power Supply or Accessory Requirements
    4. 1.4 Device Information
  8. 2Hardware
    1. 2.1 Hardware Description
      1. 2.1.1 Functional Description and Connections
        1. 2.1.1.1 Power Domains
        2. 2.1.1.2 LEDs
        3. 2.1.1.3 Encoder Connectors
        4. 2.1.1.4 Boot Modes
        5. 2.1.1.5 BoosterPack Sites
        6. 2.1.1.6 Analog Voltage Reference
        7. 2.1.1.7 Other Headers and Jumpers
          1. 2.1.1.7.1 USB Isolation Block
          2. 2.1.1.7.2 Alternate Power
          3. 2.1.1.7.3 5V Step-up Converter
        8. 2.1.1.8 Programmable Gain Amplifier (PGA)
      2. 2.1.2 Debug Interface
        1. 2.1.2.1 XDS110 Debug Probe
        2. 2.1.2.2 Virtual COM Port
      3. 2.1.3 Alternate Routing
        1. 2.1.3.1 Overview
        2. 2.1.3.2 GPIO35/GPIO37 Routing
        3. 2.1.3.3 eQEP Routing
        4. 2.1.3.4 X1, X2 Routing
        5. 2.1.3.5 PWM DAC
    2. 2.2 Using the F28E12x LaunchPad
    3. 2.3 BoosterPacks
    4. 2.4 Hardware Revisions
      1. 2.4.1 Revision A
      2. 2.4.2 Revision E2
  9. 3Software
    1. 3.1 Software Development
      1. 3.1.1 Software Tools and Packages
      2. 3.1.2 F28E12x LaunchPad Demo Program
      3. 3.1.3 Programming and Running Other Software on the F28E12x LaunchPad
  10. 4Hardware Design Files
    1. 4.1 Schematic
    2. 4.2 PCB Layout
      1. 4.2.1 LAUNCHXL-F28E12X Board Dimensions
    3. 4.3 Bill of Materials (BOM)
  11. 5Additional Information
    1. 5.1 Frequently Asked Questions
    2. 5.2 Trademarks
  12. 6References
    1. 6.1 Reference Documents
    2. 6.2 Other TI Components Used in This Design
  13. 7Revision History

5.1 Frequently Asked Questions

  1. Why isn't my C2000 device getting any power even though I have the USB-C cable connected to USB1?
    1. Make sure that the USB 5V power and GND jumpers are connected (JP1).
    2. Make sure that the XDS110 5V and 3.3V power jumpers are connected (JP2).
  2. Can other programming and debug tools (such as an XDS200 debug probe) be used with the F28E12x LaunchPad?
    1. The F28E12x LaunchPad utilizes an onboard XDS110 debug probe in a 4-pin JTAG configuration.
  3. What versions of Code Composer Studio IDE can be used to develop software for the F28E12x LaunchPad?
    1. The on-board XDS110 debug probe is compatible with Code Composer Studio development environment version 6.1.0 and later.
  4. Why can't I connect to the LaunchPad in Code Composer Studio IDE?
    1. Are shunts present on J101 for TCK and TMS?
    2. Is the XDS110 and the F28E120SC MCU powered? Are LED7, LED0, LED6 and LED1 illuminated? For further details on powering the LaunchPad, see Section 2.1.1.1.
      1. If JP1 shunts are disconnected, the power provided through the USB is isolated from the rest of the board. Make sure that 3.3V or 5V is supplied to any of the available connectors on the target side of the isolation.
    3. Is the USB-C cable connected to the PCB and is the USB region receiving power? Is LED7 illuminated?
      1. The XDS region must be powered with the 5V from the USB cable. LED7 illuminates when 5V USB power is connected. The XDS-side 5V to 3.3V LDO regulator requires 5V on the USB side to generate the +3V3 rail for the XDS110 device.
    4. Make sure that the S2 switch configuration matches the target configuration being used. Open the Target Configuration file (.ccxml) in Code Composer Studio IDE. Click on the Advanced tab. In the JTAG / SWD / cJTAG mode field, if JTAG (1149.1) SWD and cJTAG are disabled is selected, make sure S2 is in JTAG TDI, TDO mode. If cJTAG (1149.7) 2-pin advanced modes is selected, any S2 configuration can be used. Alternately, a working Target configuration file is included in the launchxl_ex1_f28e12x_demo project F28E120SC.ccxml. Use this without modifications.
      LAUNCHXL-F28E12X Target Configuration Advanced Options Figure 5-1 Target Configuration Advanced Options
      LAUNCHXL-F28E12X Target Configuration Included in the Demo Project Figure 5-2 Target Configuration Included in the Demo Project
  5. Why is the serial connection not working?
    1. Are you using the correct COM port?
      1. Right click on My Computer and select Properties. Navigate to the Hardware tab in the dialog box and open the device manager. Scroll to Ports (COM & LPT) and expand this entry. Is XDS110 Class Application/User UART listed? If so, read the COM number to the right of the entry; this is the COM number to use.
    2. Are you using the correct baud rate? Most, if not all, of the examples are configured for a baud rate of 115200 when the CPU is running at 160MHz. If you have changed the PLL settings or developed your own code, you can recalculate the baud rate for your specific application. For information on how to do this, see the F28E12x Real-Time Microcontrollers Technical Reference Manual.
    3. Is the UART channel connection to the debug probe enabled and does this match the channel configured in software?
      1. The F28E12x LaunchPad provides options for customizing the use of GPIO35 and GPIO37. In this program, use GPIO35 and GPIO37 as UART signals to establish a serial connection to the debug probe. Make sure that S2 is configured to the appropriate UART channel for the application software. For details, see Section 2.1.3.2.