aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSpencer Oliver <spen@spen-soft.co.uk>2012-10-18 10:52:16 +0100
committerPeter Stuge <peter@stuge.se>2012-10-18 16:10:55 +0000
commit27f0497efa3c4fe14510979c1fa6905be74ad43b (patch)
tree62720a78b42c5720f328a2871fcc19b951dfc68e /doc
parent7165e05cf64f5c24177239f9f9db577b45f1b52c (diff)
docs: mention extended-remote support
Change-Id: Idd7cc0364856082cbbfee5015e49cd7d237d68ef Signed-off-by: Spencer Oliver <spen@spen-soft.co.uk> Reviewed-on: http://openocd.zylin.com/913 Tested-by: jenkins Reviewed-by: Peter Stuge <peter@stuge.se>
Diffstat (limited to 'doc')
-rw-r--r--doc/openocd.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/openocd.texi b/doc/openocd.texi
index 2cf1cbc2..c2ee20de 100644
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -7579,6 +7579,11 @@ A socket (TCP/IP) connection is typically started as follows:
target remote localhost:3333
@end example
This would cause GDB to connect to the gdbserver on the local pc using port 3333.
+
+It is also possible to use the GDB extended remote protocol as follows:
+@example
+target extended-remote localhost:3333
+@end example
@item
A pipe connection is typically started as follows:
@example