From e4056cca2d10da3a746ebfa01799165140640071 Mon Sep 17 00:00:00 2001 From: Øyvind Harboe Date: Tue, 20 Apr 2010 09:05:07 +0200 Subject: doc: gdb-attach can fix gdb connect issues MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Flash probing must succeed for e.g. gdb load and automatic hardware/software breakpoints to work. Signed-off-by: Øyvind Harboe --- doc/openocd.texi | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/openocd.texi b/doc/openocd.texi index bb8f3abb..5273d5de 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -3784,7 +3784,8 @@ proc my_attach_proc @{ @} @{ mychip.cpu configure -event gdb-attach my_attach_proc mychip.cpu configure -event gdb-attach @{ echo "Reset..." - reset halt + # To make flash probe and gdb load to flash work we need a reset init. + reset init @} @end example @@ -3804,7 +3805,11 @@ The following target events are defined: @* Currently not used (goal: when JTAG examine starts) @end ignore @item @b{gdb-attach} -@* When GDB connects +@* When GDB connects. This is before any communication with the target, so this +can be used to set up the target so it is possible to probe flash. Probing flash +is necessary during gdb connect if gdb load is to write the image to flash. Another +use of the flash memory map is for GDB to automatically hardware/software breakpoints +depending on whether the breakpoint is in RAM or read only memory. @item @b{gdb-detach} @* When GDB disconnects @item @b{gdb-end} -- cgit v1.2.3