On Sun, Jul 20, 2008 at 8:44 PM, Spen <[EMAIL PROTECTED]> wrote: >> The input I've seen is that multiple devices in a chain, only >> one of which is an ARM CPU can make any fixed scheme for reset fail. >> >> Rather I'm thinking that a reset procedure needs to be >> written in script form to handle the more contrived cases. >> > > Why cannot the advanced user/setup have access as they previously did?
Can you be a bit more precise? > I find it a real shame that i cannot set the the reset mode for each target > now. I understand that openocd must progress, and adding tcl is one of them, > but > i am finding some of the functionality > particularly reset becoming more and more limiting, unless i start using > tcl. What do you mean more and more? You have two outstanding issues that I know of: 1. gdb & resetart/reset. This looked relatively straightforward to handle in a better fashion, but I want the problem to stew a bit. 2. having reset(no parameters) do different things for different targets. The second is somewhat obscure and ingenious use of side effects of implementation. I don't want to complicate the implementation or the life of normal users, so I'm thinking in terms of a scheme that does not inconvenice normal users, but allows for more powerful target scripts to be defined. Also the second scheme is not very flexible. A more flexible way of handling targets becomes important with heterogenous chains as has been discussed on the list. -- Ø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
