On May 26, 2012, at 17:00 , Xiaofan Chen wrote: > I will assume that J-Link firmware has taken care some of the > things similar to Versaloon approach
J-Link provides a function named EMU_CMD_HW_JTAG3, which sends a number of bits to the debugged device and returns the same number of bits. it is used for both JTAG and SWD, based on the selection done with EMU_CMD_SELECT_IF. when SWD is selected, the tin/out transactions are done separately. there is also a command called EMU_CMD_HW_JTAG_WRITE, that does only the sending. > So it is probably good to > forget about libswd for the J-Link SWD work, am I right to > say that? libswd or not, some layer above the J-Link driver needs to prepare these sequences of bits, in a similar way as JTAG layer does now. I think that the first aproach would be to use a generic layer, that can support any driver, and later eventualy optimise for specific interfaces. regards, Liviu ------------------------------------------------------------------------------ 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 OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
