I see that I've jumped into a discussion where you are much more up to date on the overall reset_config, how to write quality documentation, etc. Below are some comments where I had any.
Q: What's a "system configuration file"? I can think of interface config files, target config files, board config files, the users config file.... >> + >> +If you have an interface that does not support SRST and >> +TRST(unlikely), > > Not unlikely at all. The 14-pin JTAG connectors > that TI uses don't pass SRST. The 10-pin JTAG > connectors that Atmel uses with AVR8 (and AVR32) > chips don't pass TRST. (Although there's a pin > reserved for TRST. It's unclear if *any* JTAG > adapters use that, since the only chips supporting > that signal are the unclear-future AVR32 AP7s.) So these are *targets* that don't need or want TRST? I was referring to the interface not supporting TRST. I don't understand how one could infer that srst is tied to trst by specifying trst_disable... W.r.t. #3 I'm not keen because it's nice to be able to tinker with various combinations from telnet instead of having to "reboot" the system... I'm also not entirely convinced that reset scripts might need to tinker with reset_config options during reset itself(seems far-fetch today though). -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
