OK I didn't know OpenOCD can still execute after connection, because I have
been seeing the fellowing output on the log when I try to attach a gdb to
the device.
Error: 550 17141 armv4_5.c:1052 arm_get_gdb_reg_list(): not a valid arm
core mode - communication failure?
Debug: 551 17141 gdb_server.c:1258 gdb_error(): Reporting -4 to GDB as
generic error
And then the gdb connection just get dropped. I guess if openOCD is suppose
to support execution after connection then the problem
is probably somewhere else then.
Thank you.
On Tue, Nov 22, 2011 at 2:23 AM, Øyvind Harboe (Code Review) <
[email protected]> wrote:
> Øyvind Harboe has posted comments on this change.
>
> Change subject: gdb: add config command to auto send halt cmd
> ......................................................................
>
>
> Patch Set 2:
>
> I think the manual should be improved to the point where users can figure
> out that they can use "monitor halt" immediately after a connect.
>
> A patch to improve the documentation would be very much appreciated.
>
> --
> To view, visit http://openocd.zylin.com/233
> To unsubscribe, visit http://openocd.zylin.com/settings
>
> Gerrit-MessageType: comment
> Gerrit-Change-Id: Ia1d55ab2596642dab485ac612ab7d5ad44b6da21
> Gerrit-PatchSet: 2
> Gerrit-Project: openocd
> Gerrit-Branch: master
> Gerrit-Owner: James Zhao <[email protected]>
> Gerrit-Reviewer: jenkins
> Gerrit-Reviewer: Øyvind Harboe <[email protected]>
>
--
James H.T. Zhao
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
