Skip to main content
ADębs.1
Senior
Aug 23, 2022 11:50 AM UTC
Question

Error localhost:61234: Connection timed out.

Error in final launch sequence:

Failed to execute MI command:

target remote localhost:61234

Error message from debugger back end:

localhost:61234: Connection timed out.

Failed to execute MI command:

target remote localhost:61234

Error message from debugger back end:

localhost:61234: Connection timed out.

Why?

    This topic has been closed for replies.

    22 replies

    Graduate
    Sep 3, 2024 2:20 PM UTC

    But, i have resolve my problem (bad config) :

    "Debug configuration..." > "Debugger"

     - Change :  "[X] Connect to remote GDB server" to "[X] Autostart local GDB serveur".

     - Chek if "Debug probe" is "ST-LINK (ST-LINK GDB serveur).

     - And :  "[X] ST-LINK S/N" and press "[Scan]".

     

     

    SGasp.1
    Associate III
    Sep 4, 2024 1:20 PM UTC

    @S3b   i have tried but nothing. my st link is hot when i touch it 

    Visitor II
    Sep 4, 2024 2:08 PM UTC

    Make sure both of the st-link jumpers on your board are exist.

    Visitor II
    Oct 5, 2024 6:40 AM UTC

    What fixed the issue for me was removing a misplaced jumper that was causing the board to be stuck in the reset state. Check the user manual of your board for what jumpers are needed for what function, then remove the jumpers that are out of place. You can search "jump" or "JP" to make searching the manual faster.

    Visitor II
    Mar 20, 2025 8:15 PM UTC

    In my case ST-Link Upgrade from STM32CubeIDE helped.

    Associate III
    May 10, 2025 4:43 PM UTC

    In my case it was just restarting the computer, I have windows 11 and CubeIDE 1.17.0