SPRUJE5A June   2025  – August 2025

 

  1.   1
  2.   Description
  3.   Get Started
  4.   Features
  5.   5
  6. 1Evaluation Module Overview
    1. 1.1 Introduction
    2. 1.2 Kit Contents
    3. 1.3 Specifications
      1. 1.3.1 External Power Supply or Accessory Requirements
    4. 1.4 Device Information
  7. 2Software
    1. 2.1 Software Description
    2. 2.2 Software Installation
      1. 2.2.1 Install SDK
      2. 2.2.2 Install Additional Software
        1. 2.2.2.1 Install Python
        2. 2.2.2.2 Install OpenSSL
    3. 2.3 Software Development
    4. 2.4 F29H85x LaunchPad Demo Program
    5. 2.5 Programming and Running Other Software on the F29H85x LaunchPad
  8. 3Hardware
    1. 3.1 Hardware Description
      1. 3.1.1 Functional Description and Connections
        1. 3.1.1.1  Microcontroller
        2. 3.1.1.2  PMIC
        3. 3.1.1.3  Power Domains
        4. 3.1.1.4  LEDs
        5. 3.1.1.5  Encoder Connectors
        6. 3.1.1.6  FSI
        7. 3.1.1.7  CAN
        8. 3.1.1.8  SENT
        9. 3.1.1.9  CLB
        10. 3.1.1.10 Boot Modes
        11. 3.1.1.11 BoosterPack Sites
        12. 3.1.1.12 Analog Voltage Reference
        13. 3.1.1.13 Differential ADC Header
        14. 3.1.1.14 Other Headers and Jumpers
          1. 3.1.1.14.1 XDS Isolation Block
          2. 3.1.1.14.2 BoosterPack Site 2 Power Isolation
          3. 3.1.1.14.3 Alternate Power
      2. 3.1.2 Debug Interface
        1. 3.1.2.1 XDS110 Debug Probe
        2. 3.1.2.2 XDS110 Output
        3. 3.1.2.3 Virtual COM Port
      3. 3.1.3 Alternate Routing
        1. 3.1.3.1 Overview
        2. 3.1.3.2 UART Routing
        3. 3.1.3.3 EQEP Routing
        4. 3.1.3.4 CAN Routing
        5. 3.1.3.5 FSI Routing
        6. 3.1.3.6 PWM DAC
      4. 3.1.4 Hardware Revisions
        1. 3.1.4.1 Revision A
  9. 4Hardware Design Files
    1. 4.1 Schematics
    2. 4.2 PCB Layouts
      1. 4.2.1 LAUNCHXL-F29H85X Board Dimensions
    3. 4.3 Bill of Materials (BOM)
  10. 5Frequently Asked Questions
  11. 6Additional Information
    1. 6.1 Trademarks
  12. 7References
    1. 7.1 Reference Documents
    2. 7.2 Other TI Components Used in This Design
  13. 8Revision History

5 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)
      1. To avoid contention on the 5V rail, make sure that the "ENABLE +5V0 BOOST" jumper (J17) is disconnected when supplying 5V through the USB.
  2. Can other programming and debug tools (such as an XDS200 debug probe) be used with the F29H85x LaunchPad?
    1. The F29H85x LaunchPad utilizes an on-board 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 F29H85x LaunchPad?
    1. The on-board XDS110 debug probe is compatible with Code Composer Studio development environment version 20.0.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 F29H850TU9 MCU powered? Are LED1, LED7 and LED3 illuminated? For further details on powering the LaunchPad, see Section 3.1.1.3.
      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 LED1 illuminated?
      1. The XDS region must be powered with the 5V from the USB cable. LED1 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 target configuration is set up to use JTAG in 4-pin advanced mode. Open the Target Configuration file (.ccxml) in Code Composer Studio IDE. Click on the Advanced tab and select JTAG (1149.1) SWD and cJTAG are disabled. Alternately, a working Target configuration file is included in the launchxl_ex1_f29h85x_demo project "F29H850TU9.ccxml". You can use this without modifications.
      LAUNCHXL-F29H85X Target Configuration Advanced Options Figure 5-1 Target Configuration Advanced Options
      LAUNCHXL-F29H85X 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 and 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 200MHz. 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 F29H85x and F29P58x Real-Time Microcontrollers Technical Reference Manual.
    3. Does the UART channel wired to the debug probe match the UART channel configured in software?
      1. The F29H85x LaunchPad provides an option for one of two possible UART channels to be routed to the debug probe. Make sure that S2 is configured to the appropriate UART channel for the application software. For details, see Section 3.1.3.2.
  6. Why does my F29H85x LaunchPad keep resetting at random?
    1. Check if the boot mode switch (S3) is set to parallel GPIO boot. Using this boot mode when there is no host device driving the corresponding GPIO pins can cause erratic behavior, including MCU reset. S3 must be set according to the desired boot mode.