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>

diff --git a/doc/openocd.texi b/doc/openocd.texi
index 2cf1cbc278de1af79e0a2002e25a1eed507d51ba..c2ee20dea3e84517459f4575f4e148c2c35eff7b 100644 (file)
--- 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