From f2dc1eeef159f00bc5c1f5bbd99b1761f3df0ae1 Mon Sep 17 00:00:00 2001 From: dbrownell Date: Wed, 7 Oct 2009 15:56:11 +0000 Subject: [PATCH] Note bug in handling of variables through command line parameters. git-svn-id: svn://svn.berlios.de/openocd/trunk@2819 b42882b7-edfa-0310-969c-e2dbd0fdcd60 --- TODO | 4 ++++ doc/openocd.texi | 8 ++++++++ 2 files changed, 12 insertions(+) diff --git a/TODO b/TODO index a2ee398bf..6efca5166 100644 --- a/TODO +++ b/TODO @@ -23,6 +23,10 @@ This section provides possible things to improve with OpenOCD's TCL support. - provide more directory structure for boards/targets? - factor configurations into layers (encapsulation and re-use) +- Fix handling of variables between multiple command line "-c" and "-f" + parameters. Currently variables assigned through one such parameter + command/script are unset before the next one is invoked. + - Isolate all TCL command support: - Pure C CLI implementations using --disable-builtin-tcl. - Allow developers to build new dongles using OpenOCD's JTAG core. diff --git a/doc/openocd.texi b/doc/openocd.texi index 11267fc08..4d68ae523 100644 --- 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.