CCS/MSP-EXP432E401Y: CS_DAP_0: Error initializing emulator

Philip Baltz1

Part Number: MSP-EXP432E401Y
Other Parts Discussed in Thread: MSP432E401Y

Tool/software: Code Composer Studio

I've been using two MSP432E401Y LaunchPads with built in XDS110 emulators for several weeks with no issues connecting to CCS, but today CCS is unable to initialize the emulator on either LaunchPad. An attempt to connect to the LaunchPads from CCS reutrns an error: CS_DAP_0: Error initializing emulator: (Error -260 @ 0x0).

The XDS110 is present in Windows 10 Device Manager, both the UART ports and the Debug Probe:

However running the Target Configuration Debug Probe Test Connection reports the following:

[Start: Texas Instruments XDS110 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\pbaltz\AppData\Local\Texas Instruments\
    CCS\ccs1000\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Feb 13 2020'.
The library build time was '18:30:11'.
The library package version is '9.1.0.00001'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-260' (0xfffffefc).
The title is 'SC_ERR_XDS110_OPEN'.

The explanation is:
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.

[End: Texas Instruments XDS110 USB Debug Probe]

And attempting to connect to the XDS110 via xdsdfu.exe reports the following:

Although Windows 10 appears to recognize that the XDS110 is present, CCS does not. Additionally the COM ports are functioning as I can connect to COM4 from the LaunchPad and perform Display Print functions to a terminal on that port. What do I need to do to get the debug probe working with CCS? I've already tried uninstalling both the device and driver in Windows and reconnecting, but the problem still occurs.

-phil

over 5 years ago

0 Dennis Lehman over 5 years ago

TI__Guru 71216 points

Hello Philip,

I have reached out to our tools team for help with this.

0 Philip Baltz1 over 5 years ago in reply to Dennis Lehman

Intellectual 820 points

Dennis,

Thank you. I've tried everything I can think of to solve this:

- uninstalled XDS110 and drivers via Windows 10 Device Manager

- manually reinstalled XDS110 EMUPack

- uninstalled and reinstalled CCS 10

None of those worked. I still get the same error. I hope the tools team can help with this problem.

-phil

0 Edward Fewell over 5 years ago in reply to Philip Baltz1

TI__Intellectual 2515 points

Whatever is going on, it's definitely not the device driver. If Device Manager displays the device correctly with no yellow triangle warning, then the device driver is working. Note that the binaries used by the driver are built into Windows; the driver .inf file just points to those files.

You haven't mentioned rebooting the PC? It is possible a process crashed and is holding a handle to the device. Also be sure no other applications that may use the device are running.

If that's not it, then can you check another thing out? Go into Device Manager, right click on any of the XDS110 entries, choose Properties, select the Details tab, scroll down and tell us what the value for Parent is.

0 Philip Baltz1 over 5 years ago in reply to Edward Fewell

Intellectual 820 points

Edward,

I've rebooted a couple of times (including after reinstalling CCS). Here's the Parent value: USB\VID_0451&PID_BEF3\ME401023

Here's some more information form the Device Manager -> Events:

The Information for each of the last four events:

Device USB\VID_0451&PID_BEF3&MI_02\f&feb977d&0&0002 requires further installation.

Device USB\VID_0451&PID_BEF3&MI_02\f&feb977d&0&0002 was configured.

Driver Name: oem679.inf
Class Guid: {8e84f6ae-7786-4c95-a48a-14cf3b92c002}
Driver Date: 02/10/2020
Driver Version: 2.0.0.2
Driver Provider: Texas Instruments Incorporated
Driver Section: USB_Install
Driver Rank: 0xFF0001
Matching Device Id: USB\VID_0451&PID_BEF3&MI_02
Outranked Drivers:
Device Updated: false
Parent Device: USB\VID_0451&PID_BEF3\ME401023

Device USB\VID_0451&PID_BEF3&MI_02\f&feb977d&0&0002 was started.

Driver Name: oem679.inf
Class Guid: {8e84f6ae-7786-4c95-a48a-14cf3b92c002}
Service: WinUSB
Lower Filters:
Upper Filters:

Driver Management concluded the process to install driver xds110_debug.inf_amd64_c3db6584de66afb3 for Device Instance ID USB\VID_0451&PID_BEF3&MI_02\F&FEB977D&0&0002 with the following status: 0x0.

0 Philip Baltz1 over 5 years ago in reply to Philip Baltz1

Intellectual 820 points

After learning how to use the search function on e2e correctly :D, I found another post with the same error which led me to this page:

https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

Based upon that I used a different USB port, one directly on my PC and now I can successfully connect the LaunchPad. For some reason if the LaunchPad is connected to a USB hub in my monitor (this had previously worked) or my laptop's docking station then CCS won't recognize it but will find it when directly connected.

Any idea why that could be? I am thinking about removing all of the USB\VID_0451&PID_BEF3 entries from the registry and starting fresh.

0 Edward Fewell over 5 years ago in reply to Philip Baltz1

TI__Intellectual 2515 points

No, I don't have any idea, especially given that it was working and then stopped. We've heard from time to time about hubs not working well. And some early USB 3.0 port hardware is problematic.But these cases are usually hard failures where it never worked.

Clearing the registry shouldn't hurt anything, but I doubt it will help.

0 Philip Baltz1 over 5 years ago in reply to Edward Fewell

Intellectual 820 points

Thanks. I'll report back.

0 Philip Baltz1 over 5 years ago in reply to Philip Baltz1

Intellectual 820 points

Edward,

I guess we'll have to chalk this up to a finicky USB 3.0 hub. When I use the docking station (with integrated USB 3.0 hub) CCS can't find the emulator. Connecting the Launchpad directly to the PC, or through a USB 2.0 hub, and CCS finds the LaunchPad every time.

I cleaned out as many of the registry VID_0451 entries as I could but that didn't help, like you expected.

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

CCS/MSP-EXP432E401Y: CS_DAP_0: Error initializing emulator