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
gdb-flash-write-end and gdb-flash-write-start events which call reset
init.
However, when I start up the debugger, I get this error:
------
Error in final launch sequence
Failed to execute MI command:
target remote | openocd --pipe
Error message from debugger back end:
Remote communication error: No error.
Remote communication error: No error.
------
It seems to download fine (I get the normal 4 second download delay) but
I get this error when debugging goes to start.
Any ideas?, can I turn on extra debugging somewhere to get any extra
info?
Cheers,
Bernie
----------------------------------------------------------------------
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 Connection String: "| openocd --pipe")
Startup tab:
Uncheck Reset and delay... and Halt
Check Load image, use project binary
Check Load symbols, use project binary
Check Set breakpoint at: main
Check Resume
No run or init commands specified
In the project root, create a file openocd.cfg:
---
source interface.cfg
source [find target/stm32.cfg]
source [find chip/st/stm32/stm32.tcl]
stm32.cpu configure -event gdb-flash-write-end {
reset init
}
stm32.cpu configure -event gdb-flash-erase-start {
reset init
}
--------------------------------------------------------
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
