Sysprogs forums › Forums › VisualGDB › OpenOCD doesn’t work with Nucleo-F411RE
- This topic has 7 replies, 3 voices, and was last updated 10 years, 8 months ago by
Tension.
-
AuthorPosts
-
January 12, 2015 at 23:30 #964
Anonymous
ParticipantI’ve tried all the suggestions found on web, but nothing worked… đ„
When I Start Debugging with GDB, this is the error I have:Open On-Chip Debugger 0.8.0 (2014-05-02-12:11)
Licensed under GNU GPL v2
For bug reports, read
… hyperlink snipped…
Info : This adapter doesn’t support configurable
speed
Info : STLINK v2 JTAG v23 API v2 SWIM v6 VID 0x0
483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.269291
Info : stm32f4x.cpu: hardware has 6 breakpoints,
4 watchpoints
target state: halted
target halted due to debug-request, current mode
: Thread
xPSR: 0x01000000 pc: 0x08002390 msp: 0x20000560
Info : accepting ‘gdb’ connection from 3333
Info : device id = 0x10006431
Warn : Cannot identify target as a STM32 family.
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb
-attach event for the target to prepare target f
or GDB connect, or use ‘gdb_memory_map disable’.
Error: attempted ‘gdb’ connection rejected
But if I test the OpenOCD settings, all is fine:
C:UsersGuidoAppDataLocalVisualGDBEmbeddedDebugPackagescom.sysprogs.arm.openocdbinopenocd.exe -f interface/stlink-v2-1.cfg -f target/stm32f4x_stlink.cfg -c init -c “reset init”
Open On-Chip Debugger 0.8.0 (2014-05-02-12:11)
Licensed under GNU GPL v2
For bug reports, read
… hyperlink snipped…
Info : This adapter doesn’t support configurable speed
Info : STLINK v2 JTAG v23 API v2 SWIM v6 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.267717
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08002390 msp: 0x20000560
Info : accepting ‘gdb’ connection from 3333
Is there someone that could help me to make VisualGDB work with ST-Link v2-1?
Thanks and best regards
GuidoJanuary 14, 2015 at 22:40 #3516Anonymous
ParticipantSolved using files of an unofficial OpenOCD 0.9.0 found here
http://cid-36f4d1230f8a673c.onedrive.live.com/browse.aspx/.Public/tool/OpenOCD/OpenOCD_Build/Binary
I hope that it would be useful for other people.
GuidoJanuary 18, 2015 at 19:49 #3518support
KeymasterHi,
We have updated our OpenOCD package to support the Nucleo-F411RE board correctly. You can update it via Tools->Embedded Tools Manager.
January 18, 2015 at 23:20 #3517Anonymous
ParticipantOk, thanks.
I will try it.
Best regards
GuidoJanuary 18, 2015 at 23:45 #3519Anonymous
ParticipantIt works!
Thanks!February 9, 2015 at 02:54 #6132Tension
ParticipantMe too. My F302-Nucleo failed with OpenOCD 0.8.0-r6
February 10, 2015 at 04:47 #6138support
KeymasterHi,
Could you please share an error log you are getting on the F302?
February 13, 2015 at 01:51 #6143Tension
ParticipantHi,
I’ve pasted those in a new issue.
-
AuthorPosts
- You must be logged in to reply to this topic.