SPRUJ32 October   2022

 

  1.   C2000 F280013x Series LaunchPad Development Kit
  2.   Trademarks
  3. 1Board Overview
    1. 1.1 Kit Contents
    2. 1.2 Features
    3. 1.3 Specifications
      1. 1.3.1 External Power Supply or Accessory Requirements
    4. 1.4 Using the F280013x LaunchPad™
    5. 1.5 BoosterPack™ Plug-in Modules
    6. 1.6 Hardware Revisions
      1. 1.6.1 Revision A
  4. 2Software Development
    1. 2.1 Software Tools and Packages
    2. 2.2 F280013x LaunchPad™ Demo Program
    3. 2.3 Programming and Running Other Software on the F280013x LaunchPad™
  5. 3Hardware Description
    1. 3.1 Functional Description and Connections
      1. 3.1.1 Microcontroller
      2. 3.1.2 Power Domains
      3. 3.1.3 LEDs
      4. 3.1.4 Encoder Connectors
      5. 3.1.5 CAN
      6. 3.1.6 Boot Modes
      7. 3.1.7 BoosterPack™ Sites
      8. 3.1.8 Analog Voltage Reference Header
      9. 3.1.9 Other Headers and Jumpers
        1. 3.1.9.1 USB Isolation Block
        2. 3.1.9.2 BoosterPack™ Site 2 Power Isolation
        3. 3.1.9.3 Alternate Power
    2. 3.2 Debug Interface
      1. 3.2.1 XDS110 Debug Probe
      2. 3.2.2 XDS110 Output
      3. 3.2.3 Virtual COM Port
    3. 3.3 Alternate Routing
      1. 3.3.1 Overview
      2. 3.3.2 UART Routing
      3. 3.3.3 EQEP Routing
      4. 3.3.4 CAN Routing
      5. 3.3.5 SPI Routing
      6. 3.3.6 X1/X2 Routing
      7. 3.3.7 PWM DAC
  6. 4Board Design
    1. 4.1 Schematic
    2. 4.2 PCB Layout
    3. 4.3 BOM
    4. 4.4 LAUNCHXL-F2800137 Board Dimensions
  7. 5Frequently Asked Questions (FAQs)
  8. 6References
    1. 6.1 Reference Documents
    2. 6.2 Other TI Components Used in This Design
  9. 7Revision History

5 Frequently Asked Questions (FAQs)

  1. Can other programming and debug tools (such as an XDS200 debug probe) be used with the F280013x LaunchPad?
    1. The F280013x 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 tJ101 and can be connected to a debug probe through jumper wires, if necessary.
  2. What versions of Code Composer Studio IDE can be used to develop software for the F280013x LaunchPad?
    1. The on-board XDS110 debug probe is compatible with Code Composer Studio IDE version 6.1.0 and later.
  3. 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 F2800137 MCU powered? Are LED0 and LED1 illuminated? See Section 3.1.2 for further details on powering the LaunchPad.
      1. If JP1 shunts are disconnected, the power provided through the USB is isolated from the rest of the board. Make sure that 3.3 V 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 5 V from the USB cable. LED7 illuminates when 5-V USB power is connected. The USB isolation chip requires 5 V 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 the Code Composer Studio IDE. 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_F2800137_demo project "TMS320F2800137_LaunchPad.ccxml". You can use this without modifications.

       

      GUID-20211229-SS0I-S1B9-HCG5-RWR81Q219JJ7-low.png Figure 5-1 Target Configuration Advanced Options
      GUID-20211229-SS0I-LHR3-HWCV-8JT7L0J9XV5J-low.png Figure 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 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 you use.
    3. 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 100 MHz. If you have changed the PLL settings or developed your own code, you have to recalculate the baud rate for your specific application. For information on how to do this, see the TMS320F280013x 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 F280013x 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. See Section 3.3.2 for details.