On 10/20/2013 02:57 PM, Paul Fertser wrote:
> Doesn't remote_bitbang that's already mainline fit all your
> requirements? Just use socat to redirect a unix or tcp socket to your
> serial port and you should be good to go. See tools/remote_bitbang/
> for an example client. HTH 

If this really takes off (ie. when there are embedded boards that make
use of this), an option to directly access a serial port in the bitbang
code without using socat might be useful.

Apart from the ease-of-implementation, I am not very fond of serial
ports for JTAG or SWD - it is slow, and basing a new protocol or
implementation on an outdated interface does not seem smart to me. While
this may be useful for a "i only need this once"-occasion to unbrick
some hardware, it will be annoyingly slow even for "JTAG beginners" to
really use.

There are enough MCUs and cheap starter boards out here that support
direct USB (STM32 discovery, newer Arduino using Atmega32U4 etc.), so a
good, high-performance USB protocol (which means queueing data and block
transfer, not remote bitbang) would be the way to go IMHO. As soon as
there is an open-source implementation for this, porting to different
CPUs should not be difficult.

I wonder if one of the existing HLA protocols might be useable.

Now I do not want to stop anyone from providing patches that implement a
serial protocol, but in my opinion, the spent time would yield a much
better result if it went into a real USB implementation, with enough
abstraction that it can be used on STM32, ATMega etc.. with different
USB stacks used.

cu
Michael


------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to