On Tue, May 22, 2012 at 1:25 PM, Liviu Ionescu <i...@livius.net> wrote: > I'd be happy if Segger would just disclose the changes in > the USB protocol, so we don't have to reverse engineer it.
I do not think that will happen... > do we have any contacts at Segger? > > I would first write to Segger and try to get an official statement from them. You can try, there is an email address in the thread. http://lists.berlios.de/pipermail/openocd-development/2011-August/020741.html <support_jlink at segger.com> >> Last time Segger did spend time to fix the issue and when I tried it, >> 4.33h beta firmware solved the problem > > there are no 4.33[a-z] at all on the Segger site > (http://www.segger.com/j-link-older-versions.html), from 4.32b they jump to > 4.34. Then you can try 4.34 release to see if that helps. > I currently have two J-Link V8 probes, one running the latest v6.46f and the > other running the old 4.14g, so it is relatively simple to run comparison > tests. > > any other comments on how to proceed? 1) Try 4.34 release and later versions to establish which version works and which FW version does not work with OpenOCD. http://lists.berlios.de/pipermail/openocd-development/2011-August/020651.html We knew that 4.10i and below seem to work, 4.20 to 4.30 does not work. 2) Reverse engineering, compare the Segger tools and OpenOCD 3) Come out with the fix if it is possible. -- 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
