openocd 0.5.0 + jlink + stm32evale help

Hi all,

I’m attempting to get openocd 0.5.0 working with my Jlink and my STM3210E eval board. I’m running on XP and using the prebuilt binary from from http://www.freddiechopin.info/.

I think I can connect OK, but if I then try gdb, I get a failure:

Z:\tools\openocd-0.5.0>bin\openocd-0.5.0.exe -f interface\jlink.cfg -f board\stm3210e_eval.cfg

Open On-Chip Debugger 0.5.0 (2011-08-09-23:21)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.berlios.de/doc/doxygen/bugs.html

Warn : Adapter driver ‘jlink’ did not declare which transports it allows; assumi

ng legacy JTAG-only

Info : only one transport option; autoselect ‘jtag’

1000 kHz

adapter_nsrst_delay: 100

jtag_ntrst_delay: 100

cortex_m3 reset_config sysresetreq

Info : J-Link initialization started / target CPU reset initiated

Info : J-Link ARM V7 compiled Jun 30 2009 11:05:27

Info : J-Link caps 0xb9ff7bbf

Info : J-Link hw version 70000

Info : J-Link hw type J-Link

Info : J-Link max mem block 9152

Info : J-Link configuration

Info : USB-Address: 0xff

Info : Kickstart power on JTAG-pin 19: 0xffffff01

Info : Vref = 3.267 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0

Info : J-Link JTAG Interface ready

Info : clock speed 1000 kHz

Info : JTAG tap: stm32.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba0

0, ver: 0x3)

Info : JTAG tap: stm32.bs tap/device found: 0x06414041 (mfg: 0x020, part: 0x6414

, ver: 0x0)

Info : stm32.cpu: hardware has 6 breakpoints, 4 watchpoints

from gdb:

target remote localhost:3333

openocd says:

Info : accepting ‘gdb’ connection from 3333

Info : device id = 0x10016414

Info : flash size = 512kbytes

Error: Target not halted

Error: auto_probe failed

Error: Connect failed. Consider setting up a gdb-attach event for the target to

prepare target for GDB connect, or use ‘gdb_memory_map disable’.

Error: attempted ‘gdb’ connection rejected

Any ideas? I’ve tried varying the jtag speed, but then I get an error on connect:

Z:\tools\openocd-0.5.0>bin\openocd-0.5.0.exe -f interface\jlink.cfg -f board\stm3210e_eval.cfg -c “jtag_rclk 3000”

Open On-Chip Debugger 0.5.0 (2011-08-09-23:21)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.berlios.de/doc/doxygen/bugs.html

Warn : Adapter driver ‘jlink’ did not declare which transports it allows; assumi

ng legacy JTAG-only

Info : only one transport option; autoselect ‘jtag’

1000 kHz

adapter_nsrst_delay: 100

jtag_ntrst_delay: 100

cortex_m3 reset_config sysresetreq

RCLK - adaptive

Info : J-Link initialization started / target CPU reset initiated

Info : J-Link ARM V7 compiled Jun 30 2009 11:05:27

Info : J-Link caps 0xb9ff7bbf

Info : J-Link hw version 70000

Info : J-Link hw type J-Link

Info : J-Link max mem block 9152

Info : J-Link configuration

Info : USB-Address: 0xff

Info : Kickstart power on JTAG-pin 19: 0xffffff01

Info : Vref = 3.267 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0

Info : J-Link JTAG Interface ready

Info : RCLK (adaptive clock speed)

Error: jlink_usb_message failed with result=1)

Error: jlink_tap_execute, wrong result -107 (expected 1)

Error: jlink_usb_message failed with result=1)

Error: jlink_tap_execute, wrong result -107 (expected 1)

in procedure ‘transport’

in procedure ‘init’

Thanks!

Morgan

morgan@mojolabs.net

I would hope you have figured your problem out by now. But it looks like your target is not halted.

The auto probe message may be concerning too.

I would go back to the startup xxx.cfg files and make sure those run from Dos window, if you are still

working this issue.