I have a TI Stellaris Launchpad and I’m using the ARM build tools provided by ARM. I am trying to get openocd built, running and using gdb to debug in cygwin. I was able to generate an executable and set up a configuration item, based heavily off of a nice tutorial from Mauro Scomparin (http://scompoprojects.wordpress.com/201 … pad-board/). It did not appear that the trunk of the git tree of openocd contained the TI ICDI stuff yet, so I ended up using the patch similarly to what Mauro did in his.
So I now have an executable…when trying to launch it with an LM4F120XL configuration file like so:
pimmel@pig ~/stellaris/openocd-bin
$ ./openocd.exe --file ./LM4F120XL.cfg
Open On-Chip Debugger 0.7.0-dev-00089-ge9b3395 (2013-01-29-08:27)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
adapter speed: 1000 kHz
Info : clock speed 1000 kHz
Segmentation fault (core dumped)
I can’t see a core dump but there is a stackdump that was generated:
pimmel@pig ~/stellaris/openocd-bin
$ cat openocd.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=0054A740
eax=00000000 ebx=004D072E ecx=00000000 edx=0000000E esi=80061085 edi=00000000
ebp=00000000 esp=00289040 program=C:\cygwin\home\pimmel\stellaris\openocd-bin\openocd.exe, pid 5912, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
End of stack trace
The all-mighty google has really not turned anything up for the STATUS_ACCESS_VIOLATION in conjunction with openocd and windows. Does anyone out there have any hints on where to start?