Dear Salvador, I put comments inside.
> 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. I use version from 4th April 2012 ( openocd-0.6.0-dev-120404085158.zip ). Your changes are from 31st March ? How can I detect if I use right OpenOCD ? > > 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 will try it. > 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. This is overall time from point I pressed "s <ENTER>" in mips-gdb to the point when new prompt appeared. Between these two times, messages attached to the last email arrived in OpenOCD window. So there is quite big overhead of other communication? It probably does source-level stepping through breakpoints. > > I've got a wiggler clone, runs at 350 Khz, so i can't help much with > your JLink interface. I will try FT2232 after I will find it but I am not sure that something will get improved. Vaclav ------------------------------------------------------------------------------ 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
