This is one of several low-level interface changes that will
support SWD ... obviously not for the 0.4 release, but I'm
posting it now as an FYI/RFC.

 - Interface level patch:  add a call to clock bits out on TMS.
   Switching between JTAG and SWD modes involves some magic
   sequences here.  The same mechanism is general enough to
   handle the JTAG state machine too, moving it up a level (into
   the JTAG midlayer) for JTAG adapters that want it.

 - Use that from the midlayer, if the underlying JTAG adapter
   driver supports the mechanism (most could) ... helps drivers
   avoid needless differences in JTAG state transitions.

 - Implement FT2232 support.

In short ... this is structured to be useful even without SWD.

Other low level changes to support SWD will address things like
individual request/response transactions, plus link and target
initialization updates.

Plus ideally some cleanup of the interfaces at the "JTAG" level,
to address the fact that not all debug links are JTAG, and that
some of them can switch between JTAG and SWD modes.  See the
first patch for some comments reflecting my thoughts there.

I think the rest will be higher level things, at the level of
ADIv5 being aware of which transport to use.

- Dave
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to