This is an automated email from Gerrit. Antonio Borneo ([email protected]) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/5285
-- gerrit commit c8709448d9e98065246ef148af25f14d50cfc5c4 Author: Antonio Borneo <[email protected]> Date: Fri Aug 23 16:07:12 2019 +0200 doc: replace example command "interface" with "adapter driver" Keep documentation consisted after commands renaming. Change-Id: I97b43887cae9d7c224b07e4ba0b7d04915a19fc4 Signed-off-by: Antonio Borneo <[email protected]> diff --git a/doc/openocd.texi b/doc/openocd.texi index 6b70c72..dbb1b97 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -2335,7 +2335,7 @@ A few cases are so simple that you only need to say what driver to use: @example # jlink interface -interface jlink +adapter driver jlink @end example Most adapters need a bit more configuration than that. @@ -2716,7 +2716,7 @@ For example, to connect remotely via TCP to the host foobar you might have something like: @example -interface remote_bitbang +adapter driver remote_bitbang remote_bitbang_port 3335 remote_bitbang_host foobar @end example @@ -2725,7 +2725,7 @@ To connect to another process running locally via UNIX sockets with socket named mysocket: @example -interface remote_bitbang +adapter driver remote_bitbang remote_bitbang_port 0 remote_bitbang_host mysocket @end example @@ -3033,7 +3033,7 @@ For example, the interface configuration file for a classic ``Wiggler'' cable on LPT2 might look something like this: @example -interface parport +adapter driver parport parport_port 0x278 parport_cable wiggler @end example -- _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
