On Wed, Jan 11, 2017 at 01:01:23PM -0300, Lucas Vinicius Hartmann wrote: > I was writing a remote-bitbang-like implementation using an ESP8266 as a > JTAG-TCP or SWD-TCP bridge. I got it to work with a STM32F030F4P6 as target > and SWD as transport. Using pure bitbang made it awfully slow, disabling > naggle madi it better but not enough. > > I then had the idea to move the code for bitbang_exchange to the ESP, and it > got a lot better (under 15s program and boot, about 3s step over or run to > breakpoint). >
On 11.01.2017 17:14, Paul Fertser wrote: > Another question is if you care about performance why not implement > some protocol that supports proper queueing and then you won't need > the bitbang API at all. An interesting topic. Is there any protocol except remote bitbang already capable to use TCP transport? Paul, what protocol looks most suitable for TCP transport? My first idea was CMSIS-DAP (fairly well documented and available open source firmware). Tom ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
