On Tuesday 15 September 2009, Øyvind Harboe wrote: > Can we strip away the "memory" from reset_config? > > I.e that it just *sets* the flags, ignoring any previous state.
It just sets what you tell it to set ... ignoring anything you didn't tell it to change. No confusion possible! There are no hidden/automagic changes carried out on your behalf. I'm opposed to changing that because it would make it impossible to just tweak the *existing* JTAG adapter configuration without crapping on unrelated stuff you have no reason to know about. > If target & board scripts need to communicate they can do it in > tcl. Actually, they can't ... not without mechanisms (or at least conventions) that don't exist today. A change that could be useful is adding a way to see that config data in TCL. Maybe just having the no-params "reset_config" call return the currently-applicable strings. (Not display; return, so TCL scripts can use those values.) > I was thinking about adding a "srst gates jtag clk" flag and > my head hurts just thinking about how to do this > in reset_config today. I can't comprehend any difficulty. You define a bitmask with the flag. You update the option parsing code to accept names for both flag settings. You're done. (Unless we get a way to return the config to TCL, in which case those names need to be dumped too.) - Dave _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
