On Sun, Jul 20, 2008 at 11:16 PM, Tim Hudson <[EMAIL PROTECTED]> wrote:
> Øyvind Harboe wrote:
>> I need to test these changes.
>> Comments welcome!
>
> -jtag_khz 10, 3000
> +
> +jtag_khz 3000
> +proc target_0_pre_reset {} {
> + jtag_khz 10
> +}
> +proc target_0_post_reset {} {
> + jtag_khz 3000
> +}
> +
>
> Now this one I really don't understand in terms of what are the benefits of
> changing the syntax of a well established and used command? What was there
> before was simple and easy to follow - and now you have to define two event
> procs to handle it - that does seem like a regression.
You can use target_script command if you want.
I just chose to use target event scripts to avoid lots of extra files.
> Is there some point in time at which the configuration API will get locked
> down?
We have a number of outstanding issues and this is an open source
project, so giving times doesn't make any sense.
> One other scripting use case - assuming that an openocd version number is
> available and that we end up with major.minor.bugfix numbering then scripting
> could be used to have target scripts which work unchanged across multiple
> openocd versions.
If someone comes forward with the resources to handle this sort of release
scheme, then I don't think anyone will object.
There is some work in progress to fix the web site and introduce stable
branches. We'll see if someone steps forward to maintains table branches.
--
Ø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
