Øyvind > I want that same protocol to be available via the GDB mon command.
I do not think I have explained the problem well. I believe what you want exists right now. Today - in GDB, any command works - at the GDB prompt, you prefix it with "mon" so GDB knows to pass it through. Today - in the telnet interface - any command works. The port requires no prefix, and executes both tcl & openocd commands. If both mistakenly define the same command - one of the two wins, I forget who. Today - with the tcl port - all commands are assumed to be tcl by default. You must explicitly prefix openocd commands with "openocd". ======= Here is the problem: How would you propose handling errors, success, and those types of things. As Pavel Chromy put it differently. Pavel>It is absolutely true that using GDB mon is not much suitable for Pavel> real scripting from external application, e.g. it lacks passing a Pavel> machine readable error code to the caller. My question is (and suggestions are about) how can that be simplified and standardized? ====== _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
