> >>> Thank you for the quick response. The openocd executable provided with > >>> the KDS seems to expect a CMSIS-DAP device and driver. We are using the > >>> Olimex ARM USB OCD H pod to connect directly to the JTAG pins on our MCU. > >>> I have tried modifying their scripts to use the Olimex driver instead, but > >>> it gave me errors about the CPU not being supported so I did not think > >>> that > >>> was the way to go. I will look into this more. > >>> > >> > >> > > > 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. 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 originally extracted from 'KDS v3.0.0 Source Files Package.zip' which is somewhere behind Freescale login area p. -- Peter Meerwald +43-664-2444418 (mobile) ------------------------------------------------------------------------------ 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
