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.

TMS320F28069M: C2000 LaunchPadXL Serial Port Connection in Windows 10

Part Number: TMS320F28069M

Following the Launch PadXL  TMS320F28069M Development Kit Users Guide Section 4.2

The Launchpad does not have a serial port assigned (COMX) in Windows 10

I loaded ccsv6.2 and the XDS100 drivers my device manager looks as follows:

Are the drivers installed properly?

The Texas Instruments XDS100 shows under debug probes but not under USB devices.

Also there is not way to find the drivers themselves they are not at "ti.com/xds100drivers" as stated in the Quick Start Guide.

How do I get the Windows 10 to recognize the device and assign it a serial COM port?

  • Hi John,

    John Tsinetakes said:
    How do I get the Windows 10 to recognize the device and assign it a serial COM port?

    Did you have a look this post:

    Regards,

    Gautam

  • Yes, I looked at the post mentioned below.

    The part in the video where you need to select the check box next to VCP can only occur if the drives show up as a USB device..

    Windows 10 is blocking the installation of the drivers so I had no

    "TIXDS100ChannelA
    TIXDS100Channel B

    showing up under Universal Serial Bus Controllers.

    I had to do a search and found out that if the Texas Instruments XDS100 drivers are not digitally signed then Windows 10 will block them.

    After I disabled the Windows 10 protection to stop installation of unsigned drivers.

    However,  I still could not find the drivers to reload them per the Quick Start Guide. There are no driver at the location   ti.com/xds100drivers.

    I instead completely uninstalled CCSv6 and control suite completely and the drivers got reinstalled while reinstalling the whole CCS and control suite again.

    A time consuming operation to just install the XDS100 drivers.


     
    I have a new problem now since Power Suite no longer works.