I think we have gotten far enough that we can start writing up
the API rules in openocd.texi
Committed the attached patch as a start.
Patches most gratefully accepted! Anyone who writes up the
API rules gets a pretty free hand in the definition ;-)
--
Øyvind Harboe
Øyvind Harboe wrote:
On Mon, Jul 14, 2008 at 11:18 PM, Jonathan Larmour [EMAIL PROTECTED] wrote:
Øyvind Harboe wrote:
That's not true for OpenOCD.
So what's the best way to proceed here?
Make Jim Tcl + LGPL?
I didn't think you were able to change the licence of Jim or OpenOCD, as you
would
On Tue, Jul 15, 2008 at 4:34 PM, Jonathan Larmour [EMAIL PROTECTED] wrote:
Øyvind Harboe wrote:
On Mon, Jul 14, 2008 at 11:18 PM, Jonathan Larmour [EMAIL PROTECTED] wrote:
Øyvind Harboe wrote:
That's not true for OpenOCD.
So what's the best way to proceed here?
Make Jim Tcl + LGPL?
I
Øyvind Harboe wrote:
I believe the intention of the Jim Tcl licensing was to make it as
flexible as possible. Jim Tcl is intended to be embedded into
some other product, open source or not, that has the
overall license for the product.
Would
Hi,
if i setup a target reset script, eg.
target_script 0 reset debug.script
debug.script contains
echo hello
flash info 0
shutdown
nothing seems to get executed - ok if i call from the telnet prompt.
I see the following in the debug log, so the script is being called.
Debug: 174 1000
