I am sorry, I misspoke. The error was not an unsupported CPU, it was that
the kinestis configuration only defines one flash bank so that when we
attempt to program it, the flash operation immediately fails.
The gdb console indicates that it attempted to load the .text section and
failed. When we use our custom make config it succeeds through loading all
sections and only fails at the end with FSTAT.
The openocd console indicates that there was a block write error, among
others:
Error: JTAG-DP STICKY ERROR
Error: MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40004
Error: JTAG-DP STICKY ERROR
Error: MEM_AP_CSW 0x23000052, MEM_AP_TAR 0x40004
Warn : Block write error address 0x40000, wcount 0x400
On Fri, May 15, 2015 at 6:29 PM, nothing fire <[email protected]> wrote:
> 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.
>
------------------------------------------------------------------------------
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
