You're right -- my mistake. The web page says: "ARM-JTAG-EW emulates on low level the IAR Systems' J-LINK API so it works like normal J-LINK debugger, ..." I took this to mean that they were emulating the USB protocol.
But a footnote in the manual says -- "DLL compatible means that we supply our own jlinkarm.dll. The original IAR-EW DLL will not work with the ARM-JTAG-EW device because ARM-JTAG-EW and IAR J-Link use different USB protocols." So that explains that then. The Olimex manual mentions SWD in the pinout table, so perhaps they have the necessary hardware already. Might give it a shot with libswd but I need to get moving on this project .. On Wed, Oct 19, 2011 at 8:52 AM, jim norris <u17...@att.net> wrote: > > Well, the ARM-JTAG-EW is not an FT2232 device as far as I can tell -- it's >> supposed to be a JLink clone for IAR >> > Yes it is. It has an FT2232D chip in. If you open it up (and void the > warranty!) you can see it. > However, using the ARM-JTAG-EW to do SWD is not just a software change. As > Tomek > implied in the previous email, one needs to understand the pinouts. JTAG > typically uses > 5 pins, while SWD uses 2 pins. So there are some hardware ramifications > when using a > FT2232 device for SWD versus JTAG as typically found in most debuggers. > > > -- Quidquid latine dictum sit, altum viditur.
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
