Similarly to Launchpad Development Kits, there are a few common reasons that the connection to a controlCARD does not work. To determine which of these steps are relevant, see the How to test your JTAG connection with CCS link for Test Connection instructions. Before using the following the steps, disconnect any external hardware from the controlCARD.

1. If the log from Test Connection mentions that the host PC cannot communicate with the debug probe, try the following steps when using the onboard debug probe:
   1. Try changing the USB cable and make sure that the correct debug probe is selected in the Target Configuration file.
   2. Check the hardware switches on the controlCARD which select if JTAG signals are coming from the onboard debug probe or the docking station. This information is in the controlCARD User's Guide, which is usually linked on the TI.com store page for the controlCARD.
   3. If the Test Connection log still indicates that communication with the debug probe is not established, there is a possibility that the controlCARD is damaged.
2. If the Test Connection log indicates that communication with the debug probe is still not established, try the following steps if you are using a standalone debug probe:
   1. Try changing the USB cable to the debug probe.
   2. If the Test Connection log still indicates that communication with the debug probe is not established, there is a possibility that the debug probe is damaged.
3. If the log from the Test Connection indicates that the debug probe cannot circulate bits or that the IR or DR paths are broken, try the following steps:
   1. Check the hardware switches on the controlCARD to see if any disable the JTAG connection. This information is in the controlCARD User's Guide, which is usually linked on the TI.com store page for the controlCARD.
   2. If the Test Connection log still denotes that the debug probe cannot circulate bits, there is a possibility that the controlCARD is damaged.
4. If the log from Test Connection indicates that the test has passed, but code cannot load to the device, try the following steps:
   1. Use the switches on the controlCARD to put the device in wait boot mode. If the connection is successful using the Manual Launch instructions, then the error was likely something in the flashed code that was preventing the connection.
   2. If the connection still cannot be established, or if the connection succeeds but code cannot be loaded, the it is possible that the device is locked.