On Sat, Jan 26, 2013 at 11:25 PM, CeDeROM <[email protected]> wrote: > Integration part on the OpenOCD side is really small and simple (but > smart I guess) - AP/DP Reads/Writes are calling LibSWD routines when > SWD Transport is selected. When JTAG Transport is selected everything > happens as before. LibSWD use Interface Transfer/Bitbang routines to > manipulate electricity. I have additionally packed all ARM_DAP calls > into Interface Feature, so Interface can use different Features to > perform JTAG, SWD-LibSWD or its own SWD, or other tricks.
This is possible because ARM Target was already using separate DP/AP READ/WRITE functions. So it was necessary to swap the calls depending on the transport and create calls that will talk swd. Also generic bitbang/transfer needs to be implemented on the interface. Any interface that provides transfer/bitbang methods shall be able to talk swd using libswd. Current jtag_interface was only using flush() to flush jtag commands into the hardware. This made all interfaces jtag-only. Adding bitbang/transfer methods makes it possible to implement virtually any protocol on the interface. I have looked at the new MPSSE driver and it has already everything required to work with LibSWD Transport - transport and bitbang. Still I dont know how this relates to the jtag_interface. Did you change Interface desing? Is there any consistent Interface API in OpenOCD? Is it jtag_interface? -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
