• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1356 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/LAUNCHXL-CC1352P: Cannot get device recognized by Windows 10 machine.

Ray233
Prodigy 30 points
Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: UNIFLASH, SEGGER

Tool/software: Code Composer Studio

Hi,

I'm trying to connect the LAUNCHXL-CC1352P to my standalone Windows 10 64-bit computer.  I do not have admin rights on the box.

I have installed the following:

CCS 9.2 

SimpleLink SDK cc13x2_26x2_3_30_00_03

Uniflash 5.1

I updated the emulator drivers from ti_emupack 8.3 win 64 which gave me the xdc_tools_3_60_01_27 core

My file structure is C:/ti/ 

with the following located there: ccs, simplelink_cc.., uniflash, xdc_tools3_60_00_24_core, xdc_tools3_60_00_27_core.

When I plug in my Launchpad, I get the Windows message of "The USB device you connected malfunctions and Windows does not recognize it." In the Device Manager, it shows up under USB controllers as Unknown USB Device (Device Descriptor Request Failed).

I went to the ti/ccs/ccs_base/common/uscif/xds110 and ran the xdsdfu -e command from the command line and it reported that it found 0 devices.  Uniflash does not detect anything either.

I searched the forums for an answer but haven't had any luck.  I have not changed any jumpers on my Launchpad and I confirmed this behavior with another Launchpad.

Unfortunately my setup is disconnected from the internet so I cannot use the ProjectZero nor do any OTA re-flashing. 

I feel like I'm missing a step - I uninstalled and re-installed everything with no change.

Any help would be greatly appreciated! :) Thanks!

  • 0
    TI__Guru**** 171224 points

    Hi,

    Ray233 said:
    When I plug in my Launchpad, I get the Windows message of "The USB device you connected malfunctions and Windows does not recognize it." In the Device Manager, it shows up under USB controllers as Unknown USB Device (Device Descriptor Request Failed).

    This tells me the host may be at fault (bad drivers, bad USB port) or the Launchpad may have a bad firmware programmed or perhaps is faulty. 

    The first scenario can be verified if the same Launchpad can work on a different USB port or even on a different host - that would help isolate the issue. 

    To address the second scenario, can you check the section Troubleshooting --> Flashing the Bootloader of the XDS110 page below? 

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

    If that procedure fails to recover the board, then a return or a new board is needed. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 30 points

    Thanks! I think that confirms its a driver issue.

    In Device Manager, I don't even see the "Texas Instruments Debug Probes" listed. I can't following the Troubleshooting guide as I am not even at that starting point.

    When I try to re-run the CCS setup, I don't see an options for the XDS debugger either.  I checked the ccs_install_9.2.0.00013 text file and don't see anything named XDS.  Under CCS_INFO: Components Available, I see SEGGER_J_LINK, BBONE_FTDI_DRIVERS, etc but nothing labeled XDS. 

    Other than running that xdsdfu program, is there some other way to confirm installation of the drivers?

  • 0 in reply to Ray233
    TI__Guru**** 171224 points

    Hi,

    Ray233 said:
    In Device Manager, I don't even see the "Texas Instruments Debug Probes" listed. I can't following the Troubleshooting guide as I am not even at that starting point.

    The section I mentioned talks about how to force the XDS110 device to run its default ROM bootloader and thus show up on the Control Panel - did you try the procedure there?

    Regards,

    Rafael 

  • 0 in reply to desouza
    Prodigy 30 points

    Hi, yes I did.  The xdsdfu still reports the same "Found 0 devices".

    However I did figure out the issue - I was using a USB extender (B->A) and I swapped to a different one, which fixed the issue.  Power was still being applied to the device but the data lines must have been getting mangled.

    Thank you for you help though - ruling out these other issues helped me track it down. :)