• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 542 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: Comm ports will not install

Jeff Thon91
Prodigy 60 points
Other Parts Discussed in Thread: CC1350, CC1310

Tool/software: Code Composer Studio

XDS110 is not a recognized part number.

Windows 10 Home

ASUS Laptop with AMD A9 processor.

CCS Version: 8.2.0.00007 

ti_emupack_setup_8.0.903.4_win_32

The comport drivers will not install as ports.

I am developing my RF application on CC1310 Launchpad Rev 1.4 and CC1350 LaunchPad Rev 1.3.

I have no problems compiling, downloading and running the examples with the exception of examples outputing "printf" statements to stdout. I can't use any terminal program.

I have searched e2e and google for xds110 and any keyword(s) I felt relevant. I tried suggestions which I thought may resolve the problem.

I have installed and uninstalled CCS and TI emupack several times. I have even scrubbed the registry of all related entries and renamed remnant directories.

As you can see from the graphic there are devices classified as unknown with ? 's in the icon.

What is shown is for two launchpads connected.

When I select a port in any of the unknown devices, the Device Manager will immediately terminate. 

When investigating the driver details they are as follows::

Driver Date: 10/8/2018

Driver Version: 1.9.0.0

Has Problem: <false>

I usually can resolve my problems myself, but this one has me frustrated.

If anybody can help, it would be greatly appreciated

Thank you in advance

Jeff Thon

  • 0
    TI__Guru**** 171309 points
    Jeff,

    I suspect the invalid/strange entries are leftovers from previous device driver installs.

    Perhaps this may be fixed by reinstalling the Windows drivers. If you want to try this, please check the section Troubleshooting of the XDS110 page below.

    dev.ti.com/.../

    I will check if there were recent changes to the device names in the Device Manager.

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    TI__Intellectual 2515 points

    I have not seen anything like this particular issue.

    The Debug Probe and Data Port entries are installed from a separate .inf file than the COM Port entries.

    That you see the names such as "XDS110 Class Application/User UART" indicates the driver was at least partially installed.

    The category name is selected by the Class GUID entry in the driver.  For Texas Intruments Debug Probes category, the GUID was generated here and the name is included in the driver .inf install.  However, for the COM Ports, the GUID is the standard COM Port GUID supplied by Microsoft.  So that it shows "Unknown" means that somehow that info is corrupted, either the driver's GUID entry is corrupt or there's actually some issue in the Windows installed on that PC.

    I would try uninstalling all copies of the driver to attempt a new, clean installation. Right-click on the entry in the Device Manager and choose "Uninstall".  Click the box that says to delete the files in the pop-up dialog.  Then unplug and re-plug the probe, let Windows finish enumerating and re-installing the next older driver.  And repeat the uninstall, unplug, etc. until it no longer installs a driver for the probe.  Then attempt to re-install the driver.  If there are errors during that installation, they may point to the root problem.

  • 0 in reply to desouza
    Prodigy 60 points

    Rafael,

    Thanks for the suggestion. I tried this before I posted my original question.

    After two uninstalls it looked like this:

    It goes back to the original devices when I install the latest emupack.

    I am still researching.

    Thanks again,

    Jeff Thon

  • 0 in reply to Edward Fewell
    Prodigy 60 points
    If you could point me to the .inf files in question, that may give me further clues.

    Thanks
    Jeff
  • 0 in reply to Jeff Thon91
    TI__Guru**** 171309 points
    Jeff,

    Were you able to follow the uninstall procedure highlighted by Edward above? More precisely:
    "I would try uninstalling all copies of the driver to attempt a new, clean installation. Right-click on the entry in the Device Manager and choose "Uninstall". Click the box that says to delete the files in the pop-up dialog. Then unplug and re-plug the probe, let Windows finish enumerating and re-installing the next older driver. And repeat the uninstall, unplug, etc. until it no longer installs a driver for the probe. Then attempt to re-install the driver. If there are errors during that installation, they may point to the root problem."

    Regards,
    Rafael
  • 0 in reply to desouza
    Prodigy 60 points
    Yes.
    I went more extreme re-installing windows 10.
    Thanks all for your assistance.
  • 0 in reply to Jeff Thon91
    TI__Guru**** 171309 points
    Jeff,

    Wow, that was extreme, but certainly effective.

    Thank you for sharing the solution with us.

    Regards,
    Rafael