On Wed, Feb 3, 2010 at 8:18 AM, David Brownell <[email protected]> wrote: > On Tuesday 02 February 2010, Spencer Oliver wrote: >> I have been given all the info for the ST-LINK from ST. >> http://www.st.com/stonline/products/literature/um/15285.pdf >> >> It is accessed using vendor specific mass storage cmds. > > You mean, it enumerates like a mass storage device? Yeech. > > Sigh. That's presumably because Microsoft make it so extremely > painful to support custom USB peripherals on Win32. Custom > vendor interfaces *should* be easy, there's a nice clean slot > for them in the USB architecture. >
With WinUSB, it is pretty easy for Windows as well. It does have its limitation (no isochronous transfer support, XP or later) but it is good enough for many use cases. libusb-win32 is early though but it has its limitations as well (64bit problem: need a digital signature). The latest libusb 1.0 Windows WinUSB backend is getting quite mature and I expect it to be merged into the main libusb 1.0 git tree soon. I think it will benefit libftdi and OpenOCD http://www.libusb.org/wiki/windows_backend -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
