> >> > A debugger should always select the appropriate target interface before > >> > it > >> starts communicating with the target, > >> > since otherwise it could also happen that a previous session with another > >> debugger had selected SWD and the interface was not switched again by > > OpenOCD. > > > > Hi, > > > > does it mean that OpenOCD and JLink can now support SWD as well ? Is there > any > > plan to add transport jlink_jtag and jlink_swd into OpenOCD ? > > > > No, it means Segger J-Link supports JTAG and SWD with Segger tools > (and IAR, etc). But OpenOCD does not support SWD on J-Link. >
Hi, I did not write that OpenOCD did it. But if JLink already has SWD support, OpenOCD _can_ (in the future) support this transport with JLink, as well. And my question was, if there were any plans to extend this support. Or JLink SWD commands are not publicly available from Segger ? ------------------------------------------------------------------------------ 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
