Making use of the CCS cloud on mac osx and on linux, the msp432 xds110 firmware was upgraded to the 126.96.36.199 version. Afterwards, I have tried to use it with CCS, and it was imposible to connect with the debugger. I tried to downgrade it to 188.8.131.52 using the firmware.bin available in the CCS, but it stills stays in 184.108.40.206.
Is there a solution to downgrade the firmware, or upgrade the CCS driver?
Thanks in advance,
If my reply answers your question please click the "This resolved my issue" button
In reply to JohnS:
I am able to downgrade to 220.127.116.11 on MacOS as well.
Attached is the firmware file I am using. I have run ./xdsdfu -e afterwards to make sure the firmware was programmed.
What error message do you get in CCS?
The error that I get is that I have to upgrade manually the using the xdsdfu tool.
When I program with the tool using the firmware available in the CCS 6.1.1 and check it with the xdsdfu -e, I always get the version 18.104.22.168. I will try with this new firmware.bin to see if the situation changes.
Thanks for your help,
In reply to jmgc:
It seems that it is necessary to downgrade the firmware to the version 22.214.171.124:
Answer on Linux CCS v 6.1.1.
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, invalidXDS110 serial number, or faulty USB connection. The firmware andserial number may be updated using the xdsdfu utility found inthe .../ccs_base/common/uscif/xds110 directory of yourinstallation. View the ReadMe.txt file there for instructions.(Emulation package 126.96.36.199)
The console shows that there is one device with version 188.8.131.52:
[xds110]$ ./xdsdfu -e
USB Device Firmware Upgrade UtilityCopyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.
Scanning USB buses for supported XDS110 devices...
<<<< Device 0 >>>>
VID: 0x0451 PID: 0xbef3Device Name: XDS110 with CMSIS-DAPVersion: 184.108.40.206Manufacturer: Texas InstrumentsSerial Num: 00000000Mode: Runtime
Found 1 device.
Following the instructions with the firmware available in CCSv6.1.1
[xds110]$ ./xdsdfu -m
Switching device into DFU mode.[xds110]$ ./xdsdfu -e
VID: 0x1cbe PID: 0x00ffDevice Name: Tiva Device Firmware UpdateManufacturer: Texas Instruments IncorporatedSerial Num: 00000000Mode: DFU
Found 1 device.[xds110]$ ./xdsdfu -f firmware.bin -r
Downloading firmware.bin to device...[xds110]$ ./xdsdfu -e
VID: 0x0451 PID: 0xbef3Device Name: XDS110 with CMSIS-DAPVersion: 220.127.116.11Manufacturer: Texas InstrumentsSerial Num: 00000000Mode: Runtime
I don't think downgrading the firmware manually to 18.104.22.168 is going to work. CCS is just going to force you to update it to 22.214.171.124 when you launch the debugger.
I get that exact same error message you are seeing when my XDS110 is in DFU mode instead of runtime mode.
If I have it in runtime mode then CCS launches fine (Win/Lin/Mac).
The VID and PID of yours are the same as mine.
USB Device Firmware Upgrade Utility
Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.
VID: 0x0451 PID: 0xbef3
Device Name: XDS110 with CMSIS-DAP
Manufacturer: Texas Instruments
Serial Num: 00000000
Maybe your 2242 firmware files is corrupted. Here is a copy of mine. Try updating with this one. Then run the utility with -e to make sure it is in runtime mode and then try connecting with CCS. If that doesn't work I am going to need to pull in someone else to try to get to the bottom of what is going on.
The debug software will not allow connection to a different version of the firmware than was packaged with it. If you downgrade the firmware, then the auto-update feature will attempt to update to the correct version. This would be why you see that the XDS110 reverts to version 126.96.36.199 of the firmware each time.
At the moment, I'm not exactly sure what might be wrong. The XDS110 is able to communicate over the USB connection, otherwise the update and the xdsdfu utlity would not be able to work. The -m switch is executed by sending a message over the debug endpoint, so that endpoint is functional, or at least is receiving commands. So many of the common problems with OS drivers, permissions, or the like aren't the problem here.
Can you supply some more information? Please upload the .ccxml file you are using. And trying using the Test Connection button from CCS and post the results. I don't expect it to work, but it will include more info that might give a hint as to what is happening.
In reply to Edward Fewell:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.