Skip to main content
Mohan1
Mohan1
Associate III
December 1, 2019
Question

How can I remove error like 'Waiting for debugger connection... Debugger connected Debugger connection lost. Shutting down...'

  • December 1, 2019
  • 5 replies
  • 2135 views

Hello,

I am generating code using STM32CubeIDE ,but when i start to debug getting error like-

"STMicroelectronics ST-LINK GDB server. Version 5.2.3

Copyright (c) 2019, STMicroelectronics. All rights reserved.

Starting server with the following options:

    Persistent Mode      : Disabled

    Logging Level       : 1

    Listen Port Number     : 61234

    Status Refresh Delay    : 15s

    Verbose Mode        : Disabled

    SWD Debug         : Enabled

Waiting for debugger connection...

Debugger connected

Debugger connection lost.

Shutting down..."

I am using latest version of st-link USB driver(en.stsw link009).Also i am using USB to TTL converter.Initially everything working very well,near about ten code executed successfully.But now facing the above error.So how can i solve it?

Thanks in advance.

This topic has been closed for replies.

5 replies

jw56
jw56
Associate III
March 1, 2020

Currently having the same issue - only difference is ST-LINK GDB server Version 5.5.0. Did you ever find a solution?

etheory
etheory
Senior
March 1, 2020

This happens to me quite frequently with a Nucleo board, and is usually fixed by unplugging then plugging back in the usb cable of your device. It's extremely frustrating that it is this unstable, but many other users seem to report similar things.

AAlve.11
AAlve.11
Visitor II
March 6, 2020

Same problem here with STM32g071 nucleo! any suggestions?

Vvine
Vvine
Associate II
April 9, 2020

Try to debug with the ST-LINK using a different project. It should work (worked for me atleast). Then again try with the original project.

EAppe.1
EAppe.1
Associate
December 31, 2020

I have the same issues:

  • target MCU programs correctly.
  • debug aborts on resume or run, then target runs by itself.
  • single-stepping works, but if breakpoints are set then on resuming or running then debugger never stops at the breakpoint(s).

Debugger connection lost.

Shutting down...

I have created a new post for this.

Terms & ConditionsAccessibility statement