It reminds me that flash could be probed on running target (at least on
most of Cortex M).
I removed the check
if (bank->target->state != TARGET_HALTED) {
LOG_WARNING("Cannot communicate... target not halted.");
return ERROR_TARGET_NOT_HALTED;
}
from kinetis_probe() and gdb happily gets memory map with running target.
On the other hand, gdb starts in unsynced state and it could be even
more confusing
for less experienced user.
Tom
On 10.03.2016 13:57, Uwe Bonnes wrote:
>>>>>> "Paul" == Paul Fertser <[email protected]> writes:
> Paul> Hey Uwe, On Thu, Mar 10, 2016 at 12:31:16PM +0100, Uwe Bonnes
> Paul> wrote:
> >> after loading the OpenSDA firmware
> >> http://www.keil.com/appnotes/docs/apnt_232.asp
>
> Paul> I think mbed's cmsis-dap implementation is a bit better, it
> Paul> additionally provides serial port and a mass storage device for
> Paul> reflashing.
>
> Thanks for the pointer!
> More explanation and a firmware is found at
> https://developer.mbed.org/handbook/Firmware-FRDM-KL25Z
>
> ...
> Paul> Alternatively, you can start
> Paul> openocd with additional ``-c "init; halt"'' command line switch
> Paul> when you're ready to halt the target.
>
> Thanks for the remainder for the command line switch.
>
> Bye
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
