> Hi, are you sure about that ? Today I started to play with OpenOCD and PIC32.
> I
> have exactly the same chip and my CPUTAPID is 0x04a00053.
>
> What is the correct setting of WORKAREASIZE ? I use 0x1000. This PIC32 has 8kB
> but first 2kB must be free, right ?
>
> For development, do you use stock Microchip tools (C-compiler, MPLAB8/MPLABX)
> or
> something else (MIPS GCC etc ) ?
>
Hello, can I have another question? How can I burn FLASH ? "flash write_image
erase unlock test.hex 0 ihex" is not enough . Please see the log below. D3
debug does not show more info...
d:\\opt\\OpenOCD\\openocd-0.6.0-dev-111231122355\\bin\\openocd-0.6.0-dev-111231122355.exe
-f jlink.cfg -f pic32mx.cfg -f flash_pro
g.cfg
Open On-Chip Debugger 0.6.0-dev-00308-g7e22576 (2011-12-31-13:49)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Warn : Adapter driver 'jlink' did not declare which transports it allows;
assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
100 kHz
0x1000
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
Runtime Error: flash_prog.cfg:6: flash write_image erase unlock test.hex 0
ihex: command requires more arguments
in procedure 'script'
at file "embedded:startup.tcl", line 58
in procedure 'flash' called at file "flash_prog.cfg", line 6
make: *** [burn] Error 1
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
