SPRUJC0 April   2024

 

  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 Specifications
    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  FSI
        5. 2.1.1.5  PGA
        6. 2.1.1.6  CAN
        7. 2.1.1.7  CLB
        8. 2.1.1.8  Boot Modes
        9. 2.1.1.9  BoosterPack Sites
        10. 2.1.1.10 Analog Voltage Reference Header
        11. 2.1.1.11 Other Headers and Jumpers
          1. 2.1.1.11.1 USB Isolation Block
          2. 2.1.1.11.2 BoosterPack Site 2 Power Isolation
          3. 2.1.1.11.3 Alternate Power
      2. 2.1.2 Debug Interface
        1. 2.1.2.1 XDS110 Debug Probe
        2. 2.1.2.2 XDS110 Output
        3. 2.1.2.3 Virtual COM Port
      3. 2.1.3 Alternate Routing
        1. 2.1.3.1 Overview
        2. 2.1.3.2 UART Routing
        3. 2.1.3.3 EQEP Routing
        4. 2.1.3.4 CAN Routing
        5. 2.1.3.5 PGA Routing
        6. 2.1.3.6 FSI Routing
        7. 2.1.3.7 X1/X2 Routing
        8. 2.1.3.8 PWM DAC
    2. 2.2 Using the F28P55x LaunchPad
    3. 2.3 BoosterPacks
    4. 2.4 Hardware Revisions
      1. 2.4.1 Revision A
  9. 3Software
    1. 3.1 Software Development
      1. 3.1.1 Software Tools and Packages
      2. 3.1.2 F28P55x LaunchPad Demo Program
      3. 3.1.3 Programming and Running Other Software on the F28P55x LaunchPad
  10. 4Hardware Design Files
    1. 4.1 Schematic
    2. 4.2 PCB Layout
      1. 4.2.1 LAUNCHXL-F28P55X 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

5.1 Frequently Asked Questions

  1. Can other programming and debug tools (such as an XDS200 debug probe) be used with the F28P55x LaunchPad?
    1. The F28P55x LaunchPad utilizes an on-board XDS110 debug probe in a 2-pin cJTAG configuration. cJTAG only uses the TMS and TCK pins of the debug probe. TDI and TDO are present on J101 and can be connected to a debug probe through jumper wires, if necessary.
  2. What versions of Code Composer Studio can be used to develop software for the F28P55x LaunchPad?
    1. The on-board XDS110 debug probe is compatible with Code Composer Studio development environment version 6.1.0 and later.
  3. Can users not connect to the LaunchPad in Code Composer Studio?
    1. Are shunts present on J101 for TCK and TMS?
    2. Is the XDS110 and the F28P55X MCU powered? Are LED0 and LED1 illuminated? For further details on powering the LaunchPad, see Section 2.1.1.1.
      1. If JP1 shunts are disconnected, then the power provided through the USB is isolated from the rest of the board. Make sure that 3.3V 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 USB region must be powered with the 5V from the USB cable. LED7 illuminates when 5V USB power is connected. The USB isolation chip requires 5V on the USB side to operate and pass the signals across the isolation barrier.
    4. Make sure that the target configuration is set up to use cJTAG in 2-pin advanced mode. Open the Target Configuration file (.ccxml) in Code Composer Studio. Click on the Advanced tab and select cJTAG (1149.7) 2-pin advanced modes from the drop-down labeled JTAG/SWD/cJTAG Mode. Leave the Target Scan Format as OSCAN2 format. Alternately, a working Target configuration file is included in the launcxl_ex1_F28P55X_demo project TMS320F28P55X_LaunchPad.ccxml. Users can use this without modifications.
      GUID-20240408-SS0I-8DW3-VNZK-J9R1SCP9FDZH-low.svgFigure 5-1 Target Configuration Advanced Options
      GUID-20240408-SS0I-T2ZX-R5XQ-MTMJGFSK2RBD-low.svgFigure 5-2 Target Configuration Included in the Demo Project
  4. Why is the serial connection not working?
    1. Are shunts present on J101 for TXD and RXD?
    2. 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, then read the COM number to the right of the entry; this is the COM number to be used.
    3. Is the user 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 150MHz. If the PLL settings have been changed or the user developed a code, then users have to recalculate the baud rate for the specific application. For information on how to do this, see the TMS320F28P55x C2000 Real-Time Microcontrollers technical reference manual.
    4. Does the UART channel wired to the debug probe match the UART channel configured in software?
      1. The F28P55x LaunchPad provides an option for one of two possible UART channels to be routed to the debug probe through J101. Make sure that S2 is configured to the appropriate UART channel for the application software. For details, see Section 2.1.3.2.