• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 699 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/CC2640R2F: UART of XDS110 cannot communicate

Ewan
Prodigy 100 points
Part Number: CC2640R2F

Tool/software: Code Composer Studio

UART of 2640R2F LAUNCHPAD cannot communicate with my computer (Windows 7 Ultimate) . 

I can download and debug program with this board, but the UART cannot work. 

I don't think what is running on the board matters.

And it works well in my laptop(Windows 10) which use the same CCS installer. 

I tried to close the signature verification on my WIN7 PC, but nothing works. 

  • 0
    TI__Guru**** 171044 points

    Hi, 

    I haven't seen this issue before; however, since the XDS110 uses the OS drivers for the two UART ports, the behaviour is consistent with the failure. 

    One aspect of these two ports is that they use the same drivers as the OS - in other words we (TI) only provide the .inf file but not the .sys files. 

    I would definitely try to inspect if any specific permissions or group policies are somehow blocking the installation of these .inf files.

    You can try to reinstall the drivers by following the procedure at the Troubleshooting section of the XDS110 page at: 

    http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html 

    I will try to find additional reports of developers with similar scenarios and report back to this thread. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 100 points

    Thanks for your reply. I have reinstalled many times, and tried 3 different versions. But it does not seem to work.

    Looking forward to your more information.

  • 0 in reply to Ewan
    TI__Guru**** 171044 points

    Hi,

    I asked around with other developers and unfortunately nobody has seen this issue. 

    The mostly likely culprit is that <usbser.sys> is missing or corrupt. Is it possible that something was installed on the host that replaced this driver with its own copy of usbser.sys and/or removed the Microsoft one? Or perhaps a recent Windows Update that was performed on the offending host? 

    I have tested here in my Windows 7 Pro which also features the same three versions of the XDS110 Class Data Port .inf files and all of them work. 

    Without having a way to reproduce this, unfortunately my actions on this case are quite limited, but I will be on the lookout for other reports or keep trying to "break" my system here. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Prodigy 100 points

    Really appreciate your help.

    It works that I replace the <usbser.sys> in /system32 with in /DriverStore.

    Many thanks!