David Brownell <david-b@pacbell.net>:

Fix minor goofage in previous doc updates:

 * The ETM dummy driver name is "dummy" not "etm_dummy";
   re-alphabetize.

 * DCC trace message mode "charmsg" is a format type
   (and what Linux needs)

git-svn-id: svn://svn.berlios.de/openocd/trunk@1976 b42882b7-edfa-0310-969c-e2dbd0fdcd60

diff --git a/doc/openocd.texi b/doc/openocd.texi
index 55ad4005a662eca9555700e0a644d0a614d33809..ebb76f3c53a7fc8524352e65d0e03f606f560581 100644 (file)
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -3758,6 +3758,16 @@ Stops trace data collection.
 
 To use an ETM trace port it must be associated with a driver.
 
+@deffn {Trace Port Driver} dummy
+Use the @option{dummy} driver if you are configuring an ETM that's
+not connected to anything (on-chip ETB or off-chip trace connector).
+@emph{This driver lets OpenOCD talk to the ETM, but it does not expose
+any trace data collection.}
+@deffn {Config Command} {etm_dummy config} target
+Associates the ETM for @var{target} with a dummy driver.
+@end deffn
+@end deffn
+
 @deffn {Trace Port Driver} etb
 Use the @option{etb} driver if you are configuring an ETM
 to use on-chip ETB memory.
@@ -3767,16 +3777,6 @@ You can see the ETB registers using the @command{reg} command.
 @end deffn
 @end deffn
 
-@deffn {Trace Port Driver} etm_dummy
-Use the @option{etm_dummy} driver if you are configuring an ETM that's
-not connected to anything (on-chip ETB or off-chip trace connector).
-@emph{This driver lets OpenOCD talk to the ETM, but it does not expose
-any trace data collection.}
-@deffn {Config Command} {etm_dummy config} target
-Associates the ETM for @var{target} with a dummy driver.
-@end deffn
-@end deffn
-
 @deffn {Trace Port Driver} oocd_trace
 This driver isn't available unless OpenOCD was explicitly configured
 with the @option{--enable-oocd_trace} option.  You probably don't want
@@ -4186,8 +4186,11 @@ deliver messages before a serial console can be activated.
 @deffn Command {target_request debugmsgs} [enable|disable|charmsg]
 Displays current handling of target DCC message requests.
 These messages may be sent to the debugger while the target is running.
-The optional @option{enable} and @option{charmsg} parameters are
-equivalent; both enable the messages, @option{disable} disables them.
+The optional @option{enable} and @option{charmsg} parameters
+both enable the messages, while @option{disable} disables them.
+With @option{charmsg} the DCC words each contain one character,
+as used by Linux with CONFIG_DEBUG_ICEDCC;
+otherwise the libdcc format is used.
 @end deffn
 
 @node JTAG Commands