LP-EM-CC1354P10: Unable to flash firmware because the firmware upgrade of the debug probe fails

Hi Balaji,

it is correct that if you upgraded to a new Code Composer Studio version also an update of the XDS110 firmware is required. Usually this is executed automatically when you try to flash the board and if not it has to be done manually using the xdsdfu utility.

I can see that you started that process correctly. The reason that the XDS110 gets stuck in bootloader mood is because you didn't add the reset flag '-r' of the flash command. 

Please execute the following set of commands one by one and provide me with the full log so that we can trace down the error.

Kind regards,
Theo

Hi Theo,

Thanks for the response. 

Here are the outputs you have asked for.

PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -e

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

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 3.0.0.22
Manufacturer: Texas Instruments
Serial Num: LS4500IQ
Mode: Runtime
Configuration: Standard

Found 1 device.
PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -m

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

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 3.0.0.22
Manufacturer: Texas Instruments
Serial Num: LS4500IQ
Mode: Runtime
Configuration: Standard

Switching device into DFU mode.
PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -e

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

Scanning USB buses for supported XDS110 devices...

Found 0 devices.
PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -f .\firmware_3.0.0.31.bin -r

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

Scanning USB buses for supported XDS110 devices...

The requested device was not found on the bus.
PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -e

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

Scanning USB buses for supported XDS110 devices...

Found 0 devices.

Hi Balaji,

from the logs I can see that the XDS110 is not successfully switched to DFU mode.
After executing ".\xdsdfu.exe -m" the command ".\xdsdfu.exe -e" should list the XDS110 in DFU mode. Instead, it shows "0 found devices" which explains why the update is not successful.

I see two possibilities:
1. Please verify that you did not interrupt the connection in between.
2. If the error persists the XDS110 is most likely in an error state due to a failed update. The procedure to recover an XDS110 by flashing the bootloader is described here: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/887212/faq-launchxl-cc1352p-debugger-firmware-upgrade-failure/3281522#3281522

Please let me know if you could recover the XDS110 by following it.

Kind regards,
Theo

1. I do not interrupt the connection. The USB cable stays connected all the time and no other usb operation is in progress.

2. I will read up. Thanks. But I wonder how this is happening on new kits that I just unboxed. Anyways, I will try the recovery procedure and let you know. I wont be able to do it if that needs additional hardware.

Hi Balaji,

Please follow then these instructions: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/887212/faq-launchxl-cc1352p-debugger-firmware-upgrade-failure/3281522#3281522

This can happen because the XDS110 firmware flashed on the kit that you bought is not up to date with the XDS110 version required by the latest CCS Studio version due to a gap between it's production and today. When you try to flash it the first time with CCS it tells you that the XDS110 firmware needs to be updated and you need to click on update. If during this update anything goes wrong the XDS110 can end up like that. Since you said that this process failed I think it is what happened.

Kind regards,
Theo

From the linked guide, I understand that another device with a XDS110 debugger is needed for reprogramming the bricked device. But all I have is the two debuggers both having problems with firmware update. The guide also has images and instructions for another kit and I believe those are not relevant to XDS110. 
Is it possible to obtain an older version of code composer studio version that is compatible with the XDS110 firmware?

Hi Balaji,

you would need to follow the green marked answer "Rescuing a XDS110 which does not show up on the Computer" by Vegard H but you need for that a working XDS110.

Using an older CCS version that is compatible to this firmware wont help since it seems like it is in an undefined state.

When you connect it to CCS and try to flash the board can you see the pop up that the XDS110 needs a firmware update?
When you then click on update XDS110 which error message do you get?

Kind regards,
Theo

Hi Balaji, 

could you please also share a picture of your setup with me.
I would like to check that all the jumpers are in place.

Kind regards,
Theo

Theo Lange said:

When you connect it to CCS and try to flash the board can you see the pop up that the XDS110 needs a firmware update?
When you then click on update XDS110 which error message do you get?

Theo Lange said:

When you connect it to CCS and try to flash the board can you see the pop up that the XDS110 needs a firmware update?
When you then click on update XDS110 which error message do you get?

IcePick_C: Warning: A firmware update is required for the XDS110 probe. The current firmware is version 3.0.0.22. The probe must be upgraded to firmware version 3.0.0.31 to be compatible with this software. Click the "Update" button to update the firmware. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 12.8.0.00189)
IcePick_C: Error: (Error -591 @ 0x0) The firmware updater encountered an error and could not finish. The updater failed to connect to the XDS110 in programming mode. Unplug and re-plug the XDS110, and try again. If the problem remains, try updating the firmware using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of the installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 12.8.0.00189)

I have also added a video here showing whats happening.

Theo Lange said:

could you please also share a picture of your setup with me.
I would like to check that all the jumpers are in place.

Here you go.

Hi Balaji,

Thank you for the image and the video. I can see that the board setup is correct and that the error that you see in CCS is the same as when using xdsdfu.

Please try the following:
- Disconnect the board from the XDS110.
- Only connect the XDS110 to the pc.
- Try to update the XDS110 using xdsdfu.exe following the set of commands below:

I get the same output as I did with the board connected. Here it is.

PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -e

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

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 3.0.0.22
Manufacturer: Texas Instruments
Serial Num: LS4101QT
Mode: Runtime
Configuration: Standard

Found 1 device.
PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -m

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

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 3.0.0.22
Manufacturer: Texas Instruments
Serial Num: LS4101QT
Mode: Runtime
Configuration: Standard

Switching device into DFU mode.
PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -e

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

Scanning USB buses for supported XDS110 devices...

Found 0 devices.
PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -f .\firmware_3.0.0.31.bin -r

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

Scanning USB buses for supported XDS110 devices...

The requested device was not found on the bus.
PS C:\ti\ccs1280\ccs\ccs_base\common\uscif\xds110> .\xdsdfu.exe -e

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

Scanning USB buses for supported XDS110 devices...

Found 0 devices.

I see a JTAG connecter on the CC1354P10-1 board. Is it possible to use Jlink to program the chip? 

Hi Balaji,

thank you for continuing testing, that's great.

Can you now also upgrade it to the latest XDS firmware?

Kind regards,
Theo

Yes. It works now with Code Composer Studio 12.8 as well. It upgraded the firmware from v3.0.0.28 to 3.0.0.31 and everything now works well!