SW-DK-TM4C129X: Stellaris ICDI driver under Windows 11

Hi,

  I tried to load a simple program on EK-TM4C1294XL LaunchPad as well as DK-TM4C129X EVM on a Windows 11 machine and there is no issue. See below image. The easiest way for you to test is to plug in your LaunchPad to your Windows 11 machine. If it works, then there is no issue with the driver and it will work on both Windows 10 and 11 versions. You specify SW-DK-TM4C129X as the part number on your title. It is weird that your ICDI is by FTDI. The ICDI debug probe is enumerated by the TM4C123 chip on the board. It is not by FDTI. I think Windows is using the wrong driver. Perhaps in the past you might have a different board that uses FTDI chip to enemerate ICDI. In any case, download the ICDI drivers for Windows from https://www.ti.com/tool/STELLARIS_ICDI_DRIVERS and direct the Windows to pick up the right one. But if you have a different board that has a FTDI chip on it then it is a different story. 

Thanks for looking into this Charles.

I can explain the weirdness you noted - I got the dev kit part number wrong !   I am actually using the predecessor to the EK-TM4C1294XL which is the Stellaris LM3S9B96 Development Kit and your suspicion was right, it uses the FTDI chip FT2232 for the ICDI+virtual COM port interface,  and likely used different driver files.  In that case which driver files should I be using for Windows 11  ?

Thanks Charles.

If I only wanted to retain the Virtual COM Port (VCP) functionality and did not need the ICDI aspect is it theoretically possibly that a the Windows 11 driver from the FTDI website might work, or is there a technical reason why it can't  ? (e.g. the custom ROM of the FT2232 from TI to implement ICDI might preclude that from happening) 

My other option is to understand exactly why Windows 11 might be rejecting the driver and there might be a legacy setting in Windows 11 to permit it to accept Windows 10 drivers. 

Peter John said:

If I only wanted to retain the Virtual COM Port (VCP) functionality and did not need the ICDI aspect is it theoretically possibly that a the Windows 11 driver from the FTDI website might work, or is there a technical reason why it can't  ? (e.g. the custom ROM of the FT2232 from TI to implement ICDI might preclude that from happening)

I kind of doubt it will work but you can try to get the driver from FTDI and see if it will work. I think the FTDI will enumerate as a single USB composite device supporting both JTAG and serial interface. In my opinion the driver will either work for both or none and not just one of them. But I can't say for certainty as this is beyond my knowledge on how Windows driver for FTDI chip.

Peter John said:

My other option is to understand exactly why Windows 11 might be rejecting the driver and there might be a legacy setting in Windows 11 to permit it to accept Windows 10 drivers. 

That will be a thing to try too but again I don't think it will work. Your problem is at the USB enumeration between device and the host. Windows compatibility mode only comes later when you bring up an application like CCS. Anyway, try it and let me know if I'm wrong.  

OK thanks Charles.  I will try this out.  I'm unsure when I will be able to access the test PC to do this, but I will report back once I have some answers.