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. > Again this is a smart dongle, all the jtag/swi is done on the dongle. > Currently the simplest way of implementing this is to add the stlink as > a actual target, that way it gets access to reset/memory read etc. > > ideas on integration within openocd would be appreciated as this is the > next thing i may look at. Could you give a high level summary of the protocol requests to be issued to this device? For example, does it know that it's talking to e.g. a Cortex-M3 and have operations that only make sense for such a CM3? Also, how the commands need to be issued. If it presents itself as a mass storage device, it will be kind of painful to use on Linux without kernel patches. - Dave _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
