> I suppose reviewing this would be a good start?
I don't know what you meant to refer to. But the first thing to do when developing a new jtag interface driver for OpenOCD is to find out what needs to be done to interact with the interface - not how to fit this into the OpenOCD source base. So, some research/searching needs to be done to find out if/how software can interact with this device. I did a bit of searching but couldn't find anything obviously useful. In some cases, there is no open source code for a driver. In that case it may be necessary to reverse engineer how to use software to interact with it. I don't know if the XDS110 and XDS200 devices are similar and if the existing XDS110 OpenOCD driver is of any use as a starting point. Or maybe they are very different and the XDS200 needs completely different software support. --- ** [tickets:#364] Add support for XDS200 debug adaptor** **Status:** new **Milestone:** 0.10.0 **Created:** Thu Sep 08, 2022 09:30 PM UTC by Rock Boynton **Last Updated:** Thu Sep 08, 2022 11:49 PM UTC **Owner:** nobody Please add support for TI's XDS200 debug adaptor https://www.ti.com/tool/TMDSEMU200-U. It is a more performant than the already supported XDS110. --- Sent from sourceforge.net because openocd-devel@lists.sourceforge.net is subscribed to https://sourceforge.net/p/openocd/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
