This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS5 connection problem

My CCS5 keep throwing error "Error connecting to the target" when I try to launch a debug session, the only way to correct this is to complete log off and log in again, then retart CCS5, then everything works fine until my target is reset.

I tried to close CCS and restart, that didn't fix the issue, have to completely log off, so sounds like there's a background process that is holding off something. Anyone knows how to fix this problem, I can live with restarting CCS if I have to, but completely log off is really too much trouble.

I'm using CCS5 on a stellaris micro.

  • Hai,

    Which PC O/S are you running under, WinXP/WIn7/Linux(which)?

    Which emulator are you using, and which Stellaris MCU is your target processor?

    This error message is generic and happens under a lot of circumstances. You have probably already gone through this list of recovery attempts, but there are what I usually do in this case:

    1. CCS reset of the device (CPU or system or whatever is available for the target)

    2. Emulator reset through CCS

    3. Terminate the Target Configuration and re-launch it

    4. Try 1-3 in every order possible

    5. Terminate the Target Configuration, power cycle the target board, then re-launch the Target Configuration

    6. Terminate the TC, power off the board, disconnect both ends of the JTAG pod and power it off, re-power JTAG and re-attach it, power on the board, re-launch the TC

    7. #6 with emulator and system resets through CCS

    8. #6 or #7 and close CCS while everything is off then restart CCS and continue #6 or #7

    9. All of the above and reboot the PC

    It is very rare that rebooting the PC is required, and it is rare that CCS has to be closed.

    The key step that I find helping in many cases is in step #6 where the JTAG is disconnected and powered off. The power from the JTAG header can keep power applied to some logic in the target device, and that can prevent the target device from completely power cycling. So a complete disconnection can help get the target device into a good state.

    Also, the error of connecting to the target can be caused by the JTAG pod getting into a bad state because of the device getting into a bad state, so power cycling it or giving it an Emulator Reset can help this problem.

    Regards,
    RandyP