On Sat, May 26, 2012 at 9:32 PM, Tomek CEDRO <tomek.ce...@gmail.com> wrote:
> The main difference between LibSWD and Versaloon approach is that LibSWD
> takes DAP operations and translates them to/from bitstream at host level so
> it can be applied to any interface which makes it very generic solution,
> while Versaloon takes DAP operations and transfers them into interface that
> takes care of bitstream generation/analysis which makes things faster over
> high latency links like USB but it requires complex firmware for
> interface...

Thanks. I tend to assume that intelligent (MCU based) HW debugger
will usually go the Versaloon route -- to use the firmware for the
value-added thingy.

Your generic approach is probably more suitable for the dumb
HW debugger like those FTDI based ones. So I would not say
that your approach is really generic but rather lowest denominator
approach -- without a brain on the HW debugger side, the host
has to take over.

I will assume that J-Link firmware has taken care some of the
things similar to Versaloon approach. So it is probably good to
forget about libswd for the J-Link SWD work, am I right to
say that?

The ST-Link is another example with SWD support, it only
offers high level API, the complexity is handled by FW.
So OpenOCD does support SWD with ST-Link, even without
much SWD codes on the OpenOCD side.
http://www.st.com/internet/evalboard/product/251168.jsp
http://www.st.com/internet/evalboard/product/219866.jsp
http://www.st.com/internet/evalboard/product/253215.jsp
(OpenOCD supports the STM32F0 which is SWD only
if using ST-Link).

-- 
Xiaofan

------------------------------------------------------------------------------
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

Reply via email to