On Sat, May 16, 2015 at 8:00 AM, Peter Meerwald <[email protected]> wrote:


> > This was all done with the openocd executable that I build locally.  I
> > haven't actually been able to run the KDS openocd executable (which was
> > your original suggestion) because our interface scripts target the ft2232
> > and the KDS openocd executable does not have that interface available.  I
> > will work on porting our configuration scripts to use the ftdi interface,
> > if possible, and try it with the KDS executable.


This should be a simple matter of sourcing
interface/ftdi/olimex-arm-usb-ocd-h.cfg instead of whatever ft2232-related
you're sourcing now.

Also, if you have the ft2232 interface in your locally build OpenOCD,
either you've manually enabled that legacy interface during configure, or
you're using a very old version. Please try with 0.9.0rc1 since IIRC there
have been a number of kinetis fixes lately.

> Would you be able to
> > provide a link to the patch file that indicates the differences between
> > what is packaged with the KDS and what is available in the openocd repos?
> >
>
> find it here:
> http://pmeerw.net/openocd-0b26376_kds-2.0.0.patch
>
>
I applied this patch and pushed to http://openocd.zylin.com/2773 if someone
wants to try it out (Download -> Checkout).

/Andreas
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to