On Mon, May 21, 2012 at 11:31 PM, Tomek CEDRO <[email protected]> wrote: > On Mon, May 21, 2012 at 11:26 PM, Andreas Fritiofson wrote: >> Just did a quick check and this looks mildly like what I implemented >> inside the new ftdi driver to be able to configure reset signal layout >> from Tcl to replace the layout specific mess that clutters the ft2232 >> driver. > > So we did almos the same thing :-)
Yes, but for different purposes, it seems. >> I still don't get what this has to do with SWD. I think a SWD driver's >> interface to the OpenOCD side should be as high level as possible, not >> twiddling bits. But I would have to dig deeper to make sense of it and >> give any useful feedback and I haven't got time for that now. > > Nah, it works like LibSWD captures calls from Target at Transport > level, then generates/analyzes bitstream, then push it in/out using > generic driver - these are two functions "transfer" that can send > packed bitstream and "bitbang" to freely toggle/read any pin state of > the connector (to drive SRST or the buffers that drive RnW). This is > why LibSWD can be used with any other software But then not with any other hardware? The hardware needs to be able to stupidly toggle pins without knowing anything about what it actually means. That pretty much rules out all but FT2232 based interfaces (and parport, but who cares) so why not just make the SWD driver for FT2232 contain the functionality provided by LibSWD? If I'm getting anything at all, LibSWD is more of an adapter driver to OpenOCD than a framework for SWD in OpenOCD? Hierarchically it would be a sibling to, say, the SWD driver for J-Link adapters. In any case, I'm more interested in "the other side" of LibSWD, namely the one connecting to OpenOCD. /Andreas ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
