Why isn't my C2000 device getting any power even though I have the USB-C cable
connected to USB1?
Make sure that the USB 5-V power and GND jumpers are
connected (JP1).
Make sure that "ENABLE
+3V3 LDO" jumper header (J16) is populated with a jumper. This generates
the 3.3-V rail for the board from the 5-V USB power.
To avoid
contention on the 5-V rail, make sure that the "ENABLE +5V0
BOOST" jumper (J17) is disconnected when supplying 5 V through
the USB.
Can other programming and debug tools (such as an XDS200 debug probe) be used
with the F28P65x LaunchPad?
The F28P65x LaunchPad utilizes an on-board XDS110 debug probe in a 4-pin
JTAG configuration.
What versions of Code Composer Studio IDE can be used to
develop software for the F28P65x LaunchPad?
The on-board XDS110 debug
probe is compatible with Code Composer Studio development environment
version 6.1.0 and later.
Why can't I connect to the LaunchPad in Code Composer Studio
IDE?
Are shunts present on J101 for TCK and TMS?
Is the XDS110 and the F28P650DK9 MCU powered? Are LED1,
LED7, LED3 and LED6 illuminated? For further details on powering the
LaunchPad, see Section 3.1.2.
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 or 5 V is
supplied to any of the available connectors on the target side
of the isolation.
Is the USB-C cable connected to the PCB and is the USB
region receiving power? Is LED1 illuminated?
The XDS region
must be powered with the 5 V from the USB cable. LED1
illuminates when 5-V USB power is connected. The XDS-side 5-V to
3.3-V LDO regulator requires 5-V on the USB side to generate the
+3V3 rail for the XDS110 device.
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_f28p65x_demo
project "TMS320F28P650DK9.ccxml". You can use this without
modifications.
Figure 5-1 Target
Configuration Advanced Options
Figure 5-2 Target
Configuration Included in the Demo Project
Why is the serial connection not working?
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 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.
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 200 MHz. 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 TMS320F28P65x C2000 Real-Time
Microcontrollers Technical Reference Manual.
Does the UART channel wired to the debug probe match
the UART channel configured in software?
The F28P65x
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.3.2.