MSPM0G3507: debugger communication

Kent Lennartsson

Prodigy 10 points

Part Number: MSPM0G3507

Tool/software:

Try to update the firmware. It is possible to switch to DFU mode but the kit get lost, see screen shoot.

C:\Users\kent\AppData\Local\Texas Instruments\TICloudAgent\loaders\ccs_base\common\uscif\xds110>xdsdfu -m

USB Device Firmware Upgrade Utility

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3

Device Name: XDS110 Embed with CMSIS-DAP

Version: 3.0.0.25

Manufacturer: Texas Instruments

Serial Num: MG350001

Mode: Runtime

Configuration: Standard

Switching device into DFU mode.

C:\Users\kent\AppData\Local\Texas Instruments\TICloudAgent\loaders\ccs_base\common\uscif\xds110>xdsdfu -f firmware_3.0.0.31.bin -r

USB Device Firmware Upgrade Utility

Scanning USB buses for supported XDS110 devices...

The requested device was not found on the bus.

C:\Users\kent\AppData\Local\Texas Instruments\TICloudAgent\loaders\ccs_base\common\uscif\xds110>

9 months ago

0 Cash Hao11 9 months ago

TI__Mastermind 45685 points

Hi,

Are you trying to update the firmware for XDS-110?

If so, usually we you use CCS to debug a project. The CCS will pop up a notice and let you update the firmware of XDS110.

Best regards,

Cash Hao

0 Kent Lennartsson 9 months ago in reply to Cash Hao11

Prodigy 10 points

Yes that is how it should work. When this fails the suggestion is to use the XDSFDU in the command window.

As you can see from the snap shot from command window also this fails.

I can switch the XDS-110 in FDU mode, but the programming after fail.

It could be my computer?

It could be some safety function in Win11.

The firmware 3.0.0.25 may be to old for the XDSFDU software I am using (3.0.0.31?)?

I will try a second computer..

regards Kent

0 Cash Hao11 9 months ago in reply to Kent Lennartsson

TI__Mastermind 45685 points

Hi,

It may not need to run in FDU mode. You can add MSPM0_BSL_GUI.exe in SDK installation folder\tools\bsl\BSL_GUI_EXE. Modify the attach file name from .txt to .exe

MSPM0_BSL_GUI.txt

Then run the .exe file. In MoreOption->Update XDS110 firmware.

Best regards,

Cash Hao

0 Kent Lennartsson 9 months ago in reply to Cash Hao11

Prodigy 10 points

this application did have version 3.0.0.28 it return with "XDS110 firmware update finished" and you can here from windows that something is happening on the USB connection, but the firmware version is still 3.0.0.25.

best regards Kent

0 Cash Hao11 9 months ago in reply to Kent Lennartsson

TI__Mastermind 45685 points

Hi,

So, the issue now is not the XDS110 can not be updated. It is the version you updated does not match what you read back after a successful update, is it right?

Best regards,

Cash Hao

0 Kent Lennartsson 9 months ago in reply to Cash Hao11

Prodigy 10 points

Sorry for my unclear description.

It is not possible to update the firmware (the GUI claim success but the XDS is not updated) the GUI software fails and lie because the XDS firmware version is still the same version as before the GUI tried to do an update XDS.

regards Kent

0 Cash Hao11 9 months ago in reply to Kent Lennartsson

TI__Mastermind 45685 points

Okay, get it. I found in another post shows how to update the XDS110 firmware. You may want to check that. 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

Best regards,

Cash Hao

0 Kent Lennartsson 9 months ago in reply to Cash Hao11

Prodigy 10 points

I found some USB-drivers installed a year ago used for some other kit. Removed them from Windows and after that it was possible to use XDSDFU correctly.

regards Kent

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0G3507: debugger communication