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.
Tool/software: Code Composer Studio
Picking on CCS 'cause there isn't a forum for the debug probes. After seeing the error of my ways by parsing the XDS110 instructions to imply no *embedded* blanks are allowed in the eight character string passed with -s, I'm trying to change "X-NE" to "X-NE____" to conform to the spec and stop corrupting my .ccxml file in CCS-land. But here's what I'm seeing. A workaround would be much appreciated.
~/rt1/ti/ccsv8/ccs_base/common/uscif/xds110$ xdsdfu -m USB Device Firmware Upgrade Utility Copyright (c) 2008-2018 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... <<<< Device 0 >>>> VID: 0x0451 PID: 0xbef3 Device Name: XDS110 Probe with CMSIS-DAP Version: 2.3.0.17 Manufacturer: Texas Instruments Serial Num: X-NE Mode: Runtime Configuration: Standard Switching device into DFU mode. ~/rt1/ti/ccsv8/ccs_base/common/uscif/xds110$ xdsdfu -s X-NE____ USB Device Firmware Upgrade Utility Copyright (c) 2008-2018 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... Device is in runtime mode. Switch to DFU mode using '-m' before attempting any other operation
~/rt1/ti/ccsv8/ccs_base/common/uscif/xds110$ xdsdfu -e USB Device Firmware Upgrade Utility Copyright (c) 2008-2018 Texas Instruments Incorporated. All rights reserved. Scanning USB buses for supported XDS110 devices... <<<< Device 0 >>>> VID: 0x1cbe PID: 0x00ff Device Name: Device Firmware Update Manufacturer: Texas Instruments Incorporated Serial Num: 1.0.0.1 Mode: DFU Found 1 device.
Yes, the old unplug/replug trick fixed this too.