XDS110 fail to connect each time on CCS V6.1

Hi,

I get the exact same error if my CC2650 SensorTag board is not powered up. Can you double-check if that is the case?

Hope this helps,
Rafael

Yes.when I disconnect the debbuger from power next time I try to run on debug mode I get this message and need to make DFU.Is someone from TI can check it please?

Hi,

Let me clarify a few details:

- when you plug your SensorTag DevPack on the USB, what is the output of xdsdfu -e? Mine shows:

xdsdfu said:

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

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

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x1cbe    PID: 0x00ff
Device Name:   Tiva Device Firmware Update
Manufacturer:  Texas Instruments Incorporated
Serial Num:    00000000
Mode:          DFU

Found 1 device.

- do you need to run xdsdfu every time you connect your SensorTAG DevPack to your PC? If so, what are the sequence of commands you need to run before you are able to perform a successful connection? This should not be necessary, but I wonder if something is wrong with the hardware of your DevPack.

Regards,

Rafael

When I run the command xdsdfu -e

I get this format:

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

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

and every time I take the power out of the Sensor Tag DVPACK and connect again . Then I try torun debbug mode. I get this error:

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 5.1.641.0)

So I point to the xdsdfu folder and do what is written in the read me file attach.

first xdsdfu -m

and then xdsdfu -f firmware.bin -r

At the end of the process I get this log 

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

Scanning USB buses for supported XDS110 devices...

Downloading firmware.bin to device...

F:\ti\ccsv6\ccs_base\common\uscif\xds110>

Then it can do the debbug.

Is there an idea waht is wrong then?

Bar.

Bar,

Bar Strauss1 said:

and every time I take the power out of the Sensor Tag DVPACK and connect again . Then I try torun debbug mode

I really can't reproduce this here. Just to be sure the procedure I am trying matches whatever you are doing, please check the short clip below.

I am able to connect without problems and, at about 30s in the video I power cycle the SensorTag by removing and replacing its battery and then I am able to connect it again. I leave the DevPack connected to the PC.

Are you doing a similar procedure? If so, then it is possible your module or SensorTag or DevPack may be presenting some failure. If not, can you please try whatever I am doing and see if you are getting the same error?

Hope this helps,

Rafael

Hi Rafael.

I don't do exactly what you do:

1. I don't familiar with the command xdsdfu -e. I use xdsdfu -m and xdsdfu -f firmware.bin -r ? Is there a diffrents?

2. I power the DV-Pack with the Sensor Tag on it from the USB and not use the battery. So also when I disconnect I disconnect them both from power. I was assume taht the DV FW is place on a FLASH and don't need to reprogramming every power connect. Isn't so?

3. I see taht after you connect again the Tag Sensor to the battery and want to run debug gain you active the cmd and again send the dxsdfu -e command. Way you need it every time if the DV connect all the time to the power. This procedure  complicate a lot the process for running debug. Is it must?

Regards

Bar.

Bar,

1. The command "xdsdfu -e" is just to list what are the available xds110 devices plugged on my PC. If the utility returns what is shown in the clip, the XDS110 is properly recognized by Windows and ready to connect. The procedure you are following is re-writing the firmware to the XDS110 flash memory, which is only necessary if there is a firmware update available.

2.1 Perhaps that is the issue. I am using the battery to power the SensorTag, as instructed in step 2 of the small instructions leaflet that is provided with the SensorTag DevPack. When I need to power cycle the SensorTag I use the small plastic tab to momentarily disconnect the battery.
2.2 You are right; the DevPack holds its contents in Flash memory, therefore there is no need to reprogram it every time.

3. This step is not needed at all. I just showed it so you could see that Windows was able to properly recognize the DevPack after a power cycle. In a normal operation you would simply connect to the SensorTag using CCS (no cmd needed)

In summary: leave the battery on the SensorTag and power cycle it using the plastic tab when needed. I am almost sure that is the root cause of the bad connection you are experiencing.

Hope this helps,
Rafael

Hi Rafael.

Thanks for youyr answers.

And what about disconnect the DVPack from usb and reinstall? Does it still hold the FW? Can you chack it?

Regards

Bar.

I am having the same problem with a custom board.

Error connecting to the target: (Error -1265 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 6.0.83.0)

This is after

reset device by unplugging from usb

plug into usb

reinstall xds110 drivers

reload firmware

Has this been resolved, as I have the same with Windows 7

This might seem crazy, but I found that I needed to have the power plugged into my laptop in order for this to work.
If I tried to operate the debugger with my laptop running on batteries, the XDS110 was non-functional or not reliably functional.

Hi!

I am using a mac, and having the same problem.

• Host OS: OSX El Capitan 10.11.6
• CCS Version: 6.2
• Device: TI Simplelink SensorTag DevPack CC2650

Doesn't matter if I use CCS Cloud or CCS 6.2 native on my mac. Same issue. The device is running, I can connect to it via the iPhone app, etc. 

I've been trying to do the xdsdfu -m command in terminal, but I get a "command not found" response. Steps:

1. Open Terminal
2. Type "cd /Applications/ti/ccsv6/ccs_base/common/uscif/xds110", hit enter
3. Type "xdsdfu -m", hit enter

There don't seem to be any mac-specific instructions, so this is pretty confusing. Perhaps that command doesn't work in terminal?

Thanks!

J

Update: I have been able to run "xdsdfu -m" - had to use a PC in order to do so. I got a similar device not found issue. I've tried multiple configurations of debugger + sensortag, or just debugger alone. Connected to computer via micro usb to usb, and the light comes on as expected. I even opened CCS, went to my target configurations, and tested the connection. I got:

"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."