Skip to main content
Visitor II
May 23, 2026
Question

failed to start GDB server

  • May 23, 2026
  • 3 replies
  • 82 views

Hello everyone,

I am facing a flashing/debugging issue with the STEVAL-SPIN3202 Rev 3.1 board.

Board:
STEVAL-SPIN3202 Rev 3.1

Software Used:

  • STM32CubeIDE

  • STM32CubeProgrammer

Problem:
While trying to flash or debug the board from STM32CubeIDE, I get the following error:

"Failed to start GDB server"
"Error in initializing ST-LINK device"
"Failed to connect to device"

Also, in STM32CubeProgrammer:

  • Read data operation fails

  • Target connection sometimes not detected

Additional Observations:

  • ST-LINK USB is detected intermittently

  • Board LED becomes dim/slow ON sometimes

  • Reinstalled STM32CubeIDE and drivers

  • Installed ST-LINK drivers

  • Tried different USB cables and USB ports

  • Tried lower SWD frequency

  • Tried Hot Plug mode

  • Tried BOOT0 method

  • Still unable to flash or read target

I would appreciate guidance on:

  1. Correct jumper settings for STEVAL-SPIN3202 Rev 3.1

  2. Whether onboard ST-LINK firmware may be corrupted

  3. Possible hardware protection/reset issue

  4. Correct power supply requirements during flashing

Thank you.

3 replies

GMA
ST Technical Moderator
July 10, 2026

Hello ​@Charan_sahoo,

Did you try to upgrade the ST-LINK firmware version using the Firmware upgrade button on the STM32CubeProgrammer tool?

If you agree with the answer, please accept it by clicking on 'Best answer'.Best regards.GMA
Andrew Neil
Super User
July 10, 2026
  • ST-LINK USB is detected intermittently

Sounds like you have a dodgy cable and/or a faulty USB connector.

Clearly, if the basic USB connectivity is flaky, nothing else which depends upon that connection can ever be reliable!

 

 

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
AScha.3
Super User
July 10, 2026

Hi,

>  Target connection sometimes not detected

thats most time a connection problem, so try : other usb cables, other plug/port ; try not on a hub.

And check in CubeProgrammer : option bytes → look on all sectors , protection is off.

"If you feel a post has answered your question, please click ""Accept as Solution""."