[OpenOCD-user] Cannot identify STM32C071 device.

[Josef R. <jos...@gm...>]

Hello,

I am currently trying to get OpenOCD working with an STM32C071KBUxN
and an STLINK v3 using this patch:
https://review.openocd.org/c/openocd/+/8525

But the device cannot be identified even though it read the correct device ID.
Using the STM32CubeProgrammer is not showing any issue, so I assume my
hardware is fine.

That's the log:

Open On-Chip Debugger 0.12.0+dev-00802-gc40b8359c-dirty (2024-12-16-18:11)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V3J15M7B5S1 (API v3) VID:PID 0483:374F
Info : Target voltage: 3.218543
Info : clock speed 1000 kHz
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x0bc11477
Info : [stm32f0x.cpu] Cortex-M0+ r0p1 processor detected
Info : [stm32f0x.cpu] target has 4 breakpoints, 2 watchpoints
Info : [stm32f0x.cpu] Examination succeed
Info : [stm32f0x.cpu] starting gdb server on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : device id = 0x10016493
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 for GDB connect, or use 'gdb_memory_map
disable'.
Error: attempted 'gdb' connection rejected


Could that be an issue in this patch, or is there a mistake on my side?

Thanks,
Josef