LAUNCHXL-CC1350: xds110 bricked?

Davide Giovanelli

Part Number: LAUNCHXL-CC1350
Other Parts Discussed in Thread: CC1350, CC2650

Hello,

I'm setting up an development environment for the cc1350 and the cc2650 based on openocd and arm-none-eabi-gdb.

On the cc2650 it works, on the cc1350 launchpads I had few problems (probably unrelated to this), and during an attempt to fix it, I upgraded the xds110 firmware (to the version 3.something), but then openocd stopped working. This is the error it shown up.

Error: JTAG tap: cc13x0.jrc  expected 1 of 1: 0x0b9be02f (mfg: 0x017 (Texas Instruments), part: 0xb9be, ver: 0x0)

After a while I though that probably the wrong ID was due to the xds110 firmware v3, so I tried to install an older fiwmare in the xds110 (I found it in an old instance of ccs I had installed a couple of years ago). However, after the update (I've done it using xdsdfu), the device looks bricked. I don't see any activity when I plug the usb, and the windows Device Manager don't react when I plug it.

Moreover, since I was not happy with this, I tried the same procedure on the cc2650 launchpad (that was working) with the same result, the device i no more accessible...

So, did I brick the debuggers? Can I do something to fix?

Thank you,

Davide.

over 5 years ago

0 Alexis Crandall20 over 5 years ago

TI__Genius 15590 points

Hi Davide,

Can you try using SmartRF Studio and seeing if it recognizes the device? It may also reinstall the XDS110 drivers. This is just to see if you can get a connection again. SmartRF Studio can be downloaded from here: www.ti.com/.../smartrftm-studio

You could also try to reinstall the drivers manually. The drivers can be found together with SmartRF Studio here: ..\SmartRF Tools\Drivers\xds110. When doing so, make sure you only have one device plugged in at a time

Thanks,

Alexis

0 Davide Giovanelli over 5 years ago in reply to Alexis Crandall20

Expert 1275 points

Thank you Alex,

I tried to manually install the *.inf files, I tried those included in the last version of SmartRF Studio (no luck) and also those included in the old CCS installation where I took the xds firmware that broke the devices (no luck).

I tried to plug the devices into a Linux pc and the dmesg command don't show anything about usb/serial ports/debuggers. On windows I don't know if an equivalent of dmesg exists, however, when I plug a valid USB device with the Device Manager open, I usually see a kind of 'refresh' that update the device tree shown. With these boards I don't see any activity of the Device Manager (obviously if I search for the xds110 there is nothing).

Then I need other suggestions (if there are any...). Maybe, is there an hardware way (such as pulling high/low some pin) to force the DFU mode of the xds110?

0 PM over 5 years ago in reply to Davide Giovanelli

TI__Mastermind 27145 points

Hi Davide,

We are little behind the Schedule. We will look into it . Please bear with us.

Thanks,

0 TER over 5 years ago in reply to PM

TI__Guru**** 317180 points

If the XDS110 does not pop up in SmartRF Studio etc you most likely need to reflash the bootloader code into the TIVA: The hex file for this is could be found under C:\ti\ccs920\ccs\ccs_base\common\uscif\xds110\firmware.bin but that require that you have a functional XDS110 and a debug connector for the TICA. The connector is P8 (on the C1310 LP) up in the right corner if you look at the LP from the underside.

0 Davide Giovanelli over 5 years ago in reply to TER

Expert 1275 points

Thank you, it doesn't look impossible. I have a working XDS110, now I try to find the connector.

Thank you,

Davide.

Sub-1 GHz

Sub-1 GHz forum

LAUNCHXL-CC1350: xds110 bricked?