From 348bc74af44d759b3ed8c8e3b4a4c686e86a88d7 Mon Sep 17 00:00:00 2001 From: oharboe Date: Fri, 11 Jul 2008 06:52:33 +0000 Subject: working notes. git-svn-id: svn://svn.berlios.de/openocd/trunk@788 b42882b7-edfa-0310-969c-e2dbd0fdcd60 --- src/scripting.txt | 28 +++++++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/src/scripting.txt b/src/scripting.txt index 059bc85a..ae917666 100644 --- a/src/scripting.txt +++ b/src/scripting.txt @@ -51,4 +51,30 @@ Default implementation of procedures in tcl/procedures.tcl. has two choices a) parse the output from flash_banks or b) write a small piece of tcl to output the flash_banks output to a more suitable form. The latter may - be simpler. \ No newline at end of file + be simpler. + + +External scripting +================== +The embedded Jim Tcl interpreter in OpenOCD is very limited +compared to any full scale PC hosted scripting language. + +The goal is to keep the internal Jim Tcl interpreter as +small as possible and allow any advanced scripting, +especially scripting that interacts with the host, +run on the host and talk to OpenOCD via the TCP/IP +scripting connection. + +Another problem with Jim Tcl is that there is no debugger +for it. + +With a bit of trickery it should be possible to run Jim +Tcl scripts under a Tcl interpreter on a PC. The advantage +would be that the Jim Tcl scripts could be debugged using +a standard PC Tcl debugger. + +The rough idea is to write an unknown proc that sends +unknown commands to OpenOCD. + +Basically a PC version of startup.tcl. Patches most +gratefully accepted! :-) -- cgit v1.2.3