Hi Alexander, thanks for your investigation.
> I'm using j-link debugger with arm11 target, and i have image loading > speed about 125 KiB / s. I have no experience with that target and barely use JTAG targets. What is your desired speed? What speeds do you achieve with other tools like the SEGGER J-Link Commander? > Moreover, the Jlink command handling is done sequentially in a > synchronous way. Exactly, the OpenOCD jlink driver and libjaylink code is synchonous - like all other driver implementations. > I tried to multiple both defines by 4 and it leads to increasing > pause to 15ms and group duration to 12ms. This is better than 2/5, > but still not effective. IIRC, the buffer size is fairly conservative to support older models that have problems with large buffers. > While increasing this defines by more than 4 times I bumped into > another problem. Jaylink transport API works incorrectly with such > bufer sizes You mentioned this in your message on the users mailing list. What exactly is broken in the API? I would like to fix that. > I want to try my best and refactor transport level to asynhronous > transfer via USB. It seems possible. I have 15 years experience of > embeded C programming. Could someone help me with design tools which > support autocomplete, go to definition and so on. I’m planning to do > it in a free from work time. I'm happy to give you support but please outline what exactly you want to implement and how. Do you already have a PoC with increased performance? Personally I use vim as editor and cannot suggest you an IDE or similar tools. Do not hesitate to contact me directly or ping me on IRC. Best regards, Marc _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
