OpenOCD needn't be Versaloon specific, because Versaloon can be OpenOCD specific.
Actually, new JTAG driver of Versaloon in OpenOCD is only designed for OpenOCD, vsprog uses another driver. I can decide how to implement SWD driver in OpenOCD, and maybe it's also different than SWD driver in vsprog. So I haven't provide latest versaloon driver, because I'm not sure that SWD driver will be the same. But I'm sure that I can make things working when SWD support is ready in OpenOCD. 2010/7/27 Peter Stuge <pe...@stuge.se> > David asked me to forward his reply also to the list. > > David Brownell wrote: > > --- On Mon, 7/26/10, Peter Stuge <pe...@stuge.se> wrote: > > > > > Can you say if the Versaloon firmware is a good > > > fit for the SWD operations that OpenOCD likes > > > to perform? > > > > I can't say that yet ... pending SWD support in > > OpenOCD, which must NOT be versaloon-specific. > > > > There will be two types of SWD patch forthcoming: > > > > (a) infrastructure, which I'm working on; > > (b) driver support, building on (a). > > > > The Versaloon support will be (b) variants. > > > > - Dave > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > -- Best Regards, SimonQian http://www.SimonQian.com
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
