I've been pondering reset.
It's built on the concept around events.
Another approach (backwards compatible) would be to
have a default reset tcl proc defined that the user can
override.
This reset proc would be written in startup.tcl and it
would invoke lower level ocd commands like "ocd_validate"
to validate the jtag chain.
To give you an idea of what this startup.tcl reset proc might
look like:
proc reset {args} {
jtag_speed $reset_speed
# send out pre_reset event for backwards compatibility
target_event pre_reset
jtag_init_reset
target_examine
target_assert_reset
target_deassert_reset
...
}
The point is that if something requires reset to be handled
differently for a target and the standard events don't cut it,
then pasting a new reset routine into the target config
script might do the trick.
We could add lots of events, but really having a well defined
sequence of operations is much easier to read/understand
at some point.
I believe a lot of users might be more comfortable with
todays events though, so we'd want to keep that as-is.
--
Ø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
