• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 30 subscribers
  • Views 422 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.

Original question:

XDS100v1 and XDS100v2 Driver Problem

LAUNCHXL2-570LC43: Windows 11 does not recognize integrated XDS110 probe, Linux does

Durga Choudhury
Intellectual 380 points
Part Number: LAUNCHXL2-570LC43
Other Parts Discussed in Thread: HALCOGEN,

I am working with a LAUNCHXL2-570LC43 launchpad. I am a Linux user and in Ubuntu 2022.04 this device works like a charm. However, many of the software, for example Halcogen, are supplied as a Windows only distribution (significantly degrading developer productivity and software quality). Thus I was forced to switch to Windows for at least part of the project. In Windows 11, the probe is not recognized (I have tried all the obvious things like upgrading the driver: Windows reports nothing is found). A screen shot is attached.

Another behavior I noticed is that I cannot put the device to DFU mode. Here are the relevant outputs:

C:\ti\ccs1110\ccs\ccs_base\common\uscif\xds110>xdsdfu  -m

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x0451    PID: 0xbef3
Device Name:   <<Unknown>>
Manufacturer:  <<Unknown>>
Serial Num:    <<Unknown>>
Mode:          Runtime
Configuration: Standard

Switching device into DFU mode.

C:\ti\ccs1110\ccs\ccs_base\common\uscif\xds110>xdsdfu  -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.

Scanning USB buses for supported XDS110 devices...


<<<< Device 0 >>>>

VID: 0x0451    PID: 0xbef3
Device Name:   <<Unknown>>
Manufacturer:  <<Unknown>>
Serial Num:    <<Unknown>>
Mode:          Runtime
Configuration: Standard

Found 1 device.

Notice that the device did NOT switch to DFU mode.

This must be a Windows software issue because in Linux this works fine (as with most other software)

Please help.

Regards

Durga

  • 0
    TI__Guru**** 463781 points

    Hello Durga,

    I assume it is the SAME XDS110 probe that works fine on Linux but not Windows. Can you provide the xdsdfu -e output you see for that probe on Linux?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 380 points

    Hello Ki

    Yes, it is the same exact probe. In fact, it is a LAUNCHXL2-570LC43 launchpad with a built-in XDS-110 probe. The output from Linux (Ubuntu 22.04, CCS 11.1.0.00011 is as follows:

    /opt/ti/ccs1110/ccs/ccs_base/common/uscif/xds110$ ./xdsdfu -e

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2019 Texas Instruments Incorporated.  All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x0451    PID: 0xbef3
    Device Name:   XDS110 Embed with CMSIS-DAP
    Version:       3.0.0.20
    Manufacturer:  Texas Instruments
    Serial Num:    00000000
    Mode:          Runtime
    Configuration: Standard

    Found 1 device.

  • 0 in reply to Durga Choudhury
    TI__Guru**** 463781 points

    There must be some issue with your Windows 11 enviroment. I am able to get the XDS110 on my Hercules LaunchPad detected successfully on my Windows 11 PC. It looks like an issue with the WIndows drivers or the probe was not proeprly enumerated. You mentioned you tried reinstalling the Windows drivers without success. Perhaps it is an enumeration issue. Is the XDS110 connected directly to the PC or is it via some USB hub? If it is the latter, can your try the former? Also, have you tried connecting the launchpad to a different windows PC? 

  • 0 in reply to Ki
    Intellectual 380 points

    Well, may be so, but that does not provide me a solution. I'd not even think about booting to Windows if it were not that many of your tools are Windows only, such as Halcogen, and there is really no need for that because all they do are simple file unzip and code generation, that has no OS dependency inherently.

    I am connected via a USB hub, but I am also connected the same way for Linux. The setup is identical except for the host operating system. I will try connecting directly to the PC, but even if that works (I am skeptical why it would), it won't solve my issue because I need a high-current USB hub to act as a power supply for the Launchpad and I don't think the laptop's UBS port can source that much current.

    Have you taken a look at the version number of the probe: Version:       3.0.0.20

    This was *not* the version it came with; I had to upgrade it using the Linux DFU firmware (CCS prompted me to do it; I don't remember the sequence of events that lead to the prompting). After upgrading the CCS running in Linux was happy, but Windows does not even recognize it. I don't think I ever tried it in Windows with the older firmware so I won't know if that upgrade created Windows incompatibility.

    Please verify that your firmware version is the same as mine; if that is the case and it works in Windows 11 for you, I will be puzzled.

  • 0 in reply to Durga Choudhury
    TI__Guru**** 463781 points
    Durga Choudhury said:
    Have you taken a look at the version number of the probe: Version:       3.0.0.20

    CCS 11.1  debugger requires at least this version of the XDS110 firmware. If the debugger detects a version below this number, it will automatically try to update it. The same happened when I tried connecting to my Hercules LaunchPad with CCS 11.2.0. It detected an older XDS110 firmware and auto updated it to 3.0.0.20 before successfully connecting to the target