On Sun, Aug 14, 2011 at 7:51 AM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Sat, Aug 13, 2011 at 12:45 AM, Xiaofan Chen <xiaof...@gmail.com> wrote: >> Actually I think a easier way is now that you know 4.14g and >> lower firmware versions work whereas 4.14h and higher version >> firmware versions do not work. So a debug capture from OpenOCD >> may be already good enough to pinpoint the problem >> (with the "--enable-verbose-usb-comms" build option). >> >> An example from Spen last time. You can see that thread helped. >> http://lists.berlios.de/pipermail/openocd-development/2009-May/007464.html > > Here is the zip file which contains the connection logs of V3, > V6, V7 and V8 J-Link (to a TI/Luminary EK-LM3S1968 demo > board). The V7 is an ADI OEM version, the V3, V6 and V8 are > all IAR OEM version, all have been updated to their latest > supported firmware version under Windows. The logs are captured > with OpenOCD-0.5.0 release under 32bit Ubuntu 11.04. > http://code.google.com/p/picusb/downloads/detail?name=Openocd_usblog_Jlink.zip > > The init sequence is apparently quite different from Segger's > own utility. However, the good logs (V3, V6 and V7) are almost the same > as the bad one at the beginning.
And here is a zip file containing the initial connection usbmon log for different versions of J-Link using Segger's Linux utility. http://code.google.com/p/picusb/downloads/detail?name=usbmon_jlink_linux.zip -- Xiaofan _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
