> 
> 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).
> 
Hello, I just tried it on another computer - Windows XP again. Result is 
approximately 30 seconds @ 200kHz real. I made a snapshot on oscilloscope (I 
can send it here, too). I see that between JTAG transfers there are delays of 
around 600us. I then experimentally increased TCK to 1MHz. TCK increased but 
delay of 600us between transfers was still there. Time of MDW went down to 25 
seconds.

For comparison, I connected STM32 with the same setup. Communication with STM32 
is incomparably faster. Look below. I see the difference that PIC32 MDW goes to 
some special function, unlike MDW on STM32. It seems to me, that something 
inside mips_m4k_read_memory() works bad. Maybe a memory leak? Some systems are 
not affected with it. But it looks that mine is. 

One thing confuses me. Why there is so small amount of debug messages for -d3 ?

Vaclav


******************* PIC32
Debug: 349 35141 command.c:145 script_debug(): command - ocd_command 
ocd_command type ocd_mdw 0xa0000000 1024
Debug: 350 35141 command.c:145 script_debug(): command - mdw ocd_mdw 0xa0000000 
1024
Debug: 352 35141 mips_m4k.c:785 mips_m4k_read_memory(): address: 0xa0000000, 
size: 0x00000004, count: 0x00000400
User : 410 64766 command.c:547 command_print(): 0xa0000000: 00078fdf 00000000 
00000000 00000000 e37b95f3 9dbf515b cf54e881 95eb62e
5

********** STM32
Debug: 442 42125 command.c:145 script_debug(): command - mdw ocd_mdw 0 1024
User : 444 42203 command.c:547 command_print(): 0x00000000: 20005000 080006c1 
08000749 0800074d 08000751 08000755 08000759 0000000
0

------------------------------------------------------------------------------
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

Reply via email to