On 19 March 2012 12:35, Uhrheber <uhrhe...@gtfe.de> wrote: > Hi. > > Would anybody be so nice to give me an overview of the current status of > the PIC32 support? >
Should be working fine. > I tried to flash a PIC32MX220F032B using a FT2232 based JTAG programmer > (PicoTAP). > The version I used was openocd-0.6.0-dev-120229143915 for Windows. > > I was able to get contact to the MCU, I can read, erase, erase check. > > But when I started flashing, it took several hours for 12k of code, > and afterwards the code was shifted by ~10 bytes. > It will be very slow (but not that slow) without a working area defined for your target. > Also I have some additional questions: > Do I have to connect the /MCLR pin of PIC32? SRST is optional on the PIC32, it has a special internal reset that is used if no SRST is fitted. > It seems to work without, but if I understand the PIC32 flash > programming specification right, it is needed. > So, to what should it be connected? To trst or srst? > both of them are optional. > Does OOCD use the microchip "Programming Executive", or the direct method? no, it uses its own - you have seen this loader below. > There's a flash loader assembler file (\contrib\loaders\flashpic32mx.s). > What is it good for? > see above > Exactly what files do I have to edit/add to support the PicoTAP pgrogrammer? > PicoTAP is an open design (http://www.gojtag.com/downloads). Looking at the hardware it is a FTDI clone, as all the jtag related io's are fixed (TMS, TDO, TDI, TCK) so it should work with any of the ftdi interfaces - just use reset_config none to get started. Cheers 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
