> I would prefer to create dedicated reset function in arm_adi_v5 if possible
> to use existing dp/ap read/write functions, to keep dap_ops interface
> functions as compact as possible, but if thats not possible the additional
> member of dap_ops seems unavoidable :-)
The reset function will control srst in SWD mode. The existing dp/ap read/write
functions will not be called.
> Do you need my support in this Simon? I would prefer to clean up the existing
> code and prepare for merge into openocd master, then still work on queueing
> mechanism / retry on existing queue to bring speed into reasonable level
> better than presented (what it the avg speed of versaloon btw?).. but if
> there are any more important tasks just let me know and Im here to help :-)
You can save your time and prepare for libswd.
What I need is the common points of view about how it should be implemented.
Below is the speed when programming flash of stm32 using versaloon.
For STM32 chips, it gets about 8KB/s - 12KB/s under SWD mode in OpenOCD.
In vsprog, it gets about 35KB/s because vsprog uses a double buffer operation,
which means data can be transmitted to ram of target stm32 via SWD while stm32
is doing the flash programming.
simonqian.openocd
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
