On 04/09/2012 04:06 PM, Vaclav Peroutka wrote: >> >> Load the init script: "reset init" >> >> For flashing test.hex: "flash write_image test.hex" > > Salvador, thank you, I forgot "reset init". Anyway, programming and > debugging is terribly slow. I use Segger JLink with TCK set to 200 > kHz. Programming of the chip is even incorrect. So I tried to burn the > code with Pickit3 and then connect with OpenOCD. single step takes > about 20 seconds - excerpt of the Openocd log is below. > > I don't know if it is a problem of PIC32 target or JLink interface. I > tried different TCK settings but still the same. Can somebody else > check where is the problem ? Your openocd version is a little old and don't have support for flashing pic32mx1xx/2xx. If you tray to program with reset init probably will program your flash incorrect. Can you please tray the last version from git? Also you don't need to move the "global _WORKAREASIZE" at pic32mx.cfg in new versions.
If you can't, better set " -work-area-size 0 " instead of " -work-area-size$_PIC32MX_PROGSIZE ". It is slow, but a little faster and you get a correct flash programming. I can't see this 20 seconds for single step in gdb. "(gdb) monitor step" takes less than 1 second. "(gdb) step or next" from 1 to 5 seconds. I've got a wiggler clone, runs at 350 Khz, so i can't help much with your JLink interface. 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 OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
