Skip to main content
DHirs.2
Visitor II
May 1, 2023
Question

Debugging issues with STM32CubeIDE / STM32F030F4Px

  • May 1, 2023
  • 4 replies
  • 3691 views

I am having debugging issues with STM32CubeIDE. the processor is STM32F030F4Px and I am using a knock off ST-Link V2. It seem that no matter what I configure I get the same error. There also is a check GDB server version error in the IDE window.

Open On-Chip Debugger 0.12.0-00017-gb153daa14 (2023-02-03-14:58)

 

Licensed under GNU GPL v2

 

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

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

Info : Target voltage: 3.240714

Info : clock speed 4000 kHz

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x0bb11477

Info : [STM32F030F4Px.cpu] Cortex-M0 r0p0 processor detected

Info : [STM32F030F4Px.cpu] target has 4 breakpoints, 2 watchpoints

Info : starting gdb server for STM32F030F4Px.cpu on 3333

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

Info : device id = 0x10006444

Info : flash size = 32 KiB

Warn : GDB connection 1 on target STM32F030F4Px.cpu not halted

undefined debug reason 8 - target needs reset

shutdown command invoked

Info : dropped 'gdb' connection

4 replies

Billy OWEN
ST Employee
May 5, 2023

Hi @DHirs.2​ 

The forum moderator had marked your post as needing a little more investigation and direct support. An online support case has been created on your behalf, please stand by for just a moment and you will hear from us.

Regards,

Billy

Visitor II
May 7, 2024

Unfortunately I have same problem. Is there any news about this problem??

 

Open On-Chip Debugger 0.12.0-00029-gf77e7cb03 (2023-12-15-13:25) [https://github.com/STMicroelectronics/OpenOCD]

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 V2J45S7 (API v2) VID:PID 0483:3748

Info : Target voltage: 3.231196

Info : clock speed 4000 kHz

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x0bb11477

Info : [STM32F030F4Px.cpu] Cortex-M0 r0p0 processor detected

Info : [STM32F030F4Px.cpu] target has 4 breakpoints, 2 watchpoints

Info : starting gdb server for STM32F030F4Px.cpu on 3333

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

Info : device id = 0x10006444

Info : flash size = 32 KiB

Warn : GDB connection 1 on target STM32F030F4Px.cpu not halted

undefined debug reason 8 - target needs reset

shutdown command invoked

Info : dropped 'gdb' connection

Tesla DeLorean
Guru
May 7, 2024

ST is not going support boot-leg or counterfeit equipment.

Did it even program this part?

You should check if you can connect use STM32 Cube Programmer independently.

You need VCC, SWDIO, SWCLK, NRST and GND wired to the programmer.

On low pin count devices make sure your code doesn't break debugger connectivity by disabling or reassigning pins.

If you have a BOOT0 pin, pull it HIGH to stop your code running

Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
Visitor II
March 15, 2025

Open On-Chip Debugger 0.12.0+dev-00608-gd8ed48fef (2025-02-06-11:20) [https://github.com/STMicroelectronics/OpenOCD]

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 V2J34S7 (API v2) VID:PID 0483:3748

Info : Target voltage: 3.148825

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] Cortex-M3 r2p0 processor detected

Info : [STM32F103C8Tx.cpu] target has 6 breakpoints, 4 watchpoints

Info : [STM32F103C8Tx.cpu] Examination succeed

Info : starting gdb server for STM32F103C8Tx.cpu on 3333

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

Info : device id = 0x10010414

Info : flash size = 256 KiB

Warn : GDB connection 1 on target STM32F103C8Tx.cpu not halted

undefined debug reason 8 (UNDEFINED) - target needs reset

shutdown command invoked

Info : dropped 'gdb' connection

 

Visitor II
July 18, 2025

Hi there,, did you resolve this problem?

April 12, 2026

@DHirs.2myspace wrote:

I am having debugging issues with STM32CubeIDE. the processor is STM32F030F4Px and I am using a knock off ST-Link V2. It seem that no matter what I configure I get the same error. There also is a check GDB server version error in the IDE window.

Open On-Chip Debugger 0.12.0-00017-gb153daa14 (2023-02-03-14:58)

 

Licensed under GNU GPL v2

 

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

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

Info : Target voltage: 3.240714

Info : clock speed 4000 kHz

Info : stlink_dap_op_connect(connect)

Info : SWD DPIDR 0x0bb11477

Info : [STM32F030F4Px.cpu] Cortex-M0 r0p0 processor detected

Info : [STM32F030F4Px.cpu] target has 4 breakpoints, 2 watchpoints

Info : starting gdb server for STM32F030F4Px.cpu on 3333

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

Info : device id = 0x10006444

Info : flash size = 32 KiB

Warn : GDB connection 1 on target STM32F030F4Px.cpu not halted

undefined debug reason 8 - target needs reset

shutdown command invoked

Info : dropped 'gdb' connection


Likely a reset timing issue enable connect under reset and lower SWD speed in STM32CubeIDE. Also check NRST wiring and your clone myspaceht ST Link V2 firmware, as the MCU isn’t halting before GDB connects.