On 19 March 2012 23:02, salvador <salva...@telecable.es> wrote: > > Hello all > > I have some question regarding this pic32mx220 discussion, i have one. > > First, i never get to flash it with reset init. If init script is loaded > openocd flash it wrong. >
reset init is required so we load our init script, this sets up yhe pic32 working area, so flash programming etc are much faster. > Here is a copy from my screen, with RESET HALT first: > >> reset halt > JTAG tap: pic32mx.cpu tap/device found: 0x04a00053 (mfg: 0x029, part: >> 0x4a00, ver: 0x0) > JTAG tap: pic32mx.cpu UNEXPECTED: 0x04a00053 (mfg: 0x029, part: >> 0x4a00, ver: 0x0) > JTAG tap: pic32mx.cpu expected 1 of 1: 0x30938053 (mfg: 0x029, part: >> 0x0938, ver: 0x3) > Trying to use configured scan chain anyway... > Bypassing JTAG setup events due to errors > target state: halted > target halted in MIPS32 mode due to debug-request, pc: 0xbfc00000 >> > >> flash write_image prueba.hex > device id = 0x04a00053 (manuf 0x029 dev 0x4a00, ver 0x00) > flash size = 12kbytes > device id = 0x04a00053 (manuf 0x029 dev 0x4a00, ver 0x00) > flash size = 32kbytes > Padding image section 0 with 2168 bytes > Padding image section 8 with 396 bytes > wrote 3444 bytes from file prueba.hex in 218.929672s (0.015 KiB/s) >> >> verify_image prueba.hex > checksum mismatch - attempting binary compare > checksum mismatch - attempting binary compare > checksum mismatch - attempting binary compare > checksum mismatch - attempting binary compare > checksum mismatch - attempting binary compare > checksum mismatch - attempting binary compare > checksum mismatch - attempting binary compare > checksum mismatch - attempting binary compare > checksum mismatch - attempting binary compare > checksum mismatch - attempting binary compare > verified 880 bytes in 9.137698s (0.094 KiB/s) > > Yeah, i have a wiggler clone, a usb probe should be faster. > Without the patch it is too slow. what patch ? > With the patch applied, i can run the init script and it takes 0.6 seconds > to flash the same file. > > Second, page erase don't work for this chip, it let the chip half erased. > I don't know if there is another way to erase the chip, i did it ever with > my patch applied. > what target are you using ? Spen ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
