On 04/11/2012 08:22 AM, Vaclav Peroutka wrote: > > UPDATE: I switched off the debugging (-d 2 parameter) and run it again. PIC32 > was programmed correctly. Programming of 6800Bytes took 5100 seconds! Can I > do some profiling of OpenOCD ? There must be something wrong inside... I > don't know if it is libusb driver or openocd itself... > I use -d3, to see as much as possible.
Only for comparing, how much time takes it for this command: " (gdb) monitor mdw 0xa0000000 1024 " ?. For me about 6 seconds (jtag at 350Khz real). Thanks Salvador ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
