Quantcast
Channel: Microcontrollers
Viewing all articles
Browse latest Browse all 232517

Forum Post: LAUNCHXL-F2800157: Error -260 with XDS110 Debugger on LAUNCHXL-F2800157 After Disconnecting During Debug Session

$
0
0
Part Number: LAUNCHXL-F2800157 Tool/software: Hello We are experiencing a connection issue with our LAUNCHXL-F2800157 LaunchPad. During an active debug session, We inadvertently disconnected the board. Since then, attempts to reconnect the debugger result in the following error: ​ IcePick_C_0: Error initializing emulator: ( Error - 260 @ 0 x0) An attempt to connect to the XDS110 failed. The cause may be one or more of : no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 20.0 . 0.3344 ) Steps We have Taken to Resolve the Issue : Checked Physical Connections : Verified that the USB cable is securely connected and functional by testing with another device. ​ Tried different USB ports on the computer Attempted Firmware Recovery : Navigated to the ccs_base/common/uscif/xds110 directory in our Code Composer Studio (CCS) installation. ​ Ran the command xdsdfu -e to list connected devices, but received a message stating no devices were found. ​ Attempted to put the XDS110 into maintenance mode using xdsdfu -m , but encountered the same issue of no devices being detected. Inspected Device Manager : Observed that the XDS110 does not appear. ​ Previous Functionality : The LaunchPad was functioning correctly before the disconnection incident. ​ Request for Assistance : We would appreciate any guidance on the following: Are there additional steps we can take to recover or reflash the XDS110 firmware, considering it's not being recognized by the system? ​ Is there a method to manually reset the XDS110 debugger hardware on the LaunchPad? ​ Could the disconnection have caused hardware damage to the debugger, and how might we diagnose this? ​ Thank you for your assistance.

Viewing all articles
Browse latest Browse all 232517

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>