Skip to main content
JP_RS
JP_RS
Associate II
December 13, 2021
Question

STM32 debugging issue.

Earlier I used the STM32CUBEIDE 1.7.0 version it works fine then I update it to 1.8.0 then I faced an issue while debugging it showing an Error in the final launch sequence:

Failed to start GDB server

Failed to start GDB server

java.lang.NullPointerException

then I uninstall the 1.8.0 version and reinstall the 1.7.0 version but still, I faced the same error.

So, how can I fix this issue?

Thanks in advance.

This topic has been closed for replies.

13 replies

Manny
Manny
Associate II
December 13, 2021

Which debug probe are you using?

JP_RS
JP_RSAuthor
Associate II
December 13, 2021

I am using ST-LINK-V2

Manny
Manny
Associate II
December 13, 2021

Are you able to program the mcu using different software like STMCubeProgrammer? This will make sure that your probe and mcu are working correctly and non of them is faulty.

TDK
TDK
December 13, 2021

Unfortunately, Eclipse is just not the most robust piece of software. In addition, the debugging tools are often flaky.

If STM32CubeProgrammer connects, the hardware connection is there. Try restarting STM32CubeIDE and/or power cycling the chip.

"If you feel a post has answered your question, please click ""Accept as Solution""."
MHaji.1
Senior
December 14, 2021

Install ST Server again and reboot ...

APras.3
APras.3
Visitor II
March 11, 2022

I tried this, it doesn't work

APras.3
APras.3
Visitor II
March 11, 2022

Did you find any solution?

I encounter exactly the same problem

I also tried to flash the program using STM link utility and it works fine,

it is just the debugger from 1.7.0 that I cannot use

ST.9
ST.9
Visitor II
July 5, 2022

Has anyone found a solution to this? I have the same problem and I have tried all the above mentioned - still not working

IDE Version - 1.7.0

Debugger used is ST-Link V3 mini

Pavel A.
Pavel A.
July 5, 2022

Which STM32 or board do you have?

From my experience, debugger in v 1.7.0 works just fine with ST-Link V3 mini.

Newer versions seem to have some regressions.

If you've copied existing project from other PC or from Linux, try to re-create debug configuration from scratch.

PZitn.1
PZitn.1
Associate
July 27, 2022

Has anyone found a solution? I have exactly the same problem.

I had this problem when I installed STM32CubeIDE 1.10.1. Now the GDB server does not work even on the older version that I used until now, 1.6.1

ABenn.2
ABenn.2
Visitor II
August 2, 2022

i have the same problem with the same versions, can you let me now if you already found a solution.

APras.3
APras.3
Visitor II
August 2, 2022

I solved it by updating to 1.9.0 and reload my workspace

MRuze.1
MRuze.1
Visitor II
April 6, 2023

Hi, I've found a solution.

We had the same problem on our project after playing with several targets. Fortunately GIT based project allowed us to find exact commit comprising a root cause. On one computer debugging worked well unlike on mine. Problem was in *.launch configuration file.

Long story short: Find *.launch file of corresponding debug configuration and delete it. When you start debugging again, default configuration will be created.

Terms & ConditionsAccessibility statement