cancel
Showing results for 
Search instead for 
Did you mean: 

Error in initializing ST-LINK device. Reason: No device found on target. F103RB

BadEngineer
Associate II

I am using a nucleo-F103RB. This device was functional in the past. 

I am getting an error 

 

Error in final launch sequence:

 

Failed to execute MI command:

target remote localhost:61239

 

Error message from debugger back end:

localhost:61239: Connection timed out.

Failed to execute MI command:

target remote localhost:61239

 

Error message from debugger back end:

localhost:61239: Connection timed out.

localhost:61239: Connection timed out.

 I have tried different cables to ensure it isn't the issue. I have also changed the port number. 

This is my debugger information: 

BadEngineer_0-1728150589400.png

I am able to upgrade my stlink chip via cube ide as shown in the image below (it detects it)

BadEngineer_1-1728150677652.png

I have tried to use the stm32cubeprogrammer application too but that doesn't seem to work. 

BadEngineer_2-1728150746799.png

I get the below error. 

BadEngineer_3-1728150768667.png

However i know it is working on COM7 because the last thing i did was create a program to output some information through the USART, which it is still doing (image below). 

BadEngineer_4-1728150865552.png

 

I have also attached images of my board. 

BadEngineer_5-1728150966432.pngBadEngineer_6-1728150996974.png

 

 

 

 

2 REPLIES 2
AScha.3
Chief II

Maybe you did something, to block the swd , not defined degub in Cube, use swd pins for something else...

to get access :

set debug to hardware reset;

try. If not connect in IDE :

or in cubeProgrammer : set st-link, hardware reset, connect under reset.

Then full erase , to get away the "problem" program.

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

Is this what you mean?

BadEngineer_0-1728157034766.png

 

I have changed the option to this and i still get the same error