On Wednesday 10 March 2010, David Brownell wrote:
> Start decoupling the two concepts ("debug adapter driver", "jtag")
> by having two command groups, which initialize separately.
>
> This will help us support OpenOCD sessions using only non-JTAG
> transports, in which JTAG commands should not be registered.
> Update docs to mention that the JTAG, SVF, and XSVF commands
> won't work without a JTAG transport.
>
> Note that at least commands working with SRST are still inappropriately
> coupled to JTAG ... inappropriate because (a) they're not really part
> of the JTAG standard, and also (b) because they're used with non-JTAG
> debug and programming interfaces, too. They should perhaps become
> generic "interface" operations at some point. (Similarly with the
> clock rate to be used by a given adapter.)
Hmm ... right now I'm thinking of a followup to this patch, which will
add a "struct debug_driver" to hold SRST and clock methods.
One of those would be embedded within "struct jtag_interface" (which is
a misnomer for "struct jtag_driver"). That way the commands which are
relatively generic can become "interface_*" commands not "jtag_*" ones...
so they'll be usable with other transports, like SWD (and eventually SPI, if
someone wants to support some interfaces for "programming" not "debugging".
(Versaloon, Bus Pirate, and Signalyzer seem like good candidates for that.)
That will of course be circulated for review. It'll obviously be rather
invasive since it'll have to touch every JTAG adapter driver, but the
changes will be trivial.
- Dave
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
