Hi Salvador, thank you for deep description, comments are below
> Take a look at > http://openocd.sourceforge.net/doc/doxygen/html/index.html, but probably > you know it already. I did not know that pages. > /** > Stupid libusb does not offer async writes nor does it allow > access to its fd - so we need some hacks here. > \internal > */ That in maybe the reason why communication is so slow on MS Windows. It might be worth to somehow collect requests and send bigger packets through libusb. Or another idea - is it possible to try binary drivers from FTDI on Windows ? I mean, not to use libusb/libftdi at all. Then we can compare speed of MDW. This however does not solve the problem for other interfaces like jlink,etc... > You have reported that the mdw...1024 now takes 25 or 30 seconds instead > of the initial 180. I don't know the reason. Reason is that I just try the same on different PC (but again with Windows XP OS). I plan to try it on Linux, but no time for it so far. > But can you now flash your > chip with a working are defined? > For me this mdw...1024 command takes 6.7 seconds, but for programming 4k > of flash only 0.7. So i expect your adapter can do it in 3 or 4 > seconds. If not, why not?. I did not try that again. I will do it and tell you. In the meantime, I analyzed JTAG debugger from PIC32 starter kit. It is really fast debugger. But it seems to me that all JTAG routines are implemented in the MCU connected to PC. So communication through USB is quite high-level. Vaclav ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
