Failed to execute MI command: target remote localhost: 3333

HTran.1891 · ‎2019-10-23

Hi, I’m using STM32CubeIDE 1.1.0 (Window) and bluepill STM32F103C8T6 but I met error when debugging:

Error in final launch sequence:

Failed to execute MI command:

target remote localhost:3333

Error message from debugger back end:

localhost:3333: The system tried to join a drive to a directory on a joined drive.

Failed to execute MI command:

target remote localhost:3333

Error message from debugger back end:

localhost:3333: The system tried to join a drive to a directory on a joined drive.

Can anyone show me how to configure debug step by step?

Thanks!

Markus GIRDLAND · ‎2019-10-24

If you have a regular ST board there should not be a need to configure anything to launch a debug session after you've built the project.

Make sure the board is connected properly. Do you have STM32CubeProgrammer stand-alone? If so, can you connect to the board with it?

If you're still running into problems then please activate the gdb server log in the debug configuration (Debugger tab) and post it.

HTran.1891 · ‎2019-10-24

Hi, I could connect the board using STM32CubeProgrammer and I dont change anything in Debug Configuration. But when I click Debug, it showed the error like above. Here are some pictures that show the debug configuration:

Is that the problem related to my ST-Link?

Thanks.

DHirs.1806 · ‎2019-11-30

Hi,

I am having this exact same issue with STM32CubeIDE on OSX. I haven't changed any of the configurations for the debugger either.

DHirs.1806 · ‎2019-11-30

I am using a nucleo32 board. The board is connected via usb and has worked with mbed just fine.

HTran.1891 · ‎2019-12-02

Hi, I found out that the problem is because of fake STM32 chip. If you use real STM32 chip or development board from manufacturer, STM32CubeIDE will work fine.

GGill.1 · ‎2020-05-14

Fake maybe ONE of the reasons. Certainly not the only reason..... I have the problem with a NEW Nucleo-64 STM32L476

RS009 · ‎2021-06-21

I had the same problem with the Discovery board

> check cable and try changing the port if it still exists then do the following steps, I solved by this way.

Download this ST-Link Utility from ST website as shown in figure

Connect your device like discovery board to PC
click on connect to the target, if it shows an error then click on a firmware update.
again click on connect device, it will show the latest version or an older one, once click on update firmware.
after updating once again click on connect the target it will connected and then try to debug from IDE

SJant.1 · ‎2022-06-13

This worked for me, thanks.

I had actually switched to jlink using the ST-reflash utility and when I restored the ST-Link it was not getting detected in stm32cubeide. But these steps fixed the issue.

I am using a Nucleo F767ZI btw.