TMS320F28388D: XDS560V2 not recognized in Device Manager (Code 39)

Hello Sang-il,

Are they using the Blackhawk XDS560v2?

https://www.ti.com/tool/TMDSEMU560V2STM-U

If so, what is the status of the LEDs as documented in section 2.21 of the attached document?

USB560v2-IG-01.pdf

Thanks

ki

Hello Ki,

We are using the XDS560V2 STM USB Emulator from Spectrum Digital, although the company is now out of business. (I assume it is identical to Blackhawk's XDS560V2 product, as they were likely built on the same reference design.)

Given your suggestion to check the LED status as outlined in the provided document, it seems you are asking whether the device has entered safeMode. Using the Sd560v2Config tool that installs alongside Code Composer Studio, I verified that the device is in a normal operating state with safeMode=false.

Just to be thorough, I ran a test on my own PC (where the emulator works normally) instead of my colleague's PC (where the issue is occurring). I deliberately forced the XDS560V2 into safeMode=true to see if it would trigger any USB recognition issues on the PC, but I did not observe any anomalies.

For reference, here are the main specifications of my PC:
- Code Composer Studio: v12.8.1.00005 & v20.5.1.00012
- OS Edition: Microsoft Windows 11 Pro
- OS Version: 25H2
- OS Build: 26200.8655
- OS Memory Integrity: ON (Enabled)

I am wondering if this is an isolated issue specific to the USB controller or OS on my colleague's PC, or if there have been similar cases reported that have a known solution.

Best regards,
Sang-il

Hello Ki,

A1). The device's boot process proceeds normally, and the blinking sequence of the status LED matches the exact pattern observed during a regular boot sequence.

A2). I am currently unable to verify this part. Due to internal circumstances, the PC where the issue occurred is located remotely, making an immediate check impossible. On my own PC—where the device operates perfectly without any issues—all the latest MS Windows updates are fully applied, and the Memory Integrity option is turned on, yet no abnormal behavior has been observed.

Follow-up Question:
If testing the device after disabling the Memory Integrity option on the problematic PC results in successful recognition and normal operation, I would like to know if there are any follow-up solutions or countermeasures available. (I am asking this because leaving Memory Integrity disabled poses a security risk for PC usage.)

Closing Statement / Next Steps:
Aside from the answers and the additional question above, I cannot immediately perform the requested tests on the problematic PC at this moment. Furthermore, since this might be an isolated issue specific to that PC—such as a USB controller error or unique security configuration—I intend to conduct some further internal testing first. If the same issue is confirmed later and I am in an environment where direct troubleshooting is possible, I will post a new thread to the community with the same inquiry.

Best regards,
Sang-il

Sang-il Nam said:

Follow-up Question:
If testing the device after disabling the Memory Integrity option on the problematic PC results in successful recognition and normal operation, I would like to know if there are any follow-up solutions or countermeasures available. (I am asking this because leaving Memory Integrity disabled poses a security risk for PC usage.)

The memory integrity suggestion was a bit of a "reach". This is typically not an issue (it is on for me too and I do not have an issues with XDS560v2). However I don't have much insight on best practices if the memory integrity option is the culprit. 

This question really is best addressed by the vendor of the debug probe since the issue is an low level issue with the probe and not anything to do with CCS (My expertise is CCS). Unfortunately the vendor is no longer in business.

I think the issue may be security related (antivirus, etc). However you mentioned this is a colleague and that it is working for you so it must be something specific to you colleague's machine.

Yes, I completely understand what you mean. Thank you for providing such a detailed answer, even though it was outside your area of expertise.