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.

connect to the XDS110 failed

Hi,

I haven't been able to solve this for some time now.

I've followed suggestions in this forum but still nothing works.

I tried reinstalling everything, still nothing.

When I connect the sensortagDevPack, it doesn't appear in the Driver Manager

C:\ti\ccsv6\ccs_base\common\uscif\xds110>xdsdfu -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...


Found 0 devices.

also tried at

C:\ti\ccs_base\common\uscif\xds110>

xdsdfu -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...


Found 0 devices.

I've installed the latest XDS Emulation Software Package. Still nothing

Tried to debug in CCS... failed as expected

Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
Cortex_M3_0: Failed Board Reset 
IcePick_C: Error connecting to the target: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: invalid firmware update, invalid XDS110 serial number, or faulty USB connection. 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 6.0.14.5)

I don't know what else should I try doing. Suggestions? or I'm missing something here?

Thanks,

Adila

  • Hi,

    Noradila Nordin said:
    When I connect the sensortagDevPack, it doesn't appear in the Driver Manager

    By that you mean you don't see the entries below?

    If so, I would suspect the USB cable, the port or the DevPack itself are faulty. You can try to re-connect to different USB ports or change the cable.

    Also, do you see a green LED lit on your devpack? That could be another indicative of a faulty board.

    Regards,

    Rafael

  • Hi Rafael,

    Yes I don't see the entries.

    I tried several USB cables and different USB ports. Still nothing

    I can see the green LED lit on the devpack. So it most probably faulty board?

    Thanks,

    Adila

  • Adila,

    I am really short of ideas on this issue, given the fact Windows completely refuses to recognize the pod.

    As a last resort, can you try to force a reinstall the XDS110 drivers? From a command prompt, do the following:

    cmd_prompt said:

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\user>cd \ti\ccsv6\ccs_base\emulation\windows

    C:\ti\ccsv6\ccs_base\emulation\windows>DPInst64.exe /f /path .\xds110_drivers

    After that, unplug and re-plug the sensortag and see if Control Panel recognizes the pod.

    Hope this helps,

    Rafael

  • Hi Rafael,

    Still nothing. 

    It does say the "drivers were successfully installed"

    Is there anything else that you think I should try to solve this?

    I tried plugging on another laptop, it doesn't detect it as well

    Thanks,

    Adila

  • Adila,

    With all the tests you reported, I can't help but think your Devpack is really broken. I would either return it (if purchased recently) or buy another one (I don't think the cost of repair is lower than a brand new).

    Regards,

    Rafael

  • Hi Rafael,

    Turns out the fault is with my cables. I tried with 3 cables and all 3 had failed me - those cables only work with phones, not with sensortag it seems

    I only found this out when a colleague of mine tried it using his cable.

    It might be a good idea to have the cable included with the DevPack in the future

    Thanks,

    Adila

  • Adila,

    Hah, I got this problem as well in the past - several USB cables provided with phones only have the wires to provide USB power, not data. I now clearly put a marker on them saying "power only" to avoid confusion.

    In any case, thanks for reporting this! It will surely help others in the future.

    Best regards,

    Rafael