How to update OpenOCD to version 0.11.0

[hvbill]

Hi,

Does anyone now if it is possible to upgrade OpenOCD for VisualGDB to the latest version, 0.11.0?

I’m trying to create a project in VisualGDB for a ST NUCLEO-G0B1RE board, following the Embedded Project Wizard.
But when I open the VisualGDB project properties and press Test in the Debug settings, there is an error, see output below, that the CPU isn’t recognized.

I suspect it is the OpenOCD version that needs to be updated to latest (0.11.0). I have tried with both VisualGDB 5.5r4 and 5.6 beta-1 and OpenOCD 20201228-0.10.0 and 20210407-0.10.0 running on Windows 10.

OpenOCD output:

C:\Users\H655374\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c "gdb_port 65387" -c "telnet_port 65385" -f interface/stlink.cfg -f target/stm32g0x.cfg -c init -c "reset init" -c "echo VisualGDB_OpenOCD_Ready"
Open On-Chip Debugger 0.10.0 (2020-12-28) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : clock speed 2000 kHz
Info : STLINK V2J37M27 (API v2) VID:PID 0483:374B
Info : Target voltage: 3.232169
Info : stm32g0x.cpu: hardware has 4 breakpoints, 2 watchpoints
Info : starting gdb server for stm32g0x.cpu on 65387
Info : Listening on port 65387 for gdb connections
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
target halted due to debug-request, current mode: Thread 
xPSR: 0xf1000000 pc: 0xfffffffe msp: 0xfffffffc
VisualGDB_OpenOCD_Ready
Info : Listening on port 6666 for tcl connections
Info : Listening on port 65385 for telnet connections
Info : accepting 'gdb' connection on tcp/65387
Warn : Cannot identify target as an STM32G0/G4/L4/L4+/L5/WB/WL family device.
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

 

[support]

Hi,

The 20210407-0.10.0 version is based on the snapshot of the OpenOCD’s master branch from 2021-04-07 that does correspond to OpenOCD 0.11.0, so other than the older version number, it should be equivalent to 0.11.

Either way, we have released another package (20210503-0.11.0) based on the current git snapshot. Feel free to update to it.

If it still doesn’t contain support for the necessary devices, please consider waiting a couple of months for ST to add support for them, or try building OpenOCD manually as shown here and patching it manually. It typically involves searching for the error message and adding an entry for your device to the supported device list (the entry would map the flash ID to the parameters like page size taken from the device datasheet).

[hvbill]

Thanks for the new OpenOCD build. Unfortunately it didn’t help, but your support is really great.

Looking into the OpenOCD output above once again, could it have something to do with GDB?

[support]

No problem,

The “Cannot identify target as an STM32G0/G4/L4/L4+/L5/WB/WL family device” message means that the support for your device has not been added to OpenOCD yet.

Please consider waiting a couple of months for ST to add support for them, or try building OpenOCD manually as shown here and patching it manually. It typically involves searching for the error message and adding an entry for your device to the supported device list (the entry would map the flash ID to the parameters like page size taken from the device datasheet).

Another option would be to use Segger J-Link with the Segger software. It gets updated much more often than OpenOCD and hence gets to support new devices much faster.

[Author]

Posts