> originally flash banks sent its output to command_print, can tcl not have > its own output handler and then parse the data there?
I'm not sure what you are proposing. Parsing is painful and unecessary; I'm trying to avoid it. Also I want to avoid that the output from the "flash banks" command becomes part of the OpenOCD scripting API. "flash banks" outputs information about the banks in human readable form that can and should mutate over time to remain as legible as possible for humans. I've made a single example of a scripting API function (flash_banks) vs. a telnet presentation command (flash banks). The idea is not to rewrite everything to tcl, but to have a single example of the difference between the two. The "flash_banks" fn is currently written using the Jim API, but it could also just print the list using command_print(). To Tcl it is all just strings. Of course flash banks is just something I picked as an example that was sufficiently complicated to be interesting yet out of harms way and simple enough not to complicate experiments. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
