cancel
Showing results for 
Search instead for 
Did you mean: 

STM32cubeide

Vignesh_V
Associate II

Hi friends,

I am built one custom made PCB with by using STM32F103C8T6 IC for my project purpose.But ,When i am trying to upload my source code by using stm32Cubeide it shows below error.

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.

localhost:61234: Connection timed out.

I didn't know how to solve this error .I am tried to solve this error but did not solve the error till now  .so i need your help to solve this error can any one help me to solve my problem?

3 REPLIES 3
TDK
Guru

The usual suspects:

  • Check VCC voltage. Note that programmers typically do not supply power.
  • Check part orientation. Pin 1 is on the lower left when "STM32" reads from left to right.
  • Can you connect in STM32CubeProgrammer? Does it display a voltage?
  • Do you have an official ST programmer or a counterfeit one? STM32CubeIDE does not play well with knock-off programmers.
If you feel a post has answered your question, please click "Accept as Solution".

@TDK wrote:
  • Do you have an official ST programmer or a counterfeit one? STM32CubeIDE does not play well with knock-off programmers.

@Vignesh_V  If you're not sure, see:

https://community.st.com/t5/stm32-mcus/how-to-recognize-a-genuine-st-link-v2-versus-a-cloned-one/ta-p/49471

See also:

https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693

 

Rim LANDOLSI
ST Employee

Hello @Vignesh_V ,

 

Could you please check these points:

  • Ensure that the ST-LINK or other debugging interface is properly connected to the STM32F103C8T6 board
  • Verify that the power supply to the board is stable and sufficient.
  • Update ST-LINK Firmware
  • In the debug configuration, Verify that the correct port localhost:61234 and you can change it to 61238

Thanks,

Rim.