Note bug in handling of variables through command line parameters.

[openocd.git] / doc / openocd.texi

diff --git a/doc/openocd.texi b/doc/openocd.texi
index 11267fc08786706a8400b5ba892029c8a04594b6..4d68ae523d956d01b60cd2b42c983742870dc217 100644 (file)
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -670,6 +670,14 @@ each supporting a different development task.
 One might re-flash the board with a specific firmware version.
 Another might set up a particular debugging or run-time environment.
 
+@quotation Important
+At this writing (October 2009) the command line method has
+problems with how it treats variables.
+For example, after @option{-c "set VAR value"}, or doing the
+same in a script, the variable @var{VAR} will have no value
+that can be tested in a later script.
+@end quotation
+
 Here we will focus on the simpler solution:  one user config
 file, including basic configuration plus any TCL procedures
 to simplify your work.