On Mon, Aug 15, 2011 at 5:26 AM, Jean-Christophe PLAGNIOL-VILLARD <plagn...@jcrosoft.com> wrote: > On 12:04 Sat 13 Aug , Carlson Gary wrote: >> Hi Eric, >> >> I have worked a little on the jlink stuff in the past and fixed a few >> problems with OpenOCD. I have a new project that is going to force me to >> buy an unrestricted Segger very shortly since my current jlink dongles are >> Atmel-only devices. Once I get my hands on a new one, I hopefully will be >> able to take a look at this problem also. >> >> I will try to contact Segger on Monday to see if they can shine some light >> on V8 communication details. I suspect whatever is wrong is probably minor, >> but will take a little persistence to identify a solution. > I already contract Segger this year and their answer are we change nothing > > I put segger in Cc this time on the ML hope you will work with us to improve > J-Link support on OpenOCD >
To be fair to Segger, I think they do not intentionally change anything in the firmware. After all, the firmware needs to be compatible with their own utility under Windows and Linux. On the other hand, they probably did not test OpenOCD since that was not their focus. >From the usbmon log, Segger's Linux utility are consistent through different versions of J-Link. The main issue is that OpenOCD's J-Link initialization sequence is not the same as Segger's utility, as shown in Eric's previous email. I think Gary is probably correct that "whatever is wrong (in OpenOCD) is probably minor". -- Xiaofan _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
