8 Frequently Asked Questions (FAQ)

1. Can other programming and debug tools (such as an XDS510 debug probe) be used with the C2000 LaunchPad?
2. What versions of Code Composer Studio can be used to develop software for the C2000 LaunchPad?
   • While a user could potentially connect an external debug probe to the F28377S 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.
   • 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?
   • 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.

   • 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 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 TMS320F2837xS Delfino Microcontrollers Technical Reference Guide (SPRUHX5).

5. Why is my program operating at half the frequency of what I expected?
   • By default many of the controlSUITE examples are configured to operate on hardware which has a different clocking circuit, where the external clock is 20 MHz instead of 10 MHz as found on this EVM.
   • A compiler switch was added to various functions to allow a user to change the clocking configuration based on the status of a predefined symbol.
   • To ensure the PLL is correctly configured for the LAUNCHXL-F28379D, Add "_LAUNCHXL_F28377S" to the predefined symbols list.
   • Access the Predefined symbols list by accessing the Project Properties, Navigating to Build » C2000 Compiler » Advanced Options » Predefined Symbols.