On Mon, Oct 18, 2010 at 9:30 PM, Bernard Mentink
bernard.ment...@trimble.co.nz wrote:
On 2010-10-18 20:54, Bernard Mentink wrote:
Well I have tried that, but I get this error from the GDB
(DSF)Hardware debugger plugin for Eclipse:
You need to select Standard GDB Hardware Debugging Launcher
I have got decent results in Helios using the GDB (DSF) Hardware
Debugging Launcher with the following, pretty straight-forward,
configuration.
Main tab:
Select project and binary as usual
Debugger tab:
GDB Command: arm-none-eabi-gdb
Check Use remote target
JTAG Device: OpenOCD (via pipe)
(GDB
Oh, well that is news to me, so you are saying that with no tick
option for reset etc that reset-init event is still called before and
after... ok that is good.
The other problem I have with your approach is I cannot easily use
openocd as a pipe on my windoze machine for these reasons:
Hi Andreas,
I have tried to do what you describe below.
I have setup my windows paths so that openocd (cygwin version) runs fine
in a normal console window .. That works.
I can now run openocd with the pipe option in eclipse.. I also have
modified my openocd.cfg file to include the
On 2010-10-18 20:54, Bernard Mentink wrote:
Well I have tried that, but I get this error from the GDB
(DSF)Hardware debugger plugin for Eclipse:
You need to select Standard GDB Hardware Debugging Launcher and
instead of load command - use the available options below Load Image
and Symbols
