From: Salvador Arroyo Date: Sat, 23 Feb 2013 19:00:21 +0000 (+0100) Subject: pic32mx: 0 wait state option X-Git-Tag: v0.7.0-rc1~27 X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=commitdiff_plain;h=1d040adb0dd838f4d49b87573ee912d5bc917886 pic32mx: 0 wait state option By default pic32mx starts after any reset with 1 wait state for RAM access/exec. It can be changed to 0 wait states by clearing the BMXWSDRM bit (bit 6) in BMXCON register. With 0 wait states near doubles the execution speed. CRC check sum can be done much faster increasing verify_image speed. Fast data transfer also works with a bit higher scan rate, up to 1500 Khz. This option can be set at any time with mww 0xbf882004 0x40 or cleared with mww 0xbf882008 0x40. Some numbers for FTDI/HS with current devel code and a elf file: Core clock / wait states verify_image speed ------------------------------------|------------------------------ 4 Mhz / 1 21 KiB/s 4 Mhz / 0 36 KiB/s 8 Mhz / 1 37 KiB/s 8 Mhz / 0 57 KiB/s Change-Id: I4092ad0f3753f72f77108718d0ed3a3ab84e3b23 Signed-off-by: Salvador Arroyo Reviewed-on: http://openocd.zylin.com/1141 Tested-by: jenkins Reviewed-by: Spencer Oliver Reviewed-by: Xiaofan --- diff --git a/tcl/target/pic32mx.cfg b/tcl/target/pic32mx.cfg index 8a8eea0ebc..d53b99a587 100644 --- a/tcl/target/pic32mx.cfg +++ b/tcl/target/pic32mx.cfg @@ -50,12 +50,11 @@ $_TARGETNAME configure -event reset-init { # from reset the pic32 cannot execute code in ram - enable ram execution # minimum offset from start of ram is 2k # - global _PIC32MX_DATASIZE global _WORKAREASIZE - # BMXCON - mww 0xbf882000 0x001f0040 + # BMXCON set 0 wait state option by clearing BMXWSDRM bit, bit 6 + mww 0xbf882000 0x001f0000 # BMXDKPBA: 2k kernel data @ 0xa0000000 mww 0xbf882010 $_PIC32MX_DATASIZE # BMXDUDBA: 14k kernel program @ 0xa0000800 - (BMXDUDBA - BMXDKPBA)