On Monday 01 February 2010, Xiaofan Chen wrote: > > I do not think libusb0.dll is the problem. It is said that arm-jtag-ew > emulates the J-Link in low level API. It takes quite some for > OpenOCD to get J-Link working properly. So I will think the > first support is probably done by reverse-engineering and there > may be something missing in the process.
I kind of thought that Dimitar had an "in" at Olimex ... after all, he had pre-release access to the USB-TINY-H adapter too! Given the right "in", "reverse engineering" might not be needed. Regardless, as original author of that code, I've cc'd him to be sure he's aware of this reported problem on MS-Windows (modulo problems with too-much-email-to-read-it-all). > There are different firmware version for the J-link. They even > use different endpoints and supported command set are > not always the same. Maybe this is the case for Olimex > Arm-Jtag-EW as well. In that case, even if the original support > is good, it may not be good for yours. But the arm-jtag-ew driver isn't the same as the jlink driver... > The first thing to check is the USB Descriptors. You can > post yours. Probably the original author of the patch can > compare yours with his. > > Under Windows, you can use usbview to post the > USB descriptors. > http://www.ftdichip.com/Resources/Utilities.htm > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
