X-Git-Url: https://review.openocd.org/gitweb?a=blobdiff_plain;f=src%2Fscripting.txt;h=cc8f59713cc42cd28461ad10b576df95787d45f3;hb=0b6c73ae8398964268d2df6f87347d9c59b04858;hp=059bc85ad01a9b7d7d083d439b5b00aadac38dbe;hpb=313547ddd66b3dc7a8f1c6261621d26939d9d524;p=openocd.git diff --git a/src/scripting.txt b/src/scripting.txt index 059bc85ad0..cc8f59713c 100644 --- a/src/scripting.txt +++ b/src/scripting.txt @@ -31,7 +31,7 @@ Default implementation of procedures in tcl/procedures.tcl. is to ignore serial number and write a raw binary file to beginning of first flash. Target script can dictate file format and structure of serialnumber. Tcl allows - an argument to consit of e.g. a list so the structure of + an argument to consist of e.g. a list so the structure of the serial number is not limited to a single string. - reset handling. Precise control of how srst, trst & tms is handled. @@ -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! :-)