On 19 March 2012 14:47, Uhrheber <uhrhe...@gtfe.de> wrote: > On 19.03.2012 15:23, Spencer Oliver wrote: > >> # set working area to suit >> set WORKAREASIZE 8192 > > This makes 32kbytes.
how - 8192 bytes > But how is the address of the work area defined? > Program flash starts at 0x1D000000 (for all PIC32), and ends at > 0x1D007FFF (for this particular device). > all the memory definitions are in target/pic32mx.cfg > And this is only the program flash, the PIC32 has an additional 3k > boot flash(0x1FC00000 to 0x1FC00BEF), and also flash configuration fuses > at 0x1FC00BEF to 0x1FC00BFF. > > How do I access this? > look inside target/pic32mx.cfg > Unlike most of the ARM chips, the PIC's oscillator configuration, PLL, > boot type, etc. is permanently written to flash registers, independently > from the program flash. But they are still flash memory locations, programmed just the same. > The content of the flash fuses is normally put into the source code by > pragmas, and written to the ELF/HEX file. > The programmer has to read this locations and write the fuses accordingly. > > How is this done with OOCD? Flash is defined in the same file as above - target/pic32mx.cfg As long as your resulting hex/s19/elf has the correct memory locations it will be programmed correctly. 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
