This is a bug in Windows 10. There are a lot of similar complaints in MSDN forums. The bad news: only complaints, the bug never has been fixed by MS.
On Monday, May 29, 2017 at 8:07:45 AM UTC+2, Satz Klauer wrote: > > Hi, > > > I'm running a StarterWare 2 based application on an BBB which makes use of > a USB serial interface implementation based on the StarterWare example and > by using a .inf-File which is similar to "usb_dev_serial.inf" which was > provided by TI in same StarterWare package. Of course VID and PID have been > changed according to my own USB serial interface implementation. > > > This works well with all Windows-versions up to 7 (8.x was never tested) > and also with all Linux variants. But now with Windows 10 there is a > problem which was reported by different users of this application: > > - opening of the serial interface often fails, simple repeating of the > procedure then is successful latest after 10 tries > - sometimes an already opened connection seem to be corrupted, means > there is no more communication possible, host application needs to be > closed, device needs to be restarted - but after this, the same COM-port > is > available again, Windows does not change numbering > > So: is anything known about such problems in Windows 10 ? Perhaps are > there any changes necessary in an INF-file or in USB serial interface code > to make it work with Windows 10? Is there anything similar known from the > Linux Kernel of the BBB? > > > Any hint or idea is welcome! > > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c4db0882-0837-4058-8f52-07fe6a9703f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
