• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 1782 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2642R: XDS110 Class Data Port and Debug Probe are not installed

Ji-won Lee
Genius 3630 points
Part Number: CC2642R

Hi TI experts,

I am installing all BLE environments to a new laptop under Windows 10 64bit including Intel chipset Core i7 7thGen.

Launchpad is not recognized from TI Smart Programmer 2 and CCS and IAR EW. It returns -260 error.

And I realized that it is detected as XDS110(02.03.00.12) Embed with CMSIS-DAP.. So, I tried to update the related drivers to make it work as "Class Data port and Debug probe" mode.

By the way,  driver updating for XDS110(02.03.00.12) Embed with CMSIS-DAP doesn't work at all.

"Access is denied" happens as below even though I run the related program as an administrator right.

By using DPInst64, I tried to solve this out, but it still has the same issue.

Of course, the boards are recognized well on my old laptop. it works well with respect to DFU, Serial number, and so on. So, firmware.bin also works well.

But, the DFU related commands always show that "0 devices" under the new environment. it doesn't detect the board at all.

.

BR,

Ji-won Lee

  • 0
    Genius 3630 points
    After getting ti_xds110_setup_7.0.100.1_windows installed, and then copy WdfCoInstaller01009.dll and winusbcoinstaller2 in C:\ti\xds110\drivers\xds110_drivers\x64 to C:\Windows\System32. And then reboot my laptop.
    And when updating the XDS110 Embed with CMSIS-DAP on device manager, driver updating works well without the "Access is denied" issue.
    Now, all boards are detectable without issues.
  • 0 in reply to Ji-won Lee
    TI__Guru 73236 points
    Great! I'm glad you were able to resolve your issue, and also thanks for posting the solution in case others may run into the same in the future.

    Regards,
    Katie