Hello, On Tue, Feb 09, 2016 at 11:26:29AM +0100, [email protected] wrote: > I try to evaluate a product idea. A JTAG adapter that communicates > over bluetooth. While I’m pretty sure, what the bluetooth part > means, I’m very unsure about the JTAG part. The main purpose of the > device would be debugging and flashing micro controllers. As the > adapter will contain a micro controller, I think it will be a > „smart“ adapter (in opposite to ftdi based adapters).
Have you considered a cheap (~10$) single-board computer with an off-the-shelf USB debug adapter instead? So that the SBC would run OpenOCD the usual way and one would control it with BNEP or WiFi networking? > Where could I start to get a better understanding on what it means > to implement support for a JTAG adapter in openocd? It depends on how much low level you want to get it. If you're looking for raw JTAG and SWD, then MPSSE protocol can serve as an example. CMSIS-DAP is a bit higher level for SWD and JTAG but it also supports raw JTAG pass-through (not implemented in OpenOCD yet). ICDI or STLink are almost gdb serial protocol level. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
