This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I was working with the MSP432 LaunchPad without any issues, I then noticed a number of recommended updates (sorry, cannot remember them all). I then followed the suggested updates, but now receive the following error when trying to program the MSP432 LaunchPad.
Connection is: Texas Instruments XDS110 USB Debug Probe [Default]
I am using CCS Version: 6.1.0.00104
Compiler: TI v5.2.3 (Which was one of the updates) - Tried earlier versions.
Error connecting to the target:(Error -1063 @ 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 5.1.641.0)
Code Examples, Libraries and Solutions for IoT Projects
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to desouza:
In reply to Glenn Vassallo:
Thanks for reporting back your findings. I would also double check the firmware revision of your XDS110 (perhaps the board you have has an older firmware, I don't know).
To do this:
- open a command prompt and go to the directory that hosts the xdsdfu utility:
- run xdsdfu -e to enumerate the attached devices. The output of my working Launchpad is shown below:
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: 0x0451 PID: 0xbef3 Device Name: XDS110 with CMSIS-DAP Version: 220.127.116.11 Manufacturer: Texas Instruments Serial Num: RAFAEL Mode: Runtime
Found 1 device.
- If you need to update, check the file Readme.txt in the directory above.
Hope this helps,
In reply to Gregory Whitmore:
I'm getting this error anytime I load the examples from MSPWare (like the OutOfBox or the BlinkLED projects) onto my LaunchPad. I have to do this factory reset of the MSP432 to get the connection back. Gregory do your example projects work now? I never changed any of the code like the OP did, and I suspect you never did either. When I begin a debug session, the code loads, and then the debugger starts flashing quickly between executing - resetting. The debugger never settles at the beginning of main() ready to debug, and never enables the "pause" button (only the "stop" button). Then I have to stop that session (or it eventually has a connection failure), and all future sessions give the error described by the OP (until I do the factory reset of the MSP432). Any help? I'd love to get some example code up and running. It always accelerates the learning process for me. Thanks, Jeff
In reply to Jeff Tenney:
Jeff TenneyI'm getting this error anytime I load the examples from MSPWare (like the OutOfBox or the BlinkLED projects) onto my LaunchPad. I have to do this factory reset of the MSP432 to get the connection back.
This is a known issue, please see this related thread for root cause and workaround details.https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/460430/1663082#1663082
Please click This Resolved My Issue if the reply answers your question.
Search the wikis for common questions: Compiler, CCSv6, CCSv7Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box
In reply to AartiG:
Thank you AartiG, I should have searched the forum more carefully.
I can confirm that fix works for me.
Glenn VassalloThanks Rafael, 8. Connect only to the Non-Debuggable Devices > DAP. 9. Go to Script > Factory Reset. 10. Power cycle and try to restart debug.
I'm running into some trouble here. I'm not sure what the "> DAP" part means, when I chose show hidden the XDS110 debug probe became a child of "Non-Debuggable Devices". Is DAP an option that I'm supposed to choose or is it what the name of the target is supposed to be? After connecting to the non debuggable devices there are no options in the script menu with non-debuggable devices highlighted. With the XDS110 probe highlighted there a bunch of options under MSP432 Debug Clock Control, but I get an error saying target is not connected if I try to run them.
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.