On 04/11/2012 05:46 PM, 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). >> > It took about 3 minutes for me @ 200kHz TCK (set in CFG file). See below. > Unbelievable... What can we do ? > Is like your cpu is clocked very slow, or is forced to sleep state,......??? I can't see any strange messages, only where i see 10ms you have 300 or 600ms.
Can you check your hardware for pin connections? If you have a soic, spdip or ssop can you check if pins 8, 19 and 27 are tied to ground (Vss) and that the pins 13, 23 and 28 are really tied to Vdd ( 3.3V in my board)?. I have tested pin 15 (Vbus) to Vdd or Vss, but no change. /MCLR is tied to Vdd through a 820 Ohm resistor, i tested this before, with or without srst line of the adapter, but no change. Pins 14, 16, 17 and 18 are for Jtag. The rest of the pins are left not connected, floating. Have you something attached to this pins?. 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
