On May 22, 2012, at 11:14 , Xiaofan Chen wrote: > On Tue, May 22, 2012 at 1:25 PM, Liviu Ionescu <[email protected]> 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...
I'm a bit puzzled, Peter also mentioned that the J-Link "driver in OpenOCD [was] built by reverse-engineering a proprietary product". however, the J-Link USB protocol is described quite in detail in the publicly available document: http://www.segger.com/admin/uploads/productDocs/RM08001_JLinkUSBProtocol.pdf am I missing something here? > <support_jlink at segger.com> ok On May 22, 2012, at 11:19 , Xiaofan Chen wrote: > ... > To be fair to Segger, I think they do not intentionally change anything in > the firmware. ... > 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". that is really helpful. in this case I'll first try to look in the code and check if it conforms with the specs in the Segger manual. regards, Liviu ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
