Frequently Asked Questions (FAQ)
22
SPRUI11B – January 2015 – Revised March 2019
Copyright © 2015–2019, Texas Instruments Incorporated
LAUNCHXL-F28069M Overview
7
Frequently Asked Questions (FAQ)
1. Can other programming and debug tools (such as an XDS510 debug probe) be used with the C2000
LaunchPad?
While a user could potentially connect an external debug probe to the F28069M device present on the
LaunchPad, it would require some rework of the board. It is recommended that users who want to use
an external debug probe purchase a controlCard and docking station that includes an external JTAG
connector.
2. What versions of Code Composer Studio can be used to develop software for the C2000 LaunchPad?
It is highly recommend that novice users develop applications with Code Composer Studio v6. The
drivers, examples, and other associated software are tailored to make the user experience as smooth
as possible in Code Composer Studio v6.
3. Why can’t I connect to the LaunchPad in Code Composer Studio?
There are a number of things that could cause this and they all have an easy fix.
•
Is S1 switch 3 in the down position?
This is the TRST pin that enables and disables JTAG functionality on the chip. This switch must be
in the up position for the debug probe to be able to connect.
•
Are both power LEDs lit?
The board has two power domains because of the isolated JTAG interface. For low-voltage
application development, JTAG isolation is not needed and the power domains can be combined to
allow for convenience (that is, the board can be powered completely through the USB). Ensure that
jumpers are placed on the posts of JP1 and JP2.
•
Are drivers correctly installed for the XDS100v2 present on the LaunchPad?
Right click on
My Computer
and select properties. Navigate to the
Hardware
tab in the dialog box
and open the device manager. Scroll to the bottom of the list and expand the
USB Serial Bus
controllers
item. Are there two entries for
TI XDS100 Channel A/B
? If not, try unplugging and
replugging in the board. Does Windows give you any messages in the system tray? In Device
Manger, do either of the entries have a yellow exclamation mark over their icon? If so, try
reinstalling the drivers.
4. Why is the serial connection not working?
The most common cause of this is the serial muxing being set incorrectly. Ensure that JP7 has a
jumper placed on it while JP6 does not have a jumper before proceeding further.
•
Are you using the correct COM port?
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 there a USB
Serial Port listed? If so, read the COM number to the right of the entry; this is the COM number you
should be using.
If the USB Serial COM Port is not identified by the computer, reprogram the XDS100v2 EEPROM
using
.
•
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 60 MHz. If you have changed the PLL settings or written your own application you may have to
recalculate the baud rate for your specific application. For information on how to do this, see the
TMS320x2802x, 2803x Piccolo serial communications interface (SCI) reference guide
.