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.

CCS/LAUNCHXL-TMS57004: XDS100 Driver

Part Number: LAUNCHXL-TMS57004


Tool/software: Code Composer Studio

Hi, I have been using CCS on a Windows10 PC at work, debugging code fine. But now I need to do the same at home, with CCS7 running on Windows7 64.

I'm sure I have used similar 570LS3137 dev-boards on this PC, but the XDS100 driver will not pick up the Debug port.

I've tried uninstalling the drivers but with no success. Can you help, please?

  • I added a screenshot to show the Device Manager but it's not apparently loaded:

    Ports (COM...) >> XDS100 Class USB Serial Port (COM11)

    TI Debug Probes >> XDS100 Class Auxiliary Port

    USB devices >> TI Inc.XDS100 Ver 2.0 (Interface 0)

  • Hi,

    Can you compare the contents of the Control Panel with what is shown in section 2.6 of the XDS100 page below? 

    https://processors.wiki.ti.com/index.php/XDS100 

    You may need to reinstall the drivers as indicated in this section. 

    Hope this helps,

    Rafael

  • I have migrated to a standalone Windows Vista PC, and got the drivers looking as per the right-hand screen, together with its COM Port.

    But I'm still unable to set breakpoints: I can build, program and put into single step mode.

    The error message seen:

    CortexR4: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x3b4c: (Error -1066 @ 0x3B4C) Unable to set/clear requested breakpoint...

    Running a HITEX board shows the same symptoms.

    Help, please.

  • Hi,

    I don't think this severely influences this new issue, but I have to let you know that we don't test CCS and the debug probes on Windows Vista anymore, thus there is a minimal possibility there are underlying issues. 

    That said, this error is common with Flash based devices, which have a limited number of hardware breakpoints. CCS tries to setup a software breakpoint when this limit is reached, but there may be cases where this is not possible. 

    In this case, there are some breakpoints previously set by CCS when a debug session is launched - disabling them can help you keep some of them free for use. 

    Please check section 7.2.4 of the CCS User's Guide - the top options shown there mention which ones set a breakpoint. 

    https://software-dl.ti.com/ccs/esd/documents/users_guide/index.html

    Hope this helps,

    Rafael

  • Thanks. Although the Vista PC won't behave, your help has got my Windows 7 PC running breakpoints.