On Wed, Apr 11, 2012 at 5:46 PM, Vaclav Peroutka <[email protected]> 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). >> > > It took about 3 minutes for me @ 200kHz TCK (set in CFG file). See below. > Unbelievable... What can we do ? > > Vaclav > > Debug: 447 41969 command.c:145 script_debug(): command - ocd_command > ocd_command type ocd_mdw 0xa0000000 1024 > Debug: 448 41969 command.c:145 script_debug(): command - mdw ocd_mdw > 0xa0000000 1024 > Debug: 450 41985 mips_m4k.c:785 mips_m4k_read_memory(): address: 0xa0000000, > size: 0x00000004, count: 0x00000400 > User : 821 233125 command.c:547 command_print(): 0xa0000000: 000256b9 > 00000000 00000000 00000000 e33b9ff3 9d9f515b cf54e841 9dca62 > e5 > User : 822 233141 command.c:547 command_print(): 0xa0000020: 612d4c30 > dd391f9f 36b8cef6 51011c21 4e3dd5ba 58b28958 fd569f41 89d202 > c0 > User : 823 233157 command.c:547 command_print(): 0xa0000040: 1d272602 > 5794af40 247f5163 99524301 4a07aaba fc35d5bc f7f0237f a5d26e > df >
Do the same with -d3 to hopefully see what's happening during the three minutes. It depends on the target and interface driver how much useful info it prints at highest debug level, but at -d2 you won't be able to see anything. /Andreas ------------------------------------------------------------------------------ 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
