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:
1. I would like to see the output from openocd in a console window ...
so I run it as an external tool in eclipse.
2. As openocd runs under cygwin, It is hard to run it by just typing
"openocd" and as a pipe ... I need to have the cygwin dll in my path
somewhere at least and my openocd.exe in my path as well.
I will have a go at doing this different, so can run it as a pipe.
Cheers,
Bernie
But that's exactly what the event handlers in openocd.cfg does! Calling
reset init before and after gdb flashing.
Den 19 okt 2010 21.26, "Bernard Mentink"
<bernard.ment...@trimble.co.nz> skrev:
I have got decent results in Helios using the "GDB (DSF)
Hardware
Debugging Launcher" with the foll...
---------------------------------------------------
Hi Andreas,
I can't do the above because I need to execute a "reset init" on
the
target. My reset-init event handler configures the PLL and ramps
the
jtag clock up to 6Mb/s .... none of those "tick" options (or
lack of
them) allow me to execute a "reset init" in the correct order
...
IE at the moment I do this in an init script and I untick
everything
except load symbols ..
target remote localhost:3333
mon reset init
mon flash write_image erase unlock
C:/eclipse/LPC17xx_test/dbg/Trial.elf
0 elf
mon reset init
I need to do the reset init twice as you need a halt after the
flashing,
and I want to do my debugging at the fast speed ... If I put a
"reset
halt" as
The last step I would be back to the slow clock again.
Basically the "tick" options do not give enough flexibility to
emulate
the init script above (which works fine by the way ..)
Cheers,
Bernie
Cheers,
Bernie
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
