cancel
Showing results for 
Search instead for 
Did you mean: 

ST-LINK GDB debuger ends with error. Open OCD work properly.

srameond
Associate

GDB debuger ends on my blue pill with error.

Error in initializing ST-LINK device. Reason: (18) Could not verify ST device! Abort connection.

Open ODC works fine. Output stream is below.

Open On-Chip Debugger 0.10.0+dev-g30d1303 (2020-06-18-09:13)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

Info : STLINK V2J37S7 (API v2) VID:PID 0483:3748

Info : Target voltage: 3.138582

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : clock speed 4000 kHz

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x2ba01477

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

Info : starting gdb server for STM32F103C8Tx.cpu on 3333

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

target halted due to debug-request, current mode: Handler HardFault

xPSR: 0x01000003 pc: 0xfffffffe msp: 0x20004f98

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : device id = 0x20036410

Info : flash size = 128kbytes

target halted due to debug-request, current mode: Handler HardFault

xPSR: 0x01000003 pc: 0xfffffffe msp: 0x20004f98

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

Info : Unable to match requested speed 8000 kHz, using 4000 kHz

target halted due to debug-request, current mode: Thread 

xPSR: 0x61000000 pc: 0x2000003a msp: 0x20004f98

Version in my ST-LINK should be correct. Actual is ST-LINK FW : V2J37S7.

What can cause this problems ?

Thanks

0 REPLIES 0