• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 53 subscribers
  • Views 934 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CCS/CC1310: The XDS110 stopped working with CCS

CCS/MSP432P401R: The XDS110 and MSPFET stopped working with CCS 9.3

miha
Intellectual 960 points

Part Number: MSP432P401R

Tool/software: Code Composer Studio

Hi,

Today I've upgraded to CCS 9.3(os X).

After this I've tried to program my device with XDS110, I was prompt a firmware upgrade and I accepted.

Unfortunately, XDS110 stopped working with error: 

CS_DAP_0: Error connecting to the target: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the ReadMe.txt file there for instructions. (Emulation package 8.4.0.00006) 

I've tried also with MSPFET and is the same, the only difference is the error: Interface error..


What can I do? When I plug XDS110 the device is not detected anymore..  updating the firmware in the console is also not possible :/
Tried also on windows..

How can I solve this problem?

Thank you for your help

  • 0
    TI__Guru**** 171074 points

    Hi,

    Error 260fro the XDS110 is described in detail in the Debugging JTAG page below (search for the error number):

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

    miha said:
    What can I do? When I plug XDS110 the device is not detected anymore..  updating the firmware in the console is also not possible :/

    Tried also on windows..

    Does the MSP-FET work on the Windows host? If not, there is probably something in common between the two Debug Probes that may be failing. USB cable perhaps? 

    Otherwise, can you try the Troubleshooting section options in the XDS110 page on Windows? Specifically the procedure to reinstall the Device Drivers and re-flash the bootloader. 

    https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html 

    At this point those are your best options. Please report back if there are still issues.

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 960 points

    Hi,
    I've tried to flash the XDS110, but I'm not able to put it in the DFU Mode.

    I've connected the TDO pin to the ground without any success.

    There was also another LaunchPad that I had.. and I've tried to upgrade it while it was still detected by the windows.
    After the upgrade the XDS110 it's not.

    I really don't know what to trie anymore. I have MSP432 in mass production and I need to program them.

    Thank you for your help. 

    Miha


    Unfortunately

    desouza said:

    Hi,

    Error 260fro the XDS110 is described in detail in the Debugging JTAG page below (search for the error number):

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

    miha
    What can I do? When I plug XDS110 the device is not detected anymore..  updating the firmware in the console is also not possible :/

    Tried also on windows..

    Does the MSP-FET work on the Windows host? If not, there is probably something in common between the two Debug Probes that may be failing. USB cable perhaps? 

    MSP fet is working on windows.

    Otherwise, can you try the Troubleshooting section options in the XDS110 page on Windows? Specifically the procedure to reinstall the Device Drivers and re-flash the bootloader. 

    https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html 

    At this point those are your best options. Please report back if there are still issues.

    Regards,

    Rafael

  • 0 in reply to miha
    TI__Guru**** 171074 points

    Miha,

    I am sorry to hear about the issues. Let me recap the steps and see if I missed something. 

    - In macOS you were prompted to update the firmware after installing CCSv9.3. After that, the XDS110 failed to be properly acknowledged. You tried MSP-FET and it did not work as well.

    - Connecting the XDS110 in Windows failed to be acknowledged by the OS (Control Panel). Does this happen with the MSP-FET as well? (I am trying to find a common root cause)

    - Momentarily connecting the TM4C129 pin 97 (TDO) to GND during power up (connecting to USB) did not change this scenario - i.e., Control Panel still does not acknowledge the connection. Did you remove the connection from TDO to GND after plugging the USB? That is known to cause defects on the TM4C129 device. 

    - You tried another Launchpad and updated its firmware. At that point the XDS110 was not acknowledged anymore by Windows. Was the firmware updated from macOS or from Windows? (I am trying to find the exact configuration that is triggering the problem) 

    Are all these OSes running natively or is there Virtual Machines involved (VmWare, VirtualBox, Parallels, etc.)? Some of these methods of directly interfacing with hardware are known to be flaky in these environments. 

    At this moment I don't recall having a series of reports that are triggered by macOS, XDS110 and CCSv9.3 upgrades, thus reducing the chances of being something intrinsic to the tools. 

    Regards,

    Rafael