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.

EK-TM4C123GXL: Board is not recognized by device manager when plugged in via USB (Windows 10 Pro)

Part Number: EK-TM4C123GXL
Other Parts Discussed in Thread: SW-TM4C

My Windows 10 Pro PC (build 19043.1165) does not detect the TM4C123GXL launchpad board when I plug it in via USB. There is no change in the device manager when the board is connected. I have attempted to manually load in the current ICDI drivers via add legacy hardware, but get an error code 10 for "This device cannot start."

The USB cable works and the board can be detected without problems on a different computer. I have also verified that I have it connected properly to the debug port and the switch is in the correct position as well.

For reference, I have SW-TM4C-2.2.0.295 installed, the latest ICDI drivers available, and am trying to use it with CCS 10.4.0.00006.

  • Hello Chloe,

    I have seen USB cables cause issues like this before. Can you try a different USB cable? Oddly that can sometimes cause the enumeration to fail.

    Regarding the driver installation, if swapping cables doesn't work, then:

    I have attempted to manually load in the current ICDI drivers via add legacy hardware, but get an error code 10 for "This device cannot start."

    I have not heard of trying to add them via legacy hardware. Can you just do a standard 'browse to find latest drivers' option for this? Maybe the 'legacy' element is not working with the drivers.

    FYI I am on Win 10 Pro 19042.1165 and my LaunchPad's are working perfectly fine without any issues, so my guess its either cabling or the driver installation.

    Best Regards,

    Ralph Jacobi

  • I tried with a different USB cable and it still did not work. Also browsing to find the latest drivers did not work either. Part of the issue is that the ICDI does not even appear in the list until added via legacy hardware. Scanning for hardware changes does not do anything.

  • Oops, did not mean to mark as resolved..

  • Hi Chloe,

    Do you have a different LaunchPad to try?

    I'm at a bit of a loss myself as I went ahead and uninstalled my drivers and it still was able to recognize it to the point I could do a traditional installation. I am not sure why your Win 10 Pro is behaving that way. Given we are on the same version, it basically leaves me with no way to re-create your issue on my end... the only thing I can think is maybe a PC restart, maybe a different USB port or if you are using a hub, to plug it in direct, or try another LaunchPad in case the hardware is the problem.

    Best Regards,

    Ralph Jacobi

  • Unfortunately, I have tried all of those suggestions. Different launchpad, restarted PC, different direct USB port, 2 different hubs. Thanks for your help though!

  • Hi Chloe,

    I will see if I can find a colleague in the coming days which has not used this LaunchPad before and attempt with their machine.

    Also just for complete sanity check - I know you mentioned you that you used the latest ICDI drivers but I just want to make sure you did get them from this link: https://www.ti.com/tool/STELLARIS_ICDI_DRIVERS - don't want to erroneously assume this.

    Best Regards,

    Ralph Jacobi

  • Great, thank you Ralph! Yes, I downloaded the drivers from that link; I got the current version from 21-Jan-2016.

  • Hi Chloe,

    I have tried this on two other machines for colleagues which are on Win 10 Pro 19042.1165 and have not run into any issues. Unfortunately without any way to replicate it on a PC, I'm honestly at a loss about what could be causing this. The amount of stuff you've tried is about every suggestion I can imagine, but I am not seeing anything Windows related that would cause that issue.

    I wouldn't even know how to do this but literally all the comes to mind is purging all drivers and history of the device so it'd appear as a fresh USB device.

    I guess one other looong shot would be to maybe install the latest CCS and have it install TM4C/Stellaris support drivers and maybe that cleans something up?

    Best Regards,

    Ralph Jacobi

  • Thanks for trying it out on your colleagues' machines! It's quite an interesting problem. My issues could be reproduced on my colleague's company issued laptop as well as my personal laptop. I don't believe there is a stored "history" of the device on my machine, because my computer was never able to detect it in the first place! I did try removing all the drivers and reinstalling, but still no luck.

    If you don't mind, what versions of CCS, Stellaris, and SW-TM4C do you have installed on your machine?

  • Hi Chloe,

    Up until recently I had CCS 9.3 installed. Now I have 10.4 as the latest. SW-TM4C is the latest, 2.2.0.295, and Stellaris ICDI is the 2016 one.

    The only thing I can potentially think of is maybe having at one point having CCS installed in the past helped or something. Given how widely used CCS is by engineers I know, I am not really sure how to find a Win 10 Pro machine which has never had CCS installed. But I wouldn't really understand why that would even be an issue, it shouldn't be, and also Win 10 Pro 19042.1165 has been out for a year now so if it was something fundamental then I would have expected a number of posts about this in the meantime, we have had plenty of first time users in the past year.

    Best Regards,

    Ralph Jacobi

  • Hmm those are the same versions that I have. Both of the company laptops that are having issues have never had CCS installed before, maybe I will try rolling back to an older version. Can you think of any security/permissions settings in Windows that the IT dept may have applied to prevent unknown devices from being recognized? We have been in contact with our IT dept, but everyone seems to be at a loss right now.

  • Hi Chloe,

    No idea on the IT front unfortunately... usually those are restrictions against applications. I've read of stuff like USB Flash Drives being restricted but that wouldn't make sense here. I feel like if the LaunchPad was being restricted, a USB mouse would be too...! It's just a simple CDC device in the end.

    Best Regards,

    Ralph Jacobi

  • Update: the issue is now resolved; it turns out it was a bad USB cable after all. When I had swapped the USB cable the first time, the replacement cable was also bad. Thanks for all your help Ralph!