From 27f0497efa3c4fe14510979c1fa6905be74ad43b Mon Sep 17 00:00:00 2001 From: Spencer Oliver Date: Thu, 18 Oct 2012 10:52:16 +0100 Subject: [PATCH 1/1] docs: mention extended-remote support Change-Id: Idd7cc0364856082cbbfee5015e49cd7d237d68ef Signed-off-by: Spencer Oliver Reviewed-on: http://openocd.zylin.com/913 Tested-by: jenkins Reviewed-by: Peter Stuge --- doc/openocd.texi | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/openocd.texi b/doc/openocd.texi index 2cf1cbc278..c2ee20dea3 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 -- 2.30.2