Re: [OpenOCD-devel] J-Link v8 with FW newer than May 20, 2010?

[Alexander O. <si...@gm...>]

It would be nice to print a warning message about unsupported firmware.

2012/5/22 Xiaofan Chen <xia...@gm...>:
> On Tue, May 22, 2012 at 1:25 PM, Liviu Ionescu <il...@li...> wrote:
>>
>> anyway, I don't think we should expect Segger to update their
>> firmware to work with OpenOCD, we should update OpenOCD to
>> make it work with all Segger firware versions.
>
> You can always try to get Segger to help if their firmware updates
> solved the problem.
>
> On the other hand, this was my take on the issue and my view does not change.
>
> +++++
> http://lists.berlios.de/pipermail/openocd-development/2011-August/020695.html
>
> 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".
> ++++++
>
> We just need to iron out the "minor" issues in OpenOCD to solve
> the problem.
>
> --
> 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
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openocd-devel