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.

LAUNCHXL-CC1310: Instability of the Windows device driver: use usbser.sys instead?

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC2650

I have encountered problems with the device driver of CC13XX and CC2650 launchpads (that is, with the driver of the embedded XDS110). At least on Windows 7, if I don't "eject" the device from windows before I disconnect the USB cable, I often can't use the same lauchpad again on the same computer until I reboot. I assume that this is due to the Windows driver being left in some bad state.

My question is whether on machines in which I do not need the debug functionality, only the UART functionality, I can install an INF file that will tell Windows to use its own serial port driver, usbser.sys, rather than the TI drivers. I am pretty sure that this will work because on Linux, the built in CDC-ACM driver communicates with the launchpads without any problem, so the USB protocol is standard serial.

Will this work, and if anybody can comment on whether this will be more stable, I will appreciate it.

Thanks, Sivan Toledo

  • Actually, looking at the INF files that came with Smart RF Programmer 2, it looks like usbser.sys is used, not a TI serial driver. So I guess the bugs might be in usbser.sys. Too bad.
  • Hi Sivan,
    good idea and investigation. I also noticed some instabilities on the XDS110 driver, but only when putting my computer to standby while a debug session is running or when using SmartRF Studio while running a debug session or when removing the USB cable while having an open UART connection. But I have never observed directly the problem that you describe. I am also using Windows 7, 64 bit.
  • Thanks Richard. I also noticed the issues you describe (removing the usb cable when the port is open and suspend during debug). Maybe they caused me to be too careful and to eject before removing the cable. In any case, I think that FTDI bridges are more tolerant of these things, and I assume it's the Windows driver, not the devices themselves.